Dear all,
I am hitting some issues when fetching email using isync/mbsync with xoauth2 authentication. Here's a positive control, an example that works as expected: $ guix shell isync -- mbsync gmail Channels: 1 Boxes: 7 Far: +0 *0 #0 -0 Near: +0 *0 #0 -0 This one is a negative control, an example that shouldn't not work, because it requires xoauth2 authentication: $ guix shell isync -- mbsync uclouvain 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 GS2-IAKERB GS2-KRB5 GSSAPI GSS-SPNEGO DIGEST-MD5 EXTERNAL OTP CRAM-MD5 PLAIN LOGIN ANONYMOUS However, adding cyrus-sasl-xoauth2, I would expect it to work $ guix show cyrus-sasl-xoauth2 name: cyrus-sasl-xoauth2 version: 0.2 outputs: + out: everything systems: x86_64-linux i686-linux dependencies: [email protected] [email protected] [email protected] [email protected] location: gnu/packages/cyrus-sasl.scm:98:2 homepage: https://github.com/moriyoshi/cyrus-sasl-xoauth2 license: Expat synopsis: XOAUTH2 plugin for Cyrus SASL description: The cyrus-sasl-xoauth2 plugin adds support for XOAUTH2 authentication to Cyrus + SASL. Install this package with the isync package to enable fetching mail from IMAP servers + advertising XOAUTH2 support. ... but it does not, with the same error ... $ guix shell isync cyrus-sasl-xoauth2 -- mbsync uclouvain 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 GS2-IAKERB GS2-KRB5 GSSAPI GSS-SPNEGO DIGEST-MD5 EXTERNAL OTP CRAM-MD5 PLAIN LOGIN ANONYMOUS As if cyrus-sasl-xoauth2 wasn't used at all. The config file should be valid, as mbsync works on an Ubuntu machine [0]. Any idea? Laurent [0] I get the same issue on that machine that uses guix as package manager.
