Ok dovecot really has nothing to do with the OAuth2 via google, microsoft etc
Basically any incoming emails being forwarded are being handled by fetchmail, how it gets to dovecot (usually postfix) is of no concern.
Fethmail 7.0.0 alpha (not released yet)
see : https://sourceforge.net/projects/fetchmail/files/branch_7-alpha/
is going to or has basic support for OAuth2 support builtin
I am an ISP and will also be forced to deal with this issue shortly.
So I am just getting to testing this, last branch update was 2021-08-03
Like all beta software use at your own risk and test thoroughly.
fyi
Happy Thursday !!! Thanks - paul
Paul Kudla
Scom.ca Internet Services http://www.scom.ca 004-1009 Byron Street South Whitby, Ontario - Canada L1N 4S3
Toronto 416.642.7266 Main 1.866.411.7266 Fax 1.888.892.7266 On 4/13/2022 5:25 PM, Richard wrote:
Date: Wednesday, April 13, 2022 17:10:36 -0400 From: Steve Littslitt@troubleshooters.com
Hi all,
I'm not sure Dovecot has anything to do with this, but I'd rather ask and know for sure.
I do the following:
Gmail IMAP=>fetchmail=>procmail=>Dovecot IMAP
Then, I view my Dovecot hosted email with Claws-Mail.
I understand that on May 31, 2022, current methods to access Gmail IMAP will turn into pumpkins because of insistence on OAuth2. Do I need to do anything to Dovecot to get ready for this Mass Extinction Event?
Do you think I'll need to dump fetchmail for something else?
While it's a little obtuse, a reading of:
https://support.google.com/accounts/answer/6010255#zippy=%2Cif-less-secure-a...
specifically the "fix problems" / "use an app password" section, would seem to indicate that app passwords will continue to work for gmail access after May 30.
What google is turning off is "third-party apps or devices which ask you to sign in to your Google Account using only your username and password", i.e., using your google login password with "less secure" 3rd party apps.
So, you need to set up, and configure your application to use, app passwords.
