[Users] Gmail OAuth2 Authorization Errors (ToCM)

[Geoffrey Leach]

Hi Dustin. Thanks for the reply.

Your assumptions are correct. That was exactly what I was doing. Adding
@gmail.com to the user id shows my level of desperation.

So, I removed the (gmail) passwords from the password fields of the
Basic and Send panels of the Claws Configuration of the user I'm using
to test my understanding. The (gmail) User Id remains (without
@gmail.com).

Claws accepts this configuration, but not with empty User Id.

On the OAuth2 panel, Client Id, Client Secret and Authorization Code
are as obtained from Google.

On sending the test email, Claws prompts me for the password for
smtp.gmail.com. Entering the password for the gmail user id, results in
a network trace as before.

What did I miss?

Geoffrey

 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.
> > 
> > Username is that that was used during the registration process.
> > 
> > Password verified. I assume that '@gmail.com' is not part of the
> > password.
> > 
> > Username and password were used to log in to the gmail account, off
> > of the error diagnostic page from google.
> > 
> > The credentials were copied from the google pages using their 'copy
> > to clipboard' links. They looked correct, but I will confess that I
> > did not do a byte-by-byte comparison.
> > 
> > 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
> > 
> > Thanks.
> > 
> > * OAuth2 trying for fresh access token with auth code
> > * OAuth2 access token not obtained
> > * OAuth2 refresh token not obtained
> > * OAuth2 access token not obtained
> > * Account 'gmail': Connecting to SMTP server: smtp.gmail.com:465...
> > [2022-04-12 14:45:15] SMTP< 220 smtp.gmail.com ESMTP
> > a21-20020aa780d5000000b005059fdae5 [2022-04-12 14:45:15] ESMTP> EHLO
> > webster [2022-04-12 14:45:15] ESMTP< 250-smtp.gmail.com at your
> > service, [98.97.35.136] [2022-04-12 14:45:15] ESMTP< 250-SIZE
> > 35882577 [2022-04-12 14:45:15] ESMTP< 250-8BITMIME
> > [2022-04-12 14:45:15] ESMTP< 250-AUTH LOGIN PLAIN XOAUTH2
> > PLAIN-CLIENTTOKEN OAUTHBEARER [2022-04-12 14:45:15] ESMTP<
> > 250-ENHANCEDSTATUSCODES [2022-04-12 14:45:15] ESMTP< 250-PIPELINING
> > [2022-04-12 14:45:15] ESMTP< 250-CHUNKING
> > [2022-04-12 14:45:15] ESMTP< 250 SMTPUTF8
> > [2022-04-12 14:45:15] ESMTP> [AUTH XOAUTH2]
> > [2022-04-12 14:45:15] ESMTP< 334
> > eyJzdGF0dXMiOiI0MDAiLCJzY2hlbWVzIjoiQmVhcmVyIiwic2NvcG [2022-04-12
> > 14:45:15] ESMTP> MAIL FROM:<SUSLEA491 at GMAIL.COM> SIZE=334
> > [2022-04-12 14:45:15] SMTP< 535-5.7.8 Username and Password not
> > accepted. Learn more at [2022-04-12 14:45:15] SMTP< 535 5.7.8
> > https://support.google.com/mail/?p=BadCredential ** error occurred
> > on authentication *** Authentication failed: