I got "IMAP error: selected SASL mechanism(s) not available" when something somewhere didn't like my sasl plugin. I got around it by installing cyrus-sasl-xoauth2 from Github then reinstalling isync. Here is a summary I wrote at the time for colleagues (and myself): https://people.maths.bris.ac.uk/~mb13434/linux_m_uob/o365_imap_smtp.html
I've been using O365 + isync + neomutt ever since. Best wishes, Marton On Wed, Dec 07, 2022 at 11:59:05AM +0000, Mario Župan wrote: > [...] > IMAPAccount ftrr > Host outlook.office365.com > User mym...@ftrr.hr > AuthMechs XOAUTH2 > PassCmd "/home/mario/Documents/mutt_oauth2.py /home/mario/Documents/ > office-token" > CertificateFile /etc/ssl/certs/ca-certificates.crt > TLSType IMAPS > > #Remote storage > IMAPStore ftrr-remote > Account ftrr > > # Local storage > MaildirStore ftrr-local > Path ~/Mail/ftrr/ > Inbox ~/Mail/ftrr/Inbox > Subfolders Verbatim > > > Channel ftrr-inbox > Far ":ftrr-remote:INBOX" > Near ":ftrr-local:Inbox" > > > I got: > IMAP error: selected SASL mechanism(s) not available; > selected: XOAUTH2 > available: SCRAM-SHA-512 SCRAM-SHA-384 SCRAM-SHA-256 SCRAM-SHA-224 > SCRAM-SHA-1 DIGEST-MD5 EXTERNAL CRAM-MD5 NTLM PLAIN LOGIN ANONYMOUS > > Could you please help me with th config file. > > Thank you in advance > > Mario > > _______________________________________________ > 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
