Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: gmail+imap+smtp (oauth2)
Date: Tue, 17 May 2022 18:29:19 +0200	[thread overview]
Message-ID: <87bkvw6s2o.fsf@mat.ucm.es> (raw)
In-Reply-To: <878rr86nqn.fsf@t14.reltub.ca>

[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]

>>> "LB" == Leo Butler <leo.butler@umanitoba.ca> writes:
Hello Leo

> Hello Uwe,
> I find myself in a similar bind to yours. My employer recently switched
> to 2FA and Gmail will phase out app passwords sometime soon.

Ooops do you know for sure that app passwords will be disabled, soon.

> In the interim, I use davmail to manage 2FA with my employer's microsoft
> exchange server. It is brutally slow, so I am searching for
> alternatives.

> According to
> https://www.masteringemacs.org/article/whats-new-in-emacs-28-1
> oauth2.el support has been integrated into smtpmail and gnus.

> I am running debian testing's stock emacs[1], and I haven't tried
> version 28.1.

> Perhaps someone else has tried using the oauth2 library? Any tips would
> be appreciated.

I have had an exchange with the author of oauth2, he says basically that
google again changed its mechanism and oauth2 needs to be adapted. He
also pointed out that if you applied for google dev account, then the
hassle is minor, but if you start a new one, things might get
complicated. 

I am at the end of the academic year so I would like to start to
give  oauth2 a try in July


Uwe 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

      parent reply	other threads:[~2022-05-17 16:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02  6:45 Uwe Brauer
2022-05-02 11:33 ` Eric S Fraga
2022-05-03  5:57   ` Uwe Brauer
2022-05-03  6:27     ` Tassilo Horn
2022-05-03  6:33     ` Byung-Hee HWANG
2022-05-03  7:52     ` Eric S Fraga
2022-05-03 17:37   ` Bob Newell
2022-05-04  8:53     ` Eric S Fraga
2022-05-04 14:02     ` George Clemmer
2022-05-04 15:34       ` Uwe Brauer
2022-10-24  8:20     ` Jarmo Hurri
2022-10-24 17:13       ` Bob Newell
2022-10-25  7:36         ` Jarmo Hurri
2022-10-25  8:33           ` Eric S Fraga
2022-10-25 18:26           ` Bob Newell
2022-05-03  0:57 ` Byung-Hee HWANG
2022-05-11 16:24   ` Leo Butler
2022-05-13  8:50     ` Eric S Fraga
2022-05-17 16:29     ` Uwe Brauer [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bkvw6s2o.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=ding@gnus.org \
    /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 NNTP newsgroup(s).