Re: [Imap-protocol] CLIENTID capability for IMAP (and SMTP)

--===============5408793696197521420==
Content-Type: multipart/alternative; boundary="00000000000093a7540585669e9c"

--00000000000093a7540585669e9c
Content-Type: text/plain; charset="UTF-8"

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 <[email protected]> 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
> [email protected]
> http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
>

--00000000000093a7540585669e9c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Although I don&#39;t work on the Gmail imap anymore, I wi=
ll say that we implemented a competing idea (AUTH LOGIN-CLIENTTOKEN), thoug=
h we eventually decided to concentrate on OAUTHBEARER.=C2=A0 OAUTH authoriz=
es each client separately, so provides the same client based benefits.<div =
dir=3D"auto"><br></div><div dir=3D"auto">If this became standard, we could =
implement it, but I haven&#39;t really seen consensus on it yet, or adoptio=
n by a working group.=C2=A0 When it matures, we would need to look at how m=
any &#39;legacy&#39; auth users we have , and the benefits to that populati=
on.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Brandon</div></div><=
br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat,=
 Mar 30, 2019, 11:11 AM Gene Smith &lt;<a href=3D"mailto:[email protected]"=
>[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">T=
hunderbird has recently received a patch to add a CLIENTID capability <br>
which can be seen here: <br>
<a href=3D"https://bugzilla.mozilla.org/show_bug.cgi?id=3D1532388" rel=3D"n=
oreferrer noreferrer" target=3D"_blank">https://bugzilla.mozilla.org/show_b=
ug.cgi?id=3D1532388</a>.<br>
<br>
This includes links to the draft RFCs for IMAP and SMTP. I have been <br>
unable to find any other information on this feature. Is it supported or <b=
r>
plaanned to be supported on any other IMAP or SMTP server?<br>
<br>
-gene<br>
_______________________________________________<br>
Imap-protocol mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank" rel=3D"=
noreferrer">[email protected]</a><br>
<a href=3D"http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol=
" rel=3D"noreferrer noreferrer" target=3D"_blank">http://mailman13.u.washin=
gton.edu/mailman/listinfo/imap-protocol</a><br>
</blockquote></div>

--00000000000093a7540585669e9c--

--===============5408793696197521420==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Imap-protocol mailing list
[email protected]
http://mailman13.u.washington.edu/mailman/listinfo/imap-protocol
--===============5408793696197521420==--