fetchmail-users — User questions and discussion

[Fetchmail-users] Oauth, gmail, docs/guide?

[joe a <joe...@j4...>]

I've avoided this, until now, as things seemed to be "in flux" and the 
issue generating some ill will.

Downloaded 6.4.30 in anticipation, but after some fruitless searching, I 
need to ask for the location for any current docs on configuring 
fetchmail with gmail.  OAuth2 is apparently google's answer to 
everything, overthrowing 42 as the reigning champion.

Thanks for any assistance and understanding.

joe a.

Re: [Fetchmail-users] fetchmail 7 fetchmailrc problem

[Dennis P. <da...@be...>]

On 6/3/2022 1:10 PM, Matthias Andree wrote:
> 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.
>
>
Hi Matthias,

Sorry if you consider me a PITA but this is confusing. Perhaps the 
problem is I'm not using gitlab correctly. I cloned "next" from gitlab. 
After building it:

 >bin/fetchmail --version
This is fetchmail release 6.4.30+SSL-SSLv2-SSLv3+NLS.
.
.
.

Apparently I am not able to get version 7 and can't seem to find it.

Re: [Fetchmail-users] fetchmail 7 fetchmailrc problem

[Dennis P. <da...@be...>]

On 6/3/2022 1:28 PM, Matthias Andree wrote:
> 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.
>
>
>
Its confusing. I have been using app specific passwords but Google is 
supposed to be ending it 5/30. However, it appears to still be working 
as of today.

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.

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.

Re: [Fetchmail-users] fetchmail 7 fetchmailrc problem

[Dennis P. <da...@be...>]

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

Re: [Fetchmail-users] fetchmail 7 fetchmailrc problem

[Dennis P. <da...@be...>]

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.

Re: [Fetchmail-users] fetchmail 7 fetchmailrc problem

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

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

[Fetchmail-users] fetchmail 7 fetchmailrc problem

[Dennis P. <da...@be...>]

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.

Re: [Fetchmail-users] Fetchmail via systemd won't become a daemon

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

Am 31.05.22 um 19:17 schrieb Mauro Folcarelli:
>
> Thank you Matthias.
>
> I removed the "--daemon" from the command line and replaced it with
> --nodetach
>
> The result is the same:
>
> mag 31 19:09:18 mfhost fetchmail[4255]: fetchmail: POP3> QUIT
> mag 31 19:09:18 mfhost fetchmail[4255]: fetchmail: POP3< +OK Logging out.
> mag 31 19:09:18 mfhost fetchmail[4255]: fetchmail: 6.4.30
> interrogazione di pop.tiscali.it (protocollo POP3) su mar 31 mag 2022,
> 19:09:18: completata
> mag 31 19:09:18 mfhost fetchmail[4255]: fetchmail: interruzione
> normale, stato 1
> mag 31 19:09:18 mfhost systemd[1327]: fetchmail.service: Main process
> exited, code=exited, status=1/FAILURE
> ░░ Subject: Uscito processo unità
> ░░ Defined-By: systemd
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> ░░
> ░░ Un processo ExecStart appartenente all'unità UNIT è uscito.
> ░░
> ░░ Il codice di uscita del processo è 'exited' ed è uscito con 1.
> mag 31 19:09:18 mfhost systemd[1327]: fetchmail.service: Failed with
> result 'exit-code'.
> ░░ Subject: Unit fallita
> ░░ Defined-By: systemd
> ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
> ░░
> ░░ Unità UNIT entrata nello stato 'failed' (fallito) con risultato
> 'exit-code'.
>
> Fetchmail worked well, but after having downloaded emails from
> provider's server, it ended.
>
> The --nodetach option didn't produced the result I was expecting:
> fetchmail remaining "running" and downloading emails every X time.
>
> If it's not possible to achieve this, ... ok I will use cron and
> launch fetchmail every X time.
>

it's either: --nodetach --daemon 300

or: using cron/systemd timers and no --daemon option (or --daemon 0).

Re: [Fetchmail-users] Fetchmail via systemd won't become a daemon

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

Am 29.05.22 um 19:44 schrieb Mauro Folcarelli:
> I configured fetchmail to run at startup, via systemd.
>
> It runs, without errors, but it exits as a "one time running" and not
> like a daemon.


Mauro,


fetchmail daemonizes itself including forking into the background and
letting go of the controlling terminal.

The proper approach would be to remove the --daemon and start fetchmail
via a systemd timer instead, or via cron.


If you want to configure fetchmail as a service, you may get away with
adding the --nodetach command line flag to the unit file's ExecStart.

HTH.


Matthias

[Fetchmail-users] Fetchmail via systemd won't become a daemon

[Mauro F. <mau...@ti...>]

I configured fetchmail to run at startup, via systemd.

It runs, without errors, but it exits as a "one time running" and not 
like a daemon.

In the file "/home/mf/.config/systemd/user/fetchmail.service" :

-----------------------------------------------------------------------------------------------------------------------

[Unit]
Description=A remote-mail retrieval utility
[Service]
ExecStartPre=/usr/bin/setmail
ExecStart=/usr/bin/fetchmail  -v --daemon 60  --fetchmailrc 
/home/mf/.fetchmailrc
RestartSec=1
[Install]
WantedBy=default.target

-----------------------------------------------------------------------------------------------------------------------

In the  /home/mf/.fetchmailrc :


set idfile /spazio/tmp/Logs/fetchmail-mf-uidl
defaults timeout 60
proto pop3 uidl
options fetchall
mda '/usr/bin/procmail -d %T';

I also tried adding in the ".fetchmailrc" file the option

set daemon 60

but with identical result : the fetchmail process ends with no error, 
but not persists running.


$ systemctl --user status fetchmail
○ fetchmail.service - A remote-mail retrieval utility
      Loaded: loaded (/home/mf/.config/systemd/user/fetchmail.service; 
enabled; vendor preset: disabled)
      Active: inactive (dead) since Sun 2022-05-29 18:57:00 CEST; 43min ago
     Process: 1365 ExecStartPre=/usr/bin/setmail (code=exited, 
status=0/SUCCESS)
     Process: 1572 ExecStart=/usr/bin/fetchmail -v --daemon 60 
--fetchmailrc /home/mf/.fetchmailrc (code=exited, status=0/SUCCESS)
    Main PID: 1572 (code=exited, status=0/SUCCESS)
         CPU: 14ms

mag 29 18:57:00 mfhost systemd[1311]: Starting fetchmail.service - A 
remote-mail retrieval utility...
mag 29 18:57:00 mfhost systemd[1311]: Started fetchmail.service - A 
remote-mail retrieval utility.


$ journalctl --user -xeu fetchmail.service

mag 29 18:57:00 mfhost systemd[1311]: Starting fetchmail.service - A 
remote-mail retrieval utility...
░░ Subject: L'unità UNIT inizia la fase di avvio
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ L'unità UNIT ha iniziato la fase di avvio.
mag 29 18:57:00 mfhost systemd[1311]: Started fetchmail.service - A 
remote-mail retrieval utility.
░░ Subject: L'unità UNIT ha terminato la fase di avvio
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ L'unità UNIT ha terminato la fase di avvio.
░░
░░ La fase di avvio è done.


if I run, in a terminal, as user "mf" the command:

/usr/bin/fetchmail  --fetchmailrc /home/mf/.fetchmailrc

it runs with no errors and fetches the email, normally.

Where is the problem?

Thank you for your help

-- 
*Mauro Folcarelli*

[Fetchmail-users] Configure Fetchmail 7 for OAuth2

[Dennis P. <da...@be...>]

I have installed fetchmail 7 and need to configure it for gmail and 
OAuth2. Unfortunately I cannot find the documentation for fetchmailrc 
other than version 6. I looked through gitlab but didn't have much luck. 
Can someone send me a link for what I should be reading? TIA.

Re: [Fetchmail-users] Configure Fetchmail 7 for OAuth2

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

Am 22.05.22 um 16:29 schrieb Dennis Putnam:
> I have installed fetchmail 7 and need to configure it for gmail and
> OAuth2. Unfortunately I cannot find the documentation for fetchmailrc
> other than version 6. I looked through gitlab but didn't have much
> luck. Can someone send me a link for what I should be reading? TIA.


Dennis,

It's right under your nose, fetchmail 7 comes with a README.OAUTH2 file.
Other than that, see https://gitlab.com/fetchmail/fetchmail/-/issues/27

Regards,
Matthias

[Fetchmail-users] Configure Fetchmail 7 for OAuth2

[Dennis P. <da...@be...>]

I have installed fetchmail 7 and need to configure it for gmail and 
OAuth2. Unfortunately I cannot find the documentation for fetchmailrc 
other than version 6. I looked through gitlab but didn't have much luck. 
Can someone send me a link for what I should be reading? TIA.

Re: [Fetchmail-users] OAuth2 Configuration Question

[Andrew C A. <fet...@ai...>]

On Tue, 17 May 2022, Dennis Putnam wrote:

> I am in the process of configuring fetchmail 7 for gmail's OAuth2. The
> documentation mentions configuring postfix. Since I am using fetchmail 
> to only retrieve gmail, am I correct that I can ignore the postfix instructions?

Correct.

> I don't see what postfix has to do with reading gmail.

postfix is one of the options for fetchmail to use to deliver the
messages that it has fetched; presumably the one used by the
author of the document you are reading.

I am not sure that fetchmail can actually write the
message to a file itself; I have always used
     wants mda ... /usr/sbin/exim ...
Whilst you don't need postfix you *may* need some equivalent
mta-type program.

-- 
Andrew C. Aitchison					Kendal, UK
 			an...@ai...

[Fetchmail-users] OAuth2 Configuration Question

[Dennis P. <da...@be...>]

I am in the process of configuring fetchmail 7 for gmail's OAuth2. The 
documentation mentions configuring postfix. Since I am using fetchmail 
to only retrieve gmail, am I correct that I can ignore the postfix 
instructions? I don't see what postfix has to do with reading gmail.

Re: [Fetchmail-users] Compiling Fetchmail 7 with OpenSSL 3

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

Am 17.05.22 um 19:52 schrieb Dennis Putnam:
> On 5/17/2022 1:31 PM, Matthias Andree wrote:
>> Am 17.05.22 um 18:54 schrieb Dennis Putnam:
>>> On 5/17/2022 12:26 PM, Matthias Andree wrote:
>>>> Am 17.05.22 um 15:27 schrieb Dennis Putnam:
>>>>> On 5/16/2022 12:30 PM, Matthias Andree wrote:
>>>>>>
>>>>>> The _workaround_ for me seems to be (assuming OpenSSL 3 in
>>>>>> /opt/openssl3, else adjust):
>>>>>>
>>>>>> ./configure PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig
>>>>>> ...
>>>>>>
>>>>> Thanks for the reply. Just to be clear, I should omit --with-ssl and
>>>>> just use PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig or do I need
>>>>> both?
>>>> Yes, omit --with-ssl=... and only use the PKG_CONFIG_LIBDIR=...
>>>>
>>>>
>>>>
>>> Thanks again. That seems to have worked but now I need to install it
>>> in a different directory from the old version. I don't see any
>>> destination directory directive for 'make install'. Did I miss
>>> something in the documentation?
>>
>>
>> Sorry, we're all too used to the GNU autoconf standards, but there is
>> terse information in INSTALL.
>>
>>     ./configure --prefix=/opt/myfetchmail PKG_CONFIG_LIBDIR=...
>>
>> or something like that.
>>
>>
> Thanks yet again. I was looking to do that in the make install. I
> didn't think about configure. In any case I owe you.


That would not work easily (technically it's still possible otherwise,
but with unreasonable effort), because the internationalization stuff
bakes its location (where the .mo/.gmo files get installed) into the
executable and that's way easier to do from configure. make install
permits installing into a staging directory though.

Re: [Fetchmail-users] Compiling Fetchmail 7 with OpenSSL 3

[Dennis P. <da...@be...>]

On 5/17/2022 1:31 PM, Matthias Andree wrote:
> Am 17.05.22 um 18:54 schrieb Dennis Putnam:
>> On 5/17/2022 12:26 PM, Matthias Andree wrote:
>>> Am 17.05.22 um 15:27 schrieb Dennis Putnam:
>>>> On 5/16/2022 12:30 PM, Matthias Andree wrote:
>>>>>
>>>>> The _workaround_ for me seems to be (assuming OpenSSL 3 in
>>>>> /opt/openssl3, else adjust):
>>>>>
>>>>> ./configure PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig
>>>>> ...
>>>>>
>>>> Thanks for the reply. Just to be clear, I should omit --with-ssl and
>>>> just use PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig or do I need
>>>> both?
>>> Yes, omit --with-ssl=... and only use the PKG_CONFIG_LIBDIR=...
>>>
>>>
>>>
>> Thanks again. That seems to have worked but now I need to install it
>> in a different directory from the old version. I don't see any
>> destination directory directive for 'make install'. Did I miss
>> something in the documentation?
>
>
> Sorry, we're all too used to the GNU autoconf standards, but there is
> terse information in INSTALL.
>
>     ./configure --prefix=/opt/myfetchmail PKG_CONFIG_LIBDIR=...
>
> or something like that.
>
>
Thanks yet again. I was looking to do that in the make install. I didn't 
think about configure. In any case I owe you.

Re: [Fetchmail-users] Compiling Fetchmail 7 with OpenSSL 3

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

Am 17.05.22 um 18:54 schrieb Dennis Putnam:
> On 5/17/2022 12:26 PM, Matthias Andree wrote:
>> Am 17.05.22 um 15:27 schrieb Dennis Putnam:
>>> On 5/16/2022 12:30 PM, Matthias Andree wrote:
>>>>
>>>> The _workaround_ for me seems to be (assuming OpenSSL 3 in
>>>> /opt/openssl3, else adjust):
>>>>
>>>> ./configure PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig
>>>> ...
>>>>
>>> Thanks for the reply. Just to be clear, I should omit --with-ssl and
>>> just use PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig or do I need
>>> both?
>> Yes, omit --with-ssl=... and only use the PKG_CONFIG_LIBDIR=...
>>
>>
>>
> Thanks again. That seems to have worked but now I need to install it
> in a different directory from the old version. I don't see any
> destination directory directive for 'make install'. Did I miss
> something in the documentation?


Sorry, we're all too used to the GNU autoconf standards, but there is
terse information in INSTALL.

     ./configure --prefix=/opt/myfetchmail PKG_CONFIG_LIBDIR=...

or something like that.

Re: [Fetchmail-users] Compiling Fetchmail 7 with OpenSSL 3

[Dennis P. <da...@be...>]

On 5/17/2022 12:26 PM, Matthias Andree wrote:
> Am 17.05.22 um 15:27 schrieb Dennis Putnam:
>> On 5/16/2022 12:30 PM, Matthias Andree wrote:
>>>
>>> The _workaround_ for me seems to be (assuming OpenSSL 3 in
>>> /opt/openssl3, else adjust):
>>>
>>> ./configure PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig
>>> ...
>>>
>> Thanks for the reply. Just to be clear, I should omit --with-ssl and
>> just use PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig or do I need
>> both?
> Yes, omit --with-ssl=... and only use the PKG_CONFIG_LIBDIR=...
>
>
>
Thanks again. That seems to have worked but now I need to install it in 
a different directory from the old version. I don't see any destination 
directory directive for 'make install'. Did I miss something in the 
documentation?

Re: [Fetchmail-users] Compiling Fetchmail 7 with OpenSSL 3

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

Am 17.05.22 um 15:27 schrieb Dennis Putnam:
> On 5/16/2022 12:30 PM, Matthias Andree wrote:
>>
>> The _workaround_ for me seems to be (assuming OpenSSL 3 in
>> /opt/openssl3, else adjust):
>>
>> ./configure PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig
>> ...
>>
> Thanks for the reply. Just to be clear, I should omit --with-ssl and
> just use PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig or do I need
> both?
Yes, omit --with-ssl=... and only use the PKG_CONFIG_LIBDIR=...

Re: [Fetchmail-users] Compiling Fetchmail 7 with OpenSSL 3

[Dennis P. <da...@be...>]

On 5/16/2022 12:30 PM, Matthias Andree wrote:
> Am 15.05.22 um 23:20 schrieb Dennis Putnam:
>> After successfully installing OpenSSL 3.0.3 on my CentOS 7 system, I
>> tried to compile fetchmail 7, It was cloned from gitlab. The compile
>> failed with these messages:
>>
>> undefined reference to `OpenSSL_version'
>> undefined reference to `OpenSSL_version_num'
>> undefined reference to `OPENSSL_sk_num'
>> undefined reference to `OPENSSL_sk_value'
>> undefined reference to `OPENSSL_sk_free'
>> undefined reference to `TLS_client_method'
>> undefined reference to `SSL_CTX_set_options'
>>
>> I went to the OpenSSL forum to see what was wrong and got this reply:
>>
>> *After checking the ssl.so library I observed Id don't define the
>> function OpenSSL_version but into the header file opensslv.h you found
>> a define that give you the version of your ssl library **
>> **# define OPENSSL_VERSION_NUMBER  0x101010cfL **
>> **# define OPENSSL_VERSION_TEXT    "OpenSSL 1.1.1l  24 Aug 2021" **
>> ****
>> **To resolve your problem don’t call the method OpenSSL_version, but
>> use directly the define in header file opensslv.h.*
>>
>>
>> I guess the implication is that the fetchmail source needs to be
>> modified somewhere, right?
>
> The forum suggestion "don’t call the method OpenSSL_version, but use
> directly the define in header file opensslv.h." is bullshit.
> It is someone telling you to superficially cure a symptom without
> knowing intentions or researching the actual cause.
>
> One more rant item: OpenSSL 3.0.0 and 3.0.2 both documented this method
> (and OpenSSL's policies will not deprecate this in any 3.0.x version)
> and I deliberately wrote fetchmail to inquire headers and library and
> complain if they obviously do not match.
>
> Rant aside, the cause I can currently only surmise that your fetchmail
> ends up picking up pieces of both the 1.1.1 and 3.0 installations of
> OpenSSL,
> and I found one way that I can reproduce such a failure, which is
> however specific to systems with multiple OpenSSL versions installed.
>
>
> The _workaround_ for me seems to be (assuming OpenSSL 3 in
> /opt/openssl3, else adjust):
>
> ./configure PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig
>
> and it prints (the first line is a cosmetic bug)
>
>> configure: Enabling OpenSSL support in /usr.
>> configure: SSL-check: trying pkg-config for openssl
>> checking for SSL... yes
>> checking how to link with libssl... /opt/openssl3/lib64/libssl.so
>> /opt/openssl3/lib64/libcrypto.so -Wl,-rpath -Wl,/opt/openssl3/lib64
>> configure: From pkg-config: Adding /opt/openssl3/lib64/libssl.so
>> /opt/openssl3/lib64/libcrypto.so -Wl,-rpath -Wl,/opt/openssl3/lib64 to
>> LIBS. LDFLAGS= -L/opt/openssl3/lib64
>> configure: Enabling OpenSSL support.
>> configure:
>>   CC:       gcc
>>   CPPFLAGS: -I/opt/openssl3/include
>>   CFLAGS:   -g -O2 -I/usr/kerberos/include
>>   LDFLAGS:   -L/opt/openssl3/lib64
>>   LIBS:       /opt/openssl3/lib64/libssl.so
>> /opt/openssl3/lib64/libcrypto.so -Wl,-rpath -Wl,/opt/openssl3/lib64
>> checking whether LIBRESSL_VERSION_NUMBER is declared... no
>> checking whether TLS1_3_VERSION is declared... yes
>> checking whether TLS1_2_VERSION is declared... yes
>> checking whether SSLv3_client_method is declared... no
>> checking whether TLS_MAX_VERSION is declared... yes
>
> and ends up with a working fetchmail that prints, when run with -V:
>
>> $  ./fetchmail -V
>> This is fetchmail release 7.0.0-alpha10+SSL-SSLv2-SSLv3+NLS.
>> Compiled with SSL library 0x30000020 "OpenSSL 3.0.2 15 Mar 2022"
>> Run-time uses SSL library 0x30000020 "OpenSSL 3.0.2 15 Mar 2022"
>> OpenSSL: OPENSSLDIR: "/etc/pki/tls"
>> Engines: ENGINESDIR: "/opt/openssl3/lib64/engines-3"
>> ...
> From Git, ./configure --with-ssl seems to wind up mixing both versions
> for me, I need to check that or forward-port configure.ac fixes from the
> 6.x stuff.
>
Thanks for the reply. Just to be clear, I should omit --with-ssl and 
just use PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig or do I need both?

Re: [Fetchmail-users] KeyError: 'refresh_token' error in fetchmail-oauth2

[Marco G. <ga...@li...>]

Mandi! Robin Atwood
  In chel di` si favelave...

>> > >   https://support.google.com/accounts/answer/185833
> Will this technique work past the end of the month? 

AFAIK yes, or at least i've not found anywhere a bigG docs stating the
opposite...

-- 
  Che ruolo può avere all'interno di una società uno che non parla ed il cui
  curriculum é misero? IL Presidente.		(Si Può Fare - Nello)

Re: [Fetchmail-users] Compiling Fetchmail 7 with OpenSSL 3

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

Am 15.05.22 um 23:20 schrieb Dennis Putnam:
> After successfully installing OpenSSL 3.0.3 on my CentOS 7 system, I
> tried to compile fetchmail 7, It was cloned from gitlab. The compile
> failed with these messages:
>
> undefined reference to `OpenSSL_version'
> undefined reference to `OpenSSL_version_num'
> undefined reference to `OPENSSL_sk_num'
> undefined reference to `OPENSSL_sk_value'
> undefined reference to `OPENSSL_sk_free'
> undefined reference to `TLS_client_method'
> undefined reference to `SSL_CTX_set_options'
>
> I went to the OpenSSL forum to see what was wrong and got this reply:
>
> *After checking the ssl.so library I observed Id don't define the
> function OpenSSL_version but into the header file opensslv.h you found
> a define that give you the version of your ssl library **
> **# define OPENSSL_VERSION_NUMBER  0x101010cfL **
> **# define OPENSSL_VERSION_TEXT    "OpenSSL 1.1.1l  24 Aug 2021" **
> ****
> **To resolve your problem don’t call the method OpenSSL_version, but
> use directly the define in header file opensslv.h.*
>
>
> I guess the implication is that the fetchmail source needs to be
> modified somewhere, right?

The forum suggestion "don’t call the method OpenSSL_version, but use
directly the define in header file opensslv.h." is bullshit.
It is someone telling you to superficially cure a symptom without
knowing intentions or researching the actual cause.

One more rant item: OpenSSL 3.0.0 and 3.0.2 both documented this method
(and OpenSSL's policies will not deprecate this in any 3.0.x version)
and I deliberately wrote fetchmail to inquire headers and library and
complain if they obviously do not match.

Rant aside, the cause I can currently only surmise that your fetchmail
ends up picking up pieces of both the 1.1.1 and 3.0 installations of
OpenSSL,
and I found one way that I can reproduce such a failure, which is
however specific to systems with multiple OpenSSL versions installed.


The _workaround_ for me seems to be (assuming OpenSSL 3 in
/opt/openssl3, else adjust):

./configure PKG_CONFIG_LIBDIR=/opt/openssl3/lib64/pkgconfig

and it prints (the first line is a cosmetic bug)

> configure: Enabling OpenSSL support in /usr.
> configure: SSL-check: trying pkg-config for openssl
> checking for SSL... yes
> checking how to link with libssl... /opt/openssl3/lib64/libssl.so
> /opt/openssl3/lib64/libcrypto.so -Wl,-rpath -Wl,/opt/openssl3/lib64
> configure: From pkg-config: Adding /opt/openssl3/lib64/libssl.so
> /opt/openssl3/lib64/libcrypto.so -Wl,-rpath -Wl,/opt/openssl3/lib64 to
> LIBS. LDFLAGS= -L/opt/openssl3/lib64
> configure: Enabling OpenSSL support.
> configure:
>   CC:       gcc
>   CPPFLAGS: -I/opt/openssl3/include
>   CFLAGS:   -g -O2 -I/usr/kerberos/include
>   LDFLAGS:   -L/opt/openssl3/lib64
>   LIBS:       /opt/openssl3/lib64/libssl.so
> /opt/openssl3/lib64/libcrypto.so -Wl,-rpath -Wl,/opt/openssl3/lib64
> checking whether LIBRESSL_VERSION_NUMBER is declared... no
> checking whether TLS1_3_VERSION is declared... yes
> checking whether TLS1_2_VERSION is declared... yes
> checking whether SSLv3_client_method is declared... no
> checking whether TLS_MAX_VERSION is declared... yes

and ends up with a working fetchmail that prints, when run with -V:

> $  ./fetchmail -V
> This is fetchmail release 7.0.0-alpha10+SSL-SSLv2-SSLv3+NLS.
> Compiled with SSL library 0x30000020 "OpenSSL 3.0.2 15 Mar 2022"
> Run-time uses SSL library 0x30000020 "OpenSSL 3.0.2 15 Mar 2022"
> OpenSSL: OPENSSLDIR: "/etc/pki/tls"
> Engines: ENGINESDIR: "/opt/openssl3/lib64/engines-3"
> ...
 From Git, ./configure --with-ssl seems to wind up mixing both versions
for me, I need to check that or forward-port configure.ac fixes from the
6.x stuff.