<div dir="ltr">Fixed the receive method on A. Receive works. Thanks.<div>Laptop B has exactly the same config, does not get mail from gmail</div><div>Laptop A&B remain unable to send.</div><div>Additional suggestions?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 22, 2022 at 2:11 PM Richard <<a href="mailto:lists-claws@listmail.innovate.net">lists-claws@listmail.innovate.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
> Date: Friday, April 22, 2022 13:30:49 -0700<br>
> From: Geoffrey Leach <<a href="mailto:geoffleach.gl@gmail.com" target="_blank">geoffleach.gl@gmail.com</a>><br>
> <br>
> On Fri, Apr 22, 2022 at 11:16 AM Richard<br>
>> <br>
>> <br>
>> > Date: Friday, April 22, 2022 10:56:43 -0700<br>
>> > From: Geoffrey Leach <<a href="mailto:geoffleach.gl@gmail.com" target="_blank">geoffleach.gl@gmail.com</a>><br>
>> > <br>
>> > Back to the grind (sigh). Two laptops, both with up-to-date<br>
>> > Fedora 35, both with internet access via (the same) Starlink<br>
>> > connection. Following setup of OAuth2 in Claws 4.0 send and<br>
>> > receive worked on both. Now both fail for both send and receive.<br>
>> > Both laptops have working gmail accounts, but with different<br>
>> > logins.<br>
>> > <br>
>> > AFAIK both laptops have the samp claus settings, although<br>
>> > different OAuth2 keys.<br>
>> > <br>
>> > Suggestions for diagnosis/repair are, as always, received with<br>
>> > gratitude.<br>
>> > <br>
>> > Laptop A receive<br>
>> > * Account 'gmail': Connecting to POP3 server:<br>
>> > pop.gmail.com:995... [2022-04-22 10:38:07] POP< +OK Gpop ready<br>
>> > for requests from 98.97.35.176 u197mb190363244jau<br>
>> > [2022-04-22 10:38:07] POP> USER <a href="http://geoffleach.gl" rel="noreferrer" target="_blank">geoffleach.gl</a><br>
>> > [2022-04-22 10:38:07] POP< +OK send PASS<br>
>> > [2022-04-22 10:38:07] POP> PASS ********<br>
>> > [2022-04-22 10:38:09] POP< -ERR [AUTH] Username and password not<br>
>> > accepted. *** error occurred on authentication<br>
>> > *** Authentication failed.<br>
>> > Laptop A send - uplink at 100%<br>
>> > * OAuth2 obtaining access token using refresh token<br>
>> > * OAuth2 access token obtained<br>
>> > * OAuth2 access token updated<br>
>> > * Account 'gmail': Connecting to SMTP server:<br>
>> > smtp.gmail.com:25... *** Session timed out. You may be able to<br>
>> > recover by increasing the timeout value in<br>
>> > Preferences/Other/Miscellaneous.<br>
>> > <br>
>> > Laptop B receive same as Laptop a<br>
>> > <br>
>> > Laptop B receiv* OAuth2 obtaining access token using refresh<br>
>> > token * OAuth2 access token not obtained<br>
>> > * OAuth2 access token not obtained<br>
>> > * Account 'gmail': Connecting to SMTP server:<br>
>> > smtp.gmail.com:465... [2022-04-22 09:05:29] SMTP< 220<br>
>> > <a href="http://smtp.gmail.com" rel="noreferrer" target="_blank">smtp.gmail.com</a> ESMTP<br>
>> > nt22-20020a17090b249600b001<br>
>> > [2022-04-22 09:05:29] ESMTP> EHLO webster<br>
>> > [2022-04-22 09:05:29] ESMTP< <a href="http://250-smtp.gmail.com" rel="noreferrer" target="_blank">250-smtp.gmail.com</a> at your service,<br>
>> > [98.97.35.176]<br>
>> > [2022-04-22 09:05:29] ESMTP< 250-SIZE 35882577<br>
>> > [2022-04-22 09:05:29] ESMTP< 250-8BITMIME<br>
>> > [2022-04-22 09:05:29] ESMTP< 250-AUTH LOGIN PLAIN XOAUTH2<br>
>> > PLAIN-CLIENTTOKEN OAUT<br>
>> > [2022-04-22 09:05:29] ESMTP< 250-ENHANCEDSTATUSCODES<br>
>> > [2022-04-22 09:05:29] ESMTP< 250-PIPELINING<br>
>> > [2022-04-22 09:05:29] ESMTP< 250-CHUNKING<br>
>> > [2022-04-22 09:05:29] ESMTP< 250 SMTPUTF8<br>
>> > [2022-04-22 09:05:29] ESMTP> [AUTH XOAUTH2]<br>
>> > [2022-04-22 09:05:29] ESMTP< 334<br>
>> > eyJzdGF0dXMiOiI0MDAiLCJzY2hlbWVzIjoiQmVhcmVyIiw<br>
>> > [2022-04-22 09:05:29] ESMTP> MAIL FROM:<<a href="mailto:SUSLEA491@GMAIL.COM" target="_blank">SUSLEA491@GMAIL.COM</a>><br>
>> > SIZE=354 [2022-04-22 09:05:29] SMTP< 535-5.7.8 Username and<br>
>> > Password not accepted. Learn<br>
>> > [2022-04-22 09:05:29] SMTP< 535 5.7.8<br>
>> > <a href="https://support.google.com/mail/?p=BadCre" rel="noreferrer" target="_blank">https://support.google.com/mail/?p=BadCre</a><br>
>> > ** error occurred on authentication -- timeout<br>
>> > *** Authentication failed:<br>
>> <br>
>> <br>
>> Based on these log snippets, it appears that<br>
>> <br>
>> on laptop A ...<br>
>> <br>
>> - you are using an id/pw, not OAuth2, for pop (port 995) email<br>
>> retrieval.<br>
>> - for sending you are using OAuth2, but are are trying to<br>
>> connect to port 25, rather than 465. that will fail.<br>
>> <br>
>> on laptop B<br>
>> - there was no retrieval attempt,<br>
>> - you tried, but failed, to get an OAuth2 token for sending<br>
>> (on port 465).<br>
>> - it seems to fall back to id/pw, which failed, when OAuth2<br>
>> fails.<br>
>> <br>
><br>
> OK. How would I manage to use an id/pw?<br>
><br>
<br>
On the account/send and receive configuration pages there's an<br>
"authentication method" pop-down button (in the middle and top<br>
respectively) where you set the authentication selection for the<br>
account. These are set independently, and for gmail should (assuming<br>
you're trying to use OAuth2 rather than app-passwords) be set to<br>
"oauth2".<br>
<br>
The actual oauth2 setup and configuration is a separate option toward<br>
the bottom of the list of the account configuration options.<br>
<br>
[please reply (only) to the list. do not include my direct email<br>
address. ... and ideally, please don't top-post.]<br>
<br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.claws-mail.org" target="_blank">Users@lists.claws-mail.org</a><br>
<a href="https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users</a><br>
</blockquote></div>