From: Dennis P. <da...@be...> - 2022-06-01 22:52:08
|
On 6/1/2022 4:02 PM, Matthias Andree wrote: > Am 01.06.22 um 19:03 schrieb Dennis Putnam: >> I've installed fetchmail 7 and since I am not able to find >> configuration documentation, I am using the fetchmail 6 patch >> instructions. I've created the following simple fetchmailrc file >> (sanitized): >> >> *poll imap.gmail.com protocol imap** >> ** auth oauthbearer username "my...@gm..."** >> ** passwordfile "/opt/fetchmail7/cron.oauth2"** >> ** is cufsalumni-leave here ssl sslcertck sslproto tlsl* >> >> When I run fetchmail I get this error: >> >> *fetchmail:/opt/fetchmail7/.fetchmailrc:2: syntax error at oauthbearer* >> >> Since it looks correct according to the documentation, either the >> documentation does not apply to 7 or I am missing something. Please >> help: TIA. > > 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 > Thanks for the reply. Those dumb asterisks were added by the mailer for bold. I guess I won't do that again. Anyway, like I said I copy/pasted the config directly from the documentation for version 6. I'll try your suggestions. |