[Users] Check and correct your OAuth2 account preferences

[Geoffrey Leach]

On Wed, 25 May 2022 18:57:44 -0700
Michael Higgins <mykhyggz at gmail.com> wrote:

> So, this worked *yesterday*. Any clue as to what to do now?
> 
> <error msg>
> 
> 
> Connection to imap.gmail.com failed: login refused.
> 
> OAuth2 error. Check and correct your OAuth2 account preferences.
> 
> </error msg>
> 
> <network log>
> 
> * Account 'gmail': Connecting to IMAP server: imap.gmail.com:993...
> [2022-05-25 18:47:28] IMAP< * OK Gimap ready for requests from
>   2601:1c2:501:51c0:3051:4d7f:ce9a:c116 mt15mb15743790pjb 
> * IMAP connection is un-authenticated
> * OAuth2 obtaining access token using refresh token
> * OAuth2 access token not obtained
> * OAuth2 replacement refresh token not provided
> * OAuth2 access token not obtained
> [2022-05-25 18:47:29] IMAP> 1 CAPABILITY 
> [2022-05-25 18:47:29] IMAP< * CAPABILITY IMAP4rev1 UNSELECT IDLE
>   NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR
>   AUTH=XOAUTH2 AUTH=PLAIN AUTH=PLAIN-CLIENTTOKEN AUTH=OAUTHBEARER
>   AUTH=XOAUTH [2022-05-25 18:47:29] IMAP< 1 OK Thats all she wrote!
>   mt15mb15743790pjb [2022-05-25 18:47:29] IMAP> Logging mykhyggz to
>   imap.gmail.com using XOAUTH2 [2022-05-25 18:47:30] IMAP< Invalid
>   credentials (Failure) ** IMAP error on imap.gmail.com: LOGIN error
>   [2022-05-25 18:47:30] IMAP< Error logging in to imap.gmail.com
>   [2022-05-25 18:47:34] IMAP> 3 LOGOUT [2022-05-25 18:47:34] IMAP< *
>   BYE Logout Requested mt15mb15743790pjb [2022-05-25 18:47:34] IMAP< 3
>   OK Quoth the raven, nevermore... mt15mb15743790pjb 
> 
> </network log>
> 
> Since I subscribed to the ML with my gmail addy, well... this is
> inconvenient to say the least. Meh. 
> 
> . . .
> 
> So I did get a new code, using the edit accounts stuff. It allowed me
> to log in. I did this just two days ago! Fsck Google.
> 
> Just want this to work long enough to change my email connect to a new
> server that I run, but at my own pace. (That way I can continue to use
> my favorite client, with no google hassles.) 
> 
> Refreshing the, what, token[?] weekly was a hassle, but if I must do
> so every frigging time... not OK.
> 
> Anyone have any thoughts as to what changed *this time*? 
> 

My experience. I've used all of these at one time.

On the OAuth2 page. Re-request authorization, using the key that you
have. If that fails, get a new key. Failing that, go to the API console
and make yourself a new ClientID/ClientSecret, retaining the existing
settings.

One observation. I have two laptops on separate gmail accounts. The
other day one (just one) was unable to connect for 20-or so hours. The
problem then went away.