[GH-ISSUE #1082] Google Workspace customers must now use IMAP - like everyone else #862

New issue

Open

opened 2026-02-26 01:32:09 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 01:32:09 +03:00

Owner

Originally created by @computerbar on GitHub (Jun 4, 2022).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1082

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)

Originally created by @computerbar on GitHub (Jun 4, 2022). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1082 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)

kerem added the

xoauth

label

2026-02-26 01:32:09 +03:00

kerem commented

2026-02-26 01:32:10 +03:00

Author

Owner

@kurahaupo commented on GitHub (Sep 5, 2022):

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 commented on GitHub (Sep 5, 2022): 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.

kerem commented

2026-02-26 01:32:10 +03:00

Author

Owner

@da5nsy commented on GitHub (Jul 5, 2023):

I just tried to do this but got a connection error. Did something change? Or did I do something wrong?

@da5nsy commented on GitHub (Jul 5, 2023): I just tried to do this but got a connection error. Did something change? Or did I do something wrong? ![Screenshot_20230704-235032](https://github.com/jberkel/sms-backup-plus/assets/3739866/e7fc9b0b-4464-43eb-8787-d3abaf720d6d) ![Screenshot_20230704-235043](https://github.com/jberkel/sms-backup-plus/assets/3739866/c3faecae-0b4a-4fff-80ff-20171404376c)

kerem commented

2026-02-26 01:32:10 +03:00

Author

Owner

@da5nsy commented on GitHub (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

@da5nsy commented on GitHub (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](https://github.com/jberkel/sms-backup-plus/issues/959#issuecomment-513018820)) rather than _imap.google.com:993_

kerem referenced this issue

2026-02-26 01:32:34 +03:00

[PR #862] [MERGED] Update nl translation #991