[Users] Gmail OAuth2 Authorization Errors

[Dustin Miller]

On Thu, 14 Apr 2022 11:24:13 -0700
Geoffrey Leach <geoff at hughes.net> wrote:

> Dustin, many thanks.
> 
DM: You're welcome, Geoffrey; glad you got it to work. :) Cheers,
---Dustin
> 
> I cleared the Basic and Send password fields, the redid the
> authorization stel. Then punched the 'complete' button, and the
> password showed up in Basic and Receive. Test mail completed
> perfectly.
> 
> So, I conclude that I missed the f=very last step. Thanks again.
> 
> 
> On Thu, 14 Apr 2022 09:40:07 +0600
> Dustin Miller <dustbiz at gmail.com> wrote:
> 
> > On Wed, 13 Apr 2022 19:40:56 -0700
> > Geoffrey Leach <geoff at hughes.net> wrote:
> >   
> > > On the OAuth2 panel, Client Id, Client Secret and Authorization
> > > Code are as obtained from Google.
> > >     
> > DM: After removing your normal Gmail account passwords as mentioned
> > above, on the 'OAuth2' panel, did you click on the 'Authorize' in
> > the 'Complete authorization' section? This is what populates the two
> > 'Password' field with the OAuth2 'password'. You can check this by
> > going back to the 'Basic' and 'Send' panels. If the password fields
> > there are empty, it won't work; if they show a long string of dots
> > and then when you click to show the password, a long string of
> > miscellaneous characters, then that means that part of the setup is
> > okay.  
> > > 
> > > 
> > >  On Wed, 13 Apr 2022 13:28:25 +0600
> > > Dustin Miller <dustbiz at gmail.com> wrote:
> > >     
> > > > On Tue, 12 Apr 2022 16:31:58 -0700
> > > > Geoffrey Leach <geoff at hughes.net> wrote:
> > > >       
> > > > > Another bump in the road. Network log below.
> > > > > 
> > > > > Suggestions as to how to resolve the problem?
> > > > >         
> > > > DM: Hi, Geoffrey. Am I understanding right that you are trying
> > > > to use your Gmail login password in one or more of the password
> > > > fields in the Claws Mail settings? Note that if you are using
> > > > OAuth2, then you should not manually enter anything in these
> > > > password fields, since the OAuth2 setup / authorization process
> > > > will populate these for you. So try just leaving them empty,
> > > > then go through the OAuth2 setup process, and then go back and
> > > > check them to make sure they've been auto-populated. If they
> > > > have, then I think things should work as expected for you. HTH,
> > > > ---Dustin