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

Yes. For a change, it might help to read the manual page to understand
what the options mean, and to really understand what I am writing about
fonts and about TLS protocol versions. It was written such that people
might get to run fetchmail without need to ask for support and wait and
ask again. But  it may not be perfect - And if something about
fetchmail's manual page is unclear, please point out the exact section
(feel free to quote it literally) and either make a suggestion for
improvement or ask a specific question.

It also  seems pretty clear to me that your font does not permit you to
distinguish ONE (1) from ELL (l) well (in "tlsl").

It really helps to use a text editor or console window or even
system-wide a programmer's font for non-proportional (i. e. all
characters have the same width) output which was specifically designed
so that the differences between O08B, i1l7fL, yg and similar character
groups are easy to see. Especially 1, 7 and l are usually hard to tell
apart, or in other fonts, l and | (ell and pipe). Roboto Mono works for
me, but there surely is half a dozen other high-quality programmer fonts.

It was not the sslproto keyword that was wrong, but its argument. If I
paste this literally, I get

> fetchmail:/tmp/fmconf:5: syntax error, unexpected STRING at tlsl
and the manual page or README.SSL would have told you that you should
have used something like sslproto tls1.2+ and does not document sslproto
tlsl  at all. That your syntax error is in a different form, tells me
that you are operating on an older version of fetchmail but not the
current state of affairs from the Git repository's "next" branch. And
you also seem to be working off a fetchmail version that may be in a
fetchmail-7 folder but which does not appear to be an oauthbearer
capable version of fetchmail because that is what it told you in an
earlier e-mail message of yours. See my earlier message again for the
recourse.

I have to assert  that I do not have the resources to provide general
utility or computer configuration training here nor can I support
arbitrarily old versions (where I may not even know which version it
is). Sorry.