Re: [Fetchmail-users] fetchmail 7 fetchmailrc problem

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

Am 02.06.22 um 15:23 schrieb Dennis Putnam:
> On 6/1/2022 4:02 PM, Matthias Andree wrote:
>>
>> Dennis,
>>
>> adding markup (stars) by you or your mailer implicitly is not helpful,
>> and I wonder if you copied and pasted that, or retyped it.
>>
>> At any rate, "syntax error at" is not a format that the current Git
>> version of fetchmail 7 would report. Update your Git checkout (git pull
>> should do it), rebuild, retry, and before you do that:
>>
>> Also note that on top of all that, the last line is wrong, there is no
>> sslproto (I'll capitalize it so you see it) TLSL (be sure to reconfigure
>> your computer to use display fonts that actually let you tell the
>> difference between |1lI),
>> and if you hadn't mistyped, you would have forced fetchmail to talk only
>> TLS v1.0 with Google, while they offer TLS v1.3 and nothing older than
>> v1.2 should be used any more.
>>
>> You should also receive a "WARNING: ssl is obsolescent. Please use
>> sslmode wrapped instead. at ssl" in fetchmail 7, but ssl will work if
>> you want to fiddle around with patched fetchmail 6 and fetchmail 7 -
>> just be sure not to lose track of what you installed.
>>
>> HTH
>>
>>
>>
> Hi Matthias,
>
> I'm getting the same error. This is what I understood you to mean:
>
> poll imap.gmail.com protocol imap
>   auth oauthbearer username "my...@gm..."
>   passwordfile "/opt/fetchmail7/cron.oauth2"
>   is cufsalumni-leave here sslmode wrapped sslcertck tlsl


One more note on this towards the end of a practical solution, it might
be MUCH EASIER to just configure the Google Mail account for
app-specific passwords.
Google specifically appear to require you to enable 2-factor
authentication, offering various options for 2nd factor - be sure to add
as many 2nd factors as are practical and deemed secure so you can
recover your account from the loss of one of them --  and only then let
you generate an application-specific password for your mail access, and
copy that out of Google's account settings (wherever exactly that is I
don't know) into your fetchmail configuration.

I don't use Google much, I did this ages ago and did not take notes of
what exactly I did (and next day they change the design and screenshots
are moot anyways),
and I have just successfully tested that with this old account I can
still download messages with fetchmail and SSL and POP3 and regular
password login, and it's still as simple as:

poll imap.gmail.com with proto POP3 user 'whatever' pass
'app.specific/password_provided-by_google' options keep ssl

and it just works. So I wonder what good all this OAUTH mess is.