MBOX-Line: From Pidgeot18 at verizon.net  Fri Aug 29 15:52:49 2014
To: imap-protocol@u.washington.edu
From: Joshua Cranmer <Pidgeot18@verizon.net>
Date: Fri Jun  8 12:34:53 2018
Subject: [Imap-protocol] Seeking clarity on Gmail "Access for less
 secure apps" setting for non XOAuth2 access
In-Reply-To: <CABa8R6se2WefF4q-cFzR2qtU_5_jDL-wioPF+jPmOTdpCaJhtw@mail.gmail.com>
References: <5400A146.4020602@mozilla.com>
	<CABa8R6se2WefF4q-cFzR2qtU_5_jDL-wioPF+jPmOTdpCaJhtw@mail.gmail.com>
Message-ID: <54010441.1040803@verizon.net>

On 8/29/2014 3:53 PM, Brandon Long wrote:
> And we did reach out to our larger clients, assuming we knew who they 
> were and how to reach out to them.... sending us the ID command is 
> certainly helpful in that instance to know who are larger clients are. 
>  We also had some discussion with Thunderbird, but assumed our 
> fallback was sufficient for clients who couldn't really switch to 
> OAUTH.  OAUTH2 is not ready for Thunderbird at this point, really, 
> since you have to pre-register to get your client-id, and then also 
> hard-code the various URLs for usage, as there is no auto-discovery 
> yet either.  Unfortunately, the bad guys aren't waiting for the 
> standards to be written.

Since this is definitely of interest to others on the list--are there 
any updates on the dynamic client registration and autodiscovery drafts 
yet? I've seen progress on the Dynamic client registration draft 
(http://tools.ietf.org/html/draft-ietf-oauth-dyn-reg-20), although I 
admit I haven't read the spec closely yet to provide feedback; but I've 
been unable to find indication of any autodiscovery work.

-- 
Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald E. Knuth


