From: Joshua Branson <jbranso@dismail.de>
To: Peter Polidoro <peter@polidoro.io>
Cc: help-guix@gnu.org
Subject: Re: mbsync with XOAUTH2 SASL mechanism
Date: Sun, 13 Nov 2022 13:27:31 -0500 [thread overview]
Message-ID: <878rkeogks.fsf@dismail.de> (raw)
In-Reply-To: <87h6ziae15.fsf@polidoro.io> (Peter Polidoro's message of "Tue, 01 Nov 2022 11:13:55 -0400")
Peter Polidoro <peter@polidoro.io> writes:
> I am trying to setup an oauth2 email account to work with Emacs using mbsync
> (from the isync guix package) and mu4e.
>
> I setup oauth2ms to fetch the token and setup mbsync to use oauth2ms for the
> PassCmd and XOAUTH2 for the AuthMechs.
>
> Now when I run mbsync, I get the error:
>
> IMAP error: selected SASL mechanism(s) not available;
> selected: XOAUTH2
> available: SCRAM-SHA-1 SCRAM-SHA-256 GS2-IAKERB GS2-KRB5 GSSAPI GSS-SPNEGO
> DIGEST-MD5 EXTERNAL OTP CRAM-MD5 PLAIN ANONYMOUS
>
> I found instructions online saying I need to install the xoauth2 sasl plugin
> from https://github.com/moriyoshi/cyrus-sasl-xoauth2
>
> What is the proper Guix way of getting mbsync to work with XOAUTH2? Should I try
> to package cyrus-sasl-xoauth2 or modify the isync package or something else?
> Thanks!
>
Man this sounds complicated! haha. I use isync too...but I do the
really really lazy (insecure) way via ~/.authinfo.
Joshua
next prev parent reply other threads:[~2022-11-13 18:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 15:13 mbsync with XOAUTH2 SASL mechanism Peter Polidoro
2022-11-13 18:27 ` Joshua Branson [this message]
2022-11-13 19:04 ` Peter Polidoro
2022-11-13 22:00 ` Felix Lechner via
2022-11-14 23:05 ` Tobias Geerinckx-Rice
2022-11-15 15:43 ` jbranso
2023-01-24 10:04 ` Giovanni Biscuolo
2023-01-24 12:41 ` Peter Polidoro
2023-01-25 17:51 ` Timo Wilken
2023-01-26 10:19 ` Giovanni Biscuolo
2023-01-26 18:15 ` Timo Wilken
2023-01-26 10:13 ` Giovanni Biscuolo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rkeogks.fsf@dismail.de \
--to=jbranso@dismail.de \
--cc=help-guix@gnu.org \
--cc=peter@polidoro.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).