41 lines
1.7 KiB
Plaintext
41 lines
1.7 KiB
Plaintext
MBOX-Line: From blong at google.com Sun Mar 31 09:44:23 2019
|
|
To: imap-protocol@u.washington.edu
|
|
From: Brandon Long <blong@google.com>
|
|
Date: Sun Mar 31 09:44:40 2019
|
|
Subject: [Imap-protocol] CLIENTID capability for IMAP (and SMTP)
|
|
In-Reply-To: <8cade395-864a-9039-6bfa-874c26e5967e@chartertn.net>
|
|
References: <8cade395-864a-9039-6bfa-874c26e5967e@chartertn.net>
|
|
Message-ID: <CABa8R6ufcJ9GimEoLrFkKnMCh14n5+VK3uN-++f4tE-qfPW-7g@mail.gmail.com>
|
|
|
|
Although I don't work on the Gmail imap anymore, I will say that we
|
|
implemented a competing idea (AUTH LOGIN-CLIENTTOKEN), though we eventually
|
|
decided to concentrate on OAUTHBEARER. OAUTH authorizes each client
|
|
separately, so provides the same client based benefits.
|
|
|
|
If this became standard, we could implement it, but I haven't really seen
|
|
consensus on it yet, or adoption by a working group. When it matures, we
|
|
would need to look at how many 'legacy' auth users we have , and the
|
|
benefits to that population.
|
|
|
|
Brandon
|
|
|
|
On Sat, Mar 30, 2019, 11:11 AM Gene Smith <gds@chartertn.net> wrote:
|
|
|
|
> Thunderbird has recently received a patch to add a CLIENTID capability
|
|
> which can be seen here:
|
|
> https://bugzilla.mozilla.org/show_bug.cgi?id=1532388.
|
|
>
|
|
> This includes links to the draft RFCs for IMAP and SMTP. I have been
|
|
> unable to find any other information on this feature. Is it supported or
|
|
> plaanned to be supported on any other IMAP or SMTP server?
|
|
>
|
|
> -gene
|
|
> _______________________________________________
|
|
> Imap-protocol mailing list
|
|
> Imap-protocol@u.washington.edu
|
|
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
|
|
>
|
|
-------------- next part --------------
|
|
An HTML attachment was scrubbed...
|
|
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20190331/a3933c8d/attachment.html>
|