Re: KeyError: 'refresh_token' error in fetchmail-oauth2

On Wed, 13 Apr 2022, Matthias Andree wrote:

> Am 12.04.22 um 23:18 schrieb Marco Gaiarin:
> > I've followed literally:
> >
> >     https://gitlab.com/fetchmail/fetchmail/-/blob/next/README.OAUTH2
> >
> > (eg, the readme of fetchmail 7) and works as expected. Now i have to 
manage
> > some script to refresh the token, and download the email.
> >
> > I've only a question, before put all that stuff in 'production'.
> >
> > Juergen Edner say that the OAuth client created in 'Test mode' least 
at
> > maximum a week.
> > But if i try to publish the app, i need the Google approval process, 
because the api used (eg, GMAIL
> > API) is 'restricted'.
> >
> > So, it is needed to publish the app? If yes, what is the shortest and 
error
> > prone path to get it approved?
> >
> Their requiring registration of the "app" (we have never called
> fetchmail that) - and not solely the user for his or her own account -
> is one of the reasons why I say that OAUTH2 in this form is generally a
> non-starter and does not scale.
>
> I cannot possibly register fetchmail with each and every mail service,
> and device registration is somewhat pointless anyways.

There has been some discussion of fetchmail and google in the email list
for alpine - another open source MUA - particularly the thoughts
of the main alpine developer at
https://mailman12.u.washington.edu/pipermail/alpine-info/2022-April/001162.html

> So tell your mail service provider to stop that "app" registration
> nonsense. I may seem pointless, but if nobody tells them, they will
> never notice.

Good idea.

-- 
Andrew C. Aitchison                                     Kendal, UK
                         [email protected]