From: Peter Polidoro <peter@polidoro.io>
To: Joshua Branson <jbranso@dismail.de>
Cc: help-guix@gnu.org
Subject: Re: mbsync with XOAUTH2 SASL mechanism
Date: Sun, 13 Nov 2022 14:04:51 -0500 [thread overview]
Message-ID: <10E9DE33-3EE1-45F9-A408-9D1C11CBEC46@polidoro.io> (raw)
In-Reply-To: <878rkeogks.fsf@dismail.de>
> Man this sounds complicated! haha. I use isync too...but I do the
> really really lazy (insecure) way via ~/.authinfo.
>
> Joshua
I wish I did not have to have such a complicated setup. My work email account has just stopped allowing basic password authentication, however, so I can no longer use Emacs for my work email until I figure this out.
I do not know if OAuth2 refers to something proprietary, if so I apologize for bringing it up here. My only goal is to be able to use Emacs rather than proprietary software for my work email.
I submitted a patch for a “cyrus-sasl-xoauth2” package that may allow this to work, but I do not yet know enough about Guix packaging to complete the package. If anyone has a similar problem and has advice or can help I would really appreciate it. Thanks!
next prev parent reply other threads:[~2022-11-13 19:05 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
2022-11-13 19:04 ` Peter Polidoro [this message]
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=10E9DE33-3EE1-45F9-A408-9D1C11CBEC46@polidoro.io \
--to=peter@polidoro.io \
--cc=help-guix@gnu.org \
--cc=jbranso@dismail.de \
/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).