Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Workspace customers must now use IMAP - like everyone else #1082

Open
computerbar opened this issue Jun 4, 2022 · 3 comments
Open
Labels
xoauth problems caused by lack of approval to use "sensitive" Gmail API

Comments

@computerbar
Copy link

computerbar commented Jun 4, 2022

Finally Google has finally blocked it.

I get this message
This app tried to access sensitive info in
your google account. to keep your account
safe, Google blocked this access.

Edit - Update
I have now the added the custom IMAP server as TEXT and
imap.google.com:993
password
TLS

and it is now working again (with less secure app on in Google account if you have paid workspace)

@computerbar computerbar changed the title This app is blocked. This app is blocked. UPDATE - but still acecessable via custome iMAP with paid Google Workspace Jun 4, 2022
@kurahaupo kurahaupo added the xoauth problems caused by lack of approval to use "sensitive" Gmail API label Sep 5, 2022
@kurahaupo
Copy link
Collaborator

This isn't "new"; it's merely putting G-suite customers in the same position as everyone else - we all must use IMAP.

Google provided a much longer grace period for paying G-suite customers, but they were always going to do this.

When I accumulate enough tuits, I will have another go at getting Google to relent.

@kurahaupo kurahaupo changed the title This app is blocked. UPDATE - but still acecessable via custome iMAP with paid Google Workspace Google Workspace customers must now use IMAP like everyone else Sep 5, 2022
@kurahaupo kurahaupo changed the title Google Workspace customers must now use IMAP like everyone else Google Workspace customers must now use IMAP - like everyone else Sep 5, 2022
@da5nsy

This comment was marked as outdated.

@da5nsy
Copy link

da5nsy commented Jul 5, 2023

Edit - Update I have now the added the custom IMAP server as TEXT and imap.google.com:993 password TLS

This might be a me problem, but I needed to use imap.gmail.com:993 (as noted here) rather than imap.google.com:993

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
xoauth problems caused by lack of approval to use "sensitive" Gmail API
Projects
None yet
Development

No branches or pull requests

3 participants