[Users] OAUTH2 Authorisation Status

[Bernard Moreton]

Has anyone managed to get a successful (ie. stable) Production publishing status?
Changing codes every 7 days is not sustainable;  nor is every 30 days.
Google used to have a refresh code, which presumably would need activating on request;  but that seems to have dropped out of the picture ... ?

For me, freedom is more important than google, despite the pains that changing email addresses will cause.
Recommendations for reliable providers would be welcome, if we can't get reasonableness out of google!
"Do no evil"???  - they were a white knight, once ...

Sad, but best, wishes,
Bernard


On Thu, 31 Mar 2022 09:12:54 +0100
Wishful Thinking via Users <users at lists.claws-mail.org> wrote:

> Hi All,
> 
> I've been using Claws with OAuth2 enabled successfully for the last 7 days.
> 
> This morning it reported an Error condidtion, and (from the log) that:
> 
> [quote]
> * OAuth2 obtaining access token using refresh token
> * OAuth2 access token not obtained
> * OAuth2 access token not obtained
> * Account '********@gmail.com': Connecting to POP3 server: pop.gmail.com:995...
> [endquote]
> 
> So I can confirm what is suggested in the FAQ, 
> https://www.claws-mail.org/faq/index.php/Oauth2
> 
> [Note 3: " Regarding "Publishing status"" ... that is, that Authorisation with Testing
> Status apparently only lasts for seven days. ]
> 
> FWIW, I discovered the way round it is to get another Authorisation Code, so maybe all is
> well, for the next 7 days...
> 
> Has this been others' expeerience, please?
> 
> Kind Regards,
> Rosemary Lockie
> _______________________________________________
> Users mailing list
> Users at lists.claws-mail.org
> https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users