fetchmail-users

[Fetchmail-users] OAuth2 authenticator problem

[Robin A. <ro...@bi...>]

I saw the message from Gmail saying that using apps like fetchmail
would stop working on 30/05/2022. Searching showed that OAuth2
support was included in fetchmail-7.0.0-alpha so I installed it. Setting
up the oauth2 script was straightforward enough but I had a bit of a
tussle getting registered with Google! Eventually I could kick off
fetchmail and receive my mail. Thank you Matthew Ogilvie!

But (you knew this was coming :)) after about a day I started getting
fetchmail messages:

Mar 20 22:19:36 localhost fetchmail[29377] We've run out of allowed authenticators and cannot co
ntinue.
Mar 20 22:19:36 localhost fetchmail[29377] Authorisation failure on
xx...@gm...@pop.gmail.com (previously authorised)

I searched on this but couldn't find anything; I guess not a lot of
people are doing this. Have I left out some admin step? I have the
usual 10000 tokens per day available. I have a cron job refreshing my
access token.

Thanks
Robin
-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------

Re: [Fetchmail-users] OAuth2 authenticator problem

[Matthias A. <mat...@gm...>]

Am 21.03.22 um 14:56 schrieb Robin Atwood:
> I saw the message from Gmail saying that using apps like fetchmail
> would stop working on 30/05/2022. Searching showed that OAuth2
> support was included in fetchmail-7.0.0-alpha so I installed it. Setting
> up the oauth2 script was straightforward enough but I had a bit of a
> tussle getting registered with Google! Eventually I could kick off
> fetchmail and receive my mail. Thank you Matthew Ogilvie!
>
> But (you knew this was coming :)) after about a day I started getting
> fetchmail messages:
>
> Mar 20 22:19:36 localhost fetchmail[29377] We've run out of allowed authenticators and cannot co
> ntinue.
> Mar 20 22:19:36 localhost fetchmail[29377] Authorisation failure on
> xx...@gm...@pop.gmail.com (previously authorised)
>
That's a sign that you had left authentication set to automatic and the
XOAUTH2 or OAUTHBEARER authentication method started failing with your
server at some point. Re-obtaining a new token with the script may fix
it, else running fetchmail in verbose mode (-v or -v -v) may give you
sufficient information to pinpoint the failure.

Re: [Fetchmail-users] OAuth2 authenticator problem

[Robin A. <ro...@bi...>]

On Tue, 22 Mar 2022 09:11:34 +0100
Matthias Andree <mat...@gm...> wrote:
> > Mar 20 22:19:36 localhost fetchmail[29377] We've run out of allowed
> > authenticators and cannot co ntinue.
> > Mar 20 22:19:36 localhost fetchmail[29377] Authorisation failure on
> > xx...@gm...@pop.gmail.com (previously authorised)
> >  
> That's a sign that you had left authentication set to automatic and
> the XOAUTH2 or OAUTHBEARER authentication method started failing with
> your server at some point. Re-obtaining a new token with the script
> may fix it, else running fetchmail in verbose mode (-v or -v -v) may
> give you sufficient information to pinpoint the failure.

I ran 
oauth2 -c /path/to/oauth2Config.properties --obtain_refresh_token_file
again and now the logon proceeds. I will see how long it works, one week
seems to be the limit. If it happens again I will try publishing my app
to see if that helps.

Robin
-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------

Re: [Fetchmail-users] OAuth2 authenticator problem

[Robin A. <ro...@bi...>]

On Wed, 23 Mar 2022 21:00:01 +0700
Robin Atwood <ro...@bi...> wrote:
> > That's a sign that you had left authentication set to automatic and
> > the XOAUTH2 or OAUTHBEARER authentication method started failing
> > with your server at some point. Re-obtaining a new token with the
> > script may fix it, else running fetchmail in verbose mode (-v or -v
> > -v) may give you sufficient information to pinpoint the failure.  
> 
> I ran 
> oauth2 -c /path/to/oauth2Config.properties --obtain_refresh_token_file
> again and now the logon proceeds. I will see how long it works, one
> week seems to be the limit. If it happens again I will try publishing
> my app to see if that helps.

Yes, exactly one week later fetchmail ran out of authenticators again.
I "published" my Google app and ran the refresh command as above but I
received a message saying my app didn't obey the rules. So I
unpublished it and then the refresh procedure worked. For another week
I assume. Time to think about a new email service.

Robin
-- 
----------------------------------------------------------------------
Robin Atwood.

"Ship me somewheres east of Suez, where the best is like the worst,
 Where there ain't no Ten Commandments an' a man can raise a thirst"
         from "Mandalay" by Rudyard Kipling
----------------------------------------------------------------------