From: Bob Newell <bobnewell@bobnewell.net>
To: ding@gnus.org
Subject: Re: gmail+imap+smtp (oauth2)
Date: Mon, 24 Oct 2022 07:13:20 -1000 [thread overview]
Message-ID: <87fsfdb0wf.fsf@undisclosedlocation.com> (raw)
In-Reply-To: <87o7u1skek.fsf@iki.fi> (Jarmo Hurri's message of "Mon, 24 Oct 2022 11:20:03 +0300")
Jarmo Hurri <jarmo.hurri@iki.fi> writes:
> Greetings.
>
> Bob Newell <bobnewell@bobnewell.net> writes:
>
>>>> There have been some discussion, either on emacs-devel or here, how
>>>> to make emacs (gnus) work with gmail under those circumstances, that
>>>> is using oauth2.
>
>> I have read accounts of how to make oauth2 work natively with gnus,
>> but I haven't tried it and it seemed "complex and wonderful" so I'm
>> going to try app passwords first.
>
> Is there any description anywhere on how this should be set up?
>
> I wast told that Microsoft is going oauth full scale when my imap
> stopped working.
What I've been doing as an alternative is setting up
two-factor authentication and then generating an app
password. This has worked so far in all instances.
It's not an ideal solution because two-factor authentication
can be a pain when not using a client. But it's surely the
easist to implement.
Interesting however, that of my 3 M$ accounts, two require
this process but one still works with the plain old login
password. That one is a corporate account and may have to do
with the way the IT guy set it up.
--
Bob Newell
Honolulu, Hawai`i
- Via GNU/Linux/Emacs/Gnus/BBDB
next prev parent reply other threads:[~2022-10-24 17:13 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 [this message]
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=87fsfdb0wf.fsf@undisclosedlocation.com \
--to=bobnewell@bobnewell.net \
--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).