Gnus development mailing list
 help / color / mirror / Atom feed
From: George Clemmer <myglc2@gmail.com>
To: Bob Newell <bobnewell@bobnewell.net>
Cc: Eric S Fraga <e.fraga@ucl.ac.uk>, ding@gnus.org
Subject: Re: gmail+imap+smtp (oauth2)
Date: Wed, 04 May 2022 10:02:21 -0400	[thread overview]
Message-ID: <851qx9gzv6.fsf@gmail.com> (raw)
In-Reply-To: <877d7234bl.fsf@undisclosedlocation.com>

Bob Newell <bobnewell@bobnewell.net> writes:
[..]
>
> The option I intend to try when the time comes (I have a
> Workspace account and the deadline hasn't been announced yet)
> is app passwords. These are available if you're willing to put
> up with the initial hassle of two-factor authentication.
> Fortunately you can mark a device as trusted and only have to
> deal with the two-factor authentication one time per device.
>
I switched to two-factor + app passwords which works well.  However, I
have read rumors that app passwords will be phased out too.  Does anyone
know if/when this might happen? TIA George

PS Sorry for going further off topic, but you started it ;-)



  parent reply	other threads:[~2022-05-04 14:02 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 [this message]
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

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=851qx9gzv6.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=bobnewell@bobnewell.net \
    --cc=ding@gnus.org \
    --cc=e.fraga@ucl.ac.uk \
    /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).