About a year ago an update on Arch broke oauth2ms for me. I moved to oama and it works fine. https://github.com/pdobsan/oama
Best wishes, Marton On Thu, Apr 03, 2025 at 05:47:28PM +0200, Bence Ferdinandy wrote: > 2025. ápr. 3. 17:41:45 Tamas Papp <tkp...@gmail.com>: > > > I have just switched from Debian to Fedora, and I am trying to get > > e-mail working with mbsync, 1.5.0 (but I also get the same error with > > master). > > > > The relevant excerpt from my .mbsync (the whole config used to work, and > > is unchanged) is > > > > IMAPAccount ihs-account > > Host outlook.office365.com > > User "tp...@ihs.ac.at" > > PassCmd "/home/tamas/bin/oauth2ms" > > AuthMechs XOAUTH2 > > TLSType STARTTLS > > # Increase timeout to avoid o365 IMAP hiccups > > Timeout 120 > > PipelineDepth 50 > > > > The relevant oauth2ms script above works fine, insofar that it spits out > > a token. > > > > Then running mbsync -V ihs I get > > > > Reading configuration file /home/tamas/.mbsyncrc > > Channel ihs > > Opening far side store ihs-remote... > > Resolving outlook.office365.com... > > Opening near side store ihs-local... > > Connecting to outlook.office365.com (52.98.250.162:143)... > > Connection is now encrypted > > Logging in... > > Authenticating with SASL mechanism XOAUTH2... > > Error performing SASL authentication step: SASL(-1): generic failure: > > Unable to find a callback: 32775 > > Maybe you are missing cyrus-sasl-xoauth2 > ? > > > > > > best > > > > Tamas > > > > > > _______________________________________________ > > 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
