[Users] Gmail OAuth2 Authorization Errors

[Dustin Miller]

On Thu, 14 Apr 2022 07:17:09 +0100
Rosemary Lockie via Users <users at lists.claws-mail.org> wrote:

> On Wed, 13 Apr 2022 12:02:01 +0000.
> "David Fletcher" <David at megapico.co.uk> wrote: 
> 
> > Hi Dustin, Richard, Rosemary, Brian,
> > 
> > Here's the info on fixing the Google Oauth2 deprecation issue (I'm
> > assuming you are compiling Claws Mail from source):  
> 
> > (4) Oauth2 authorization - Use the normal Open default browser
> > button, or copy the code to your browser. Go through the Google
> > authorization process as normal. After completing this Google will
> > forward you to a web page that does not exist (see example screen
> > attached). Copy the authorization code out of the URL and into the
> > Claws Mail Authorization Code box. Make sure to copy just the code,
> > not the whole URL, e.g. from the URL
> > https://127.0.0.1:8888/?code=4/0AX4XfWiLeoP0OglH3-VeEIokX7Bm12L895CkWPlKqF3PkvqlhBtrjs7Aikxj_JeDk-xexQ&scope=https://mail.google.com/
> > 
> > The code is this part:
> > 4/0AX4XfWiLeoP0OglH3-VeEIokX7Bm12L895CkWPlKqF3PkvqlhBtrjs7Aikxj_JeDk-xexQ
> > 
> > This is actually the way Microsoft Outlook and Exchange
> > authorization works already.  
> 
> RL: And, presumably Thunderbird (Firefox's eMail client), since I
> understand that also handles OAuth2 without user intervention.
> 
DM: Rosemary, I'm pretty sure David actually means the way in which the
Microsoft-related authorization works within Claws Mail, since it's not
quite the same as with Google, but it does still require user
intervention. ---Dustin