Viktor Dukhovni: > > > On Apr 8, 2020, at 12:12 PM, Viktor Dukhovni <postfix-us...@dukhovni.org> > > wrote: > > > > The SASL mechanisms supported by [smtp.office365.com]:587 are: > > > > posttls-finger: < 250-BL0PR02CA0022.outlook.office365.com Hello [...] > > posttls-finger: < 250-SIZE 157286400 > > posttls-finger: < 250-PIPELINING > > posttls-finger: < 250-DSN > > posttls-finger: < 250-ENHANCEDSTATUSCODES > > posttls-finger: < 250-AUTH LOGIN XOAUTH2 > > posttls-finger: < 250-8BITMIME > > posttls-finger: < 250-BINARYMIME > > posttls-finger: < 250-CHUNKING > > posttls-finger: < 250 SMTPUTF8 > > posttls-finger: > QUIT > > > > "LOGIN" and "XOAUTH2". Terminology corrections aide, disabling the > > latter via: > > > >> Adding > >> smtp_sasl_mechanism_filter = plain, login > >> made things work again > > > > is most likely the correct solution, with "login" the one that'll be > > used in the case of "[smtp.outlook.com]:587". > > That said, we might unfortunately have to figure out how to deal with > XOAUTH2 at some point: > > > https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-april-2020-update/ba-p/1275508
One courageous person wrote a web page on this: Setting Up OAUTH2 Support for Fetchmail and Postfix http://mmogilvi.users.sourceforge.net/software/oauthbearer.html Wietse
