Hi, Thanks for your reply, and apologies for my messy subject field.
It's still odd, since the problem only started Friday afternoon. Anyway, I fought hard to setup OAuth2 on my system a year or so ago and in the end I found another solution (forwarding all email to a free office365 account). I'm guessing this is now not allowing the AuthMechs PLAIN anymore. The top hits of "mbsync office365" are a year old or more and I have read most. I'm on a Macbook M1, using mbsync with mu4e and if someone has a hint I would be happy! I have followed this, among others https://sites.uw.edu/bxf4/2022/09/01/getting-uw-outlook-365-oauth2-to-work-with-emacs-mu4e-mbsync-and-msmtp/ but it doesn't work since I don't have Office 365 admin priveleges. Thanks! /Henrik Den mån 29 jan. 2024 kl 09:46 skrev Peter P. <peterpar...@fastmail.com>: > Henrik, > > what is your authentication method? Microsoft only allows > AuthMechs XOAUTH2 > since a few months. A startpage.com search for "mbsync office365" might > yield additional hints. > > best, P > > * Henrik Frisk <fris...@gmail.com> [2024-01-29 08:50]: > > Hi, > > > > Well aware this is not a question for the devel list I'm taking my > chances. > > After no configuration change my mbsync command started returning this > > error (not every time, but farily often): > > > > IMAP command 'AUTHENTICATE PLAIN <authdata>' returned an error: > > AUTHENTICATE failed. > > > > Any ideas that might have caused this? The server is an Office365. > > > > Best, > > Henrik > > > > _______________________________________________ > > isync-devel mailing list > > isync-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/isync-devel > > > > _______________________________________________ > isync-devel mailing list > isync-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/isync-devel >
_______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
