After I upgraded to this version there has been a steady occurrence of connection errors from my main google account. After I upgraded, it asked me to go through the oauth authentication with a couple of the email accounts. I did that. And then I started receiving these errors. I’ve never had them before. The error is:
“Main: Connecting to Main failed
[SMTP] An atempt to connect to Main failed. This could be caused by temporary server unavailability or incorrect settings. Do you want to check the settings?”
I’m still able to receive and send email, so perhaps these are errors that previously were silently ignored by emclient? Or is it related to a new way of authenticating? This version though is quite insistent on showing me them and for me to explicitly mark them as “Ignored” or for me to check the settings, which is quite annoying because things seem to function fine.
Log snippet:
16:32:34 Main [SMTP] MailClient.Accounts.ConnectionException: Connection failed due to the following reason:
"{“status”:“invalid_request”,“scope”:"https://mail.google.com/“}”
—> MailClient.Authentication.SaslException: {“status”:“invalid_request”,“scope”:“https://mail.google.com/”}
at MailClient.Authentication.Mechanisms.OAuthBearerMechanism.Client.EvaluateChallenge(Byte challenge)
at MailClient.Protocols.Smtp.SmtpSendCommand.Authenticate(WorkerStatus status)
at MailClient.Protocols.Smtp.SmtpSendCommand.Connect(WorkerStatus status)
— End of inner exception stack trace —
at MailClient.Protocols.Smtp.SmtpSendCommand.Connect(WorkerStatus status)
at MailClient.Protocols.Smtp.SmtpSendCommand.Execute(WorkerStatus status)
at MailClient.Commands.Command.Process(WorkerStatus status)
— End of stack trace from previous location —
at MailClient.Accounts.AccountManager.SendAsync(IAccount account, CancellationToken cancellationToken)
at MailClient.Reminders.ReminderManager.TimerSendLaterTrigger(Object sender, ElapsedEventArgs e)