On Tuesday, 13 August 2019 16:19:36 BST Peter Humphrey wrote: > On Tuesday, 13 August 2019 15:33:02 BST Mick wrote: > > On Tuesday, 13 August 2019 10:19:23 BST Peter Humphrey wrote: > > > I'm using my ISP's SMTP server with the same settings as usual. KMail > > > detected them itself > > > > Yes, it does the same here, when I ask it to detect what Gmail wants to > > use, ... then it fails when it tries to set up a XOAUTH2 token via > > akonadi's plugin. > > > > I succeeded by selecting manually individual authentication settings and > > trying them one at a time. > > Do you mind saying which authentication method worked?
IMAP4 Connection Settings: Protocol: SSL/TLS Port: 993 Authentication: PLAIN SMTP Settings: Protocol: STARTTLS Port: 587 Authentication: PLAIN NOTES: 1. Other combinations may have worked, but I stopped trying to figure out what works, as soon as I was able to authenticate with the server. 2. Google has some setting you can access online to enable/disable what they call 'Less Secure App' authentication. They consider the good ol' authentication protocols and ports allowing IMAP4/POP3/SMTP to connect securely with a mail server and authenticate via username/password /less/ secure. https://support.google.com/accounts/answer/6010255?hl=en Instead, they prefer we use OAUTH2 or some such pseudo-authentication mechanism, which works over HTTPS. Because browsers are more ... secure?! O_o Anyway, if you find authentication attempts are rejected by Gmail servers, try enabling "Less Secure App" authentication on your Google security settings. I've just seen these Gmail client settings, which you may find useful: https://support.google.com/mail/answer/7104828 https://support.google.com/mail/answer/7126229 -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
