[Users] More OAuth2 problems -- SOLVED

[Geoffrey Leach]

On Sat, Apr 23, 2022 at 9:50 AM Geoffrey Leach <geoffleach.gl at gmail.com>
wrote:

> > Date: Friday, April 22, 2022 15:19:42 -0700
> > From: Geoffrey Leach <geoffleach.gl at gmail.com>
> >
> > On Fri, Apr 22, 2022 at 2:11 PM Richard wrote:
> >
> >>
> >> > Date: Friday, April 22, 2022 13:30:49 -0700
> >> > From: Geoffrey Leach <geoffleach.gl at gmail.com>
> >> >
> >> > On Fri, Apr 22, 2022 at 11:16 AM Richard
> >> >>
> >> >>
> >> >> > Date: Friday, April 22, 2022 10:56:43 -0700
> >> >> > From: Geoffrey Leach <geoffleach.gl at gmail.com>
> >> >> >
> >> >> > Back to the grind (sigh). Two laptops, both with up-to-date
> >> >> > Fedora 35, both with internet access via (the same) Starlink
> >> >> > connection. Following setup of OAuth2 in Claws 4.0 send and
> >> >> > receive worked on both. Now both fail for both send and
> >> >> > receive. Both laptops have working gmail accounts, but with
> >> >> > different logins.
> >> >>
> >> >> Based on these log snippets, it appears that
> >> >>
> >> >>   on laptop A ...
> >> >>
> >> >>   - you are using an id/pw, not OAuth2, for pop (port 995) email
> >> >>     retrieval.
> >> >>   - for sending you are using OAuth2, but are are trying to
> >> >>     connect to port 25, rather than 465. that will fail.
> >> >>
> >> >>   on laptop B
> >> >>    - there was no retrieval attempt,
> >> >>    - you tried, but failed, to get an OAuth2 token for sending
> >> >>      (on port 465).
> >> >>       - it seems to fall back to id/pw, which failed, when
> >> >>       OAuth2 fails.
> >> >>
> >> >
> >> > OK. How would I manage to use an id/pw?
> >> >
> >>
> >> On the account/send and receive configuration pages there's an
> >> "authentication method" pop-down button (in the middle and top
> >> respectively) where you set the authentication selection for the
> >> account. These are set independently, and for gmail should
> >> (assuming you're trying to use OAuth2 rather than app-passwords)
> >> be set to "oauth2".
> >>
> >> The actual oauth2 setup and configuration is a separate option
> >> toward the bottom of the list of the account configuration
> >> options.
> >
> > Fixed the receive method on A. Receive works. Thanks.
> > Laptop B has exactly the same config,   does not get mail from gmail
> > Laptop A&B remain unable to send.
> > Additional suggestions?
> >
>
> On laptop A OAuth2 seemed ok, but it was trying to send on port 25.
> That won't work with gmail.
>
> Laptop B was failing on OAuth2, so seemed to be falling back to id/pw.
>
> You should look at the OAuth2 setup (keys and such) on laptop B, and
> the port being used to send on laptop A. ... if things still don't
> work, please provide new log output.
>
> Sorry for the indents being off -- I'm struggling with Gmail :(
>
> OK. So I've cleaned up my configuration, and the ports are correct
> (hopefully).  Receive is working, and gmail appears to know about me.  On
> the send sde, here's what I see:
> * OAuth2 access token still fresh
> * Account 'gmail': Connecting to SMTP server: smtp.gmail.com:465...
> *** Connection closed by the remote host.
>
> On my Configuration->Send page, SMTP Authentication is SMTP AUTH, and
> OAUTH2 is selected. I assume that if Receive works, than the OAUTH2 page
> settings are correct.
>
> Any suggestions?  Thanks.
>

Solved - on the SSL/TLS page, "Use SSL/TLS" was not selected. Now all is
well.
Many thanks to all that contributed.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20220423/19b1b448/attachment-0001.htm>