[Users] Authorization error after setting up OAuth2

[Little Girl]

Hey there,

Geoffrey Leach wrote:

>FWIW, you might add to this excellent report: claws-mail version and
>the contents of the CM Network log.

Ah, sorry about that. Here are some of the details:
	* Claws Mail 4.0.0
	* Kubuntu 22.04 LTS (always fully updated)
	* Certificate for receiving:
	  ~/.claws-mail/certs/pop.gmail.com.995.cert
	* Certificate for sending:
	  ~/.claws-mail/certs/smtp.gmail.com.587.cert

I believe the certificates came with Claws Mail, because I don't
remember manually downloading or creating them. Also, I didn't
include a network log because this was an invalid certificate rather
than a network error.

>My $0.02 - what happens if you accept the invalid certificate?

No idea, but I was too chicken to try. What would happen if I
accepted an invalid certificate? I assume that would be some sort of
security risk.

At any rate, this is totally bizarre. On a whim, I decided to put my
Claws Mail "Receive" and "Send" and "OAuth2" tabs back the way they
were prior to the new OAuth2 settings (but left the new Google API
console settings as is). Just for the heck of it and not at all
expecting it to work, I tried checking my email. To my great
surprise, I got all these messages.

I have no idea why it's suddenly working again without OAuth2 being
set up, but I'll take it. As you can imagine, I'll be equally as
surprised if all of these replies that I'm writing also succeed in
sending, but will also take that with pleasure as well. Meanwhile,
I'm keeping Leon Fisk's solution on the back burner, but close at
hand, in case all of this stops working again.

-- 
Little Girl

There is no spoon.