[Users] Gmail OAuth2 Authorization Errors

[Rosemary Lockie]

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):

RL: No I'm not compiling from source, I'm a Windows User, and never ventured that far, but
now it seems I have an incentive! :-) 

Thank you so much for the work you've done on this.
> 
> (1) Replace
>     "urn:ietf:wg:oauth:2.0:oob",
> with
>    "https://127.0.0.1:8888",
> on line 50 of claws-mail/src/oauth2.c
> 
> (2) Compile Claws Mail as normal.
> 
> (3) Set up your account as normal.
> 
> (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.
> 
> Longer term this can be improved to make it more automated and remove
> this copy/paste stage, but in the immediate term this fixes the
> deprecation issue with Gmail.

RL: Thank you again! :)

Kind Regards,
Rosemary Lockie