Re: Sudden UTHENTICATE failed.
* Marton Balazs [2024-01-29 12:55]: > Thanks All, this is my page :-) great to see it's useful. While it still > works fine on my work machine running Ubuntu 20.04, some update on my Arch at > home broke something (I don't know what exactly) so at home I'm now following > Bence's excellent guides from a previous email on this thread with mailctl > instead of oauth2ms. I just noticed that installing oauth2ms requirements.txt via pip as described on [1] might fail, at least on Debian, as they updated their policy regarding python package management without setting up explicit environments. So I installed these via Debian's apt as python3-xdg python3-msal python3-gnupg. thanks again for the guide Márton! [1] https://github.com/harishkrupo/oauth2ms ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Sudden UTHENTICATE failed.
Thanks All, this is my page :-) great to see it's useful. While it still works fine on my work machine running Ubuntu 20.04, some update on my Arch at home broke something (I don't know what exactly) so at home I'm now following Bence's excellent guides from a previous email on this thread with mailctl instead of oauth2ms. Please note the part with the "little dance" if you use a corporate M365 account, that's important (and the link is to a note by our excelent sysadmin at work, David Gardner. It's a small world. :-) ). Best wishes, Marton On Mon, Jan 29, 2024 at 11:24:30AM +0100, Peter P. wrote: > * Henrik Frisk [2024-01-29 10:47]: > > [...] 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). > What OS are you on? I just succeeded using oauth2 on Debian with mbsync > following instructions from > https://people.maths.bris.ac.uk/~mb13434/linux_m_uob/o365_imap_smtp.html > > best, Peter > > > ___ > 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
Re: Sudden UTHENTICATE failed.
* Henrik Frisk [2024-01-29 10:47]: > [...] 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). What OS are you on? I just succeeded using oauth2 on Debian with mbsync following instructions from https://people.maths.bris.ac.uk/~mb13434/linux_m_uob/o365_imap_smtp.html best, Peter ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Sudden UTHENTICATE failed.
Den mån 29 jan. 2024 kl 10:58 skrev Bence Ferdinandy : > Hi Henrik, > > > On Mon Jan 29, 2024 at 10:47, Henrik Frisk wrote: > > 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. > > I would suggest trying mailctl, it usually works: > https://github.com/pdobsan/mailctl > > I have a bit written up on it for getting it working with O365: > > https://bence.ferdinandy.com/2023/07/20/email-in-the-terminal-a-complete-guide-to-the-unix-way-of-email/#oauth-mailctl > > Alternatively, if all else fails, davmail might be a solution, the aerc > wiki > has some stuff about setting it up: > https://man.sr.ht/~rjarry/aerc/providers/microsoft.md > > Thanks a lot Bence, I will try that! /Henrik ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Sudden UTHENTICATE failed.
Hi Henrik, On Mon Jan 29, 2024 at 10:47, Henrik Frisk wrote: > 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. I would suggest trying mailctl, it usually works: https://github.com/pdobsan/mailctl I have a bit written up on it for getting it working with O365: https://bence.ferdinandy.com/2023/07/20/email-in-the-terminal-a-complete-guide-to-the-unix-way-of-email/#oauth-mailctl Alternatively, if all else fails, davmail might be a solution, the aerc wiki has some stuff about setting it up: https://man.sr.ht/~rjarry/aerc/providers/microsoft.md Best, Bence -- +36305425054 bence.ferdinandy.com ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
Re: Sudden UTHENTICATE failed.
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. : > 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 [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 ' 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
Re: Sudden UTHENTICATE failed.
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 [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 ' 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
