> On Feb 13, 2020, at 1:29 AM, Arnt Gulbrandsen <a...@gulbrandsen.priv.no> > wrote: > On Wednesday 12 February 2020 19:31:23 CET, Alexander Perlis wrote: >> But instead of waiting for Microsoft to make the almost trivial change to >> support and advertise OAUTHBEARER on their server, which would be the >> correct long-term solution here, the short-term compromise would be for Mutt >> to recognize XOAUTH2. > I've brought this to the attention of the right people at Microsoft, and > would not bother with a short-term hack just yet. > Arnt
I just discovered, Microsoft has published instructions on using OAuth2 with IMAP to access Azure-based (="Office365") school and work accounts: https://docs.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth Unfortunately the SASL mechanism is still XOAUTH2. At this moment, imap.outlook.com still does not advertise OAUTHBEARER. Arnt, any updates from Microsoft whether OAUTHBEARER support is forthcoming? Otherwise, to be able to use Mutt to access Microsoft accounts, Mutt would need to support the nonstandard XOAUTH2. Alex
