From: Deus Max <deusmax@gmx.com>
To: 41386@debbugs.gnu.org
Cc: "Björn Bidar" <bjorn.bidar@thaodan.de>,
"Thomas Fitzsimmons" <fitzsim@fitzsim.org>
Subject: bug#41386: 28.0.50; Gnus nnimap OAuth 2.0 support
Date: Sun, 30 Oct 2022 14:22:24 +0200 [thread overview]
Message-ID: <87v8o1tsan.fsf@aia00820.aia.gr> (raw)
In-Reply-To: <87czaawsag.fsf@thaodan.de> ("Björn Bidar via \"Bug reports for GNU Emacs, the Swiss army knife of text editors\""'s message of "Sat, 29 Oct 2022 18:36:41 +0300")
On Sat, Oct 29 2022, Björn Bidar via "Bug reports for GNU Emacs, the Swiss army knife of text editors" wrote:
> I know this bug is marked as wontfix however more and more providers are
> moving to Oauth2, even those that use plain standards like
> imap/{cal,card}dav/smpt, thous increasing the importance of Oauth2
> support in Gnus.
>
Ditto. OAuth2 authentication is now needed, not just nice to have.
Please re-open ticket.
> Some providers like Microsoft require it next year and the employer
> can already enforce the use of Oauth2 [1].
> The argument "just use another email provider" doesn't really work in
> such cases.
Microsoft disabled Basic Authentication for POP, IMAP and other
protocols on Oct. 01, 2022. As you may know, a lot of work places use
office365.
https://answers.microsoft.com/en-us/outlook_com/forum/all/imap-password-not-working/d4432df0-f7ea-42b7-90e7-2cf1e0e02e4a
My understanding from reading M$ documentation is that now OAuth2 is the
only method for a client to connect to office365 IMAP. Correct me please
if I'm wrong.
>
> Without proper OAuth2 support there is no use for Gnus for such users,
> except to try third party solutions that can help.
>
Sadly true.
prev parent reply other threads:[~2022-10-30 12:22 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 2:05 bug#41386: 28.0.50; Gnus nnimap OAuth 2.0 support Thomas Fitzsimmons
2020-05-19 12:46 ` Lars Ingebrigtsen
2020-05-19 12:58 ` Noam Postavsky
2020-05-19 13:12 ` Lars Ingebrigtsen
2020-05-20 4:02 ` Richard Stallman
2020-05-19 15:37 ` Thomas Fitzsimmons
2020-05-19 16:00 ` David Engster
2020-05-19 16:12 ` Lars Ingebrigtsen
2020-05-20 3:59 ` Richard Stallman
2020-05-20 13:32 ` Stefan Kangas
2020-05-20 16:16 ` Thomas Fitzsimmons
2020-05-21 3:45 ` Richard Stallman
2020-07-19 1:29 ` Lars Ingebrigtsen
2020-07-20 2:40 ` Richard Stallman
2020-08-10 16:13 ` Simon Leinen
2020-08-11 3:28 ` Richard Stallman
2020-08-11 20:56 ` Simon Leinen
2020-05-22 3:07 ` Richard Stallman
2020-05-22 8:28 ` David Engster
2020-05-20 3:53 ` Richard Stallman
2020-05-20 14:05 ` Thomas Fitzsimmons
2020-05-21 3:47 ` Richard Stallman
2020-05-21 14:30 ` Thomas Fitzsimmons
2020-05-22 3:09 ` Richard Stallman
2020-05-23 15:49 ` Thomas Fitzsimmons
2020-05-24 3:54 ` Richard Stallman
2020-05-24 14:35 ` Thomas Fitzsimmons
2020-05-25 4:38 ` Richard Stallman
2020-07-23 4:07 ` Richard Stallman
2020-07-23 13:22 ` Lars Ingebrigtsen
2020-07-24 3:33 ` Richard Stallman
2020-07-24 14:54 ` Lars Ingebrigtsen
2020-07-25 3:49 ` Richard Stallman
2020-07-27 21:55 ` Lars Ingebrigtsen
2020-07-30 0:39 ` 황병희
2020-07-30 3:04 ` Richard Stallman
2022-10-29 15:36 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-30 12:22 ` Deus Max [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8o1tsan.fsf@aia00820.aia.gr \
--to=deusmax@gmx.com \
--cc=41386@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=dias@badekas.org \
--cc=fitzsim@fitzsim.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).