git/list[1] front-page[2] threads[3] people[4] search[5] about
 

RE: [RFC] imap-send: support oauth2

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Jun 4, 2021, 13:51 UTC
Message-ID
<60ba2ff3cff23_f62a62081b@natae.notmuch>
In-Reply-To
<ca1da892-f8ad-d878-a516-de5b08a99698@suse.com>
Nicolas Morey-Chaisemartin wrote:
> 2FA/OAuth2 becoming a more and more regular thing these days (and a lot of SUSE devs being recently impacted by it), I've thrown together a quick patch
> to allow imap-send to support it.
> This uses https://github.com/jeffmahoney/oauth2-clientd. It can be used with Outlook365 or Gmail. It creates a file with a token to be used to authenticate.
> As libcurl supports this type of authentication, it is quite easy from there.

While trying to implement this is nice, it takes way more effort just to get a client id and secret than it takes to setup an app password.

Plus I think this is abusing Google Cloud Platform. The point is to register an application once, and that application can have thousands of users, not thousands of users registering thousands of applications each used by a single user.

If you have an email service with OAuth2 authentication that doesn't require a client secret, then yeah; OAuth2 makes sense. I am not aware of any popular one though.

Cheers.
-- 
Felipe Contreras
Previous: Nicolas Morey-Chaisemartin
Message 2 of 2 in “[RFC] imap-send: support oauth2”
  1. Nicolas Morey-ChaisemartinJun 4, 2021
  2. Felipe ContrerasJun 4, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.