On 2020.03.03 02:54, Philip Webb wrote:
191211 Holger Hoffstätte wrote:
> On 12/10/19 11:03 PM, Philip Webb wrote:
>> A few days ago, I updated Fetchmail to the latest stable 6.4.1 .
>> Immediately, it stopped fetching mail from one of my mail
forwarders ;
>> the other one still worked, as I found by test-mailing to myself.
>> When I reverted to 6.3.26-r4 , everything worked properly again.
> I had the same problem after updating to 6.4 and managed to fix it
> by adding the "sslproto ''" option to each poll section.
> This immediately made things work again,
> both when piping through POPFile and fetching from GMail.
> See the 6.4.x man page for changes regarding the --sslproto option.
Thanks again, if I didn't thank you before.
I simply reverted, left it that way & forgot all about it
till I noticed that Fetchmail needs Python-2 only when using 'tk'.
Wanting to eliminate Py-2 ASAP, I emerged Fetchmail 6.4.1
& ran into the same problem. Eventually, I also noticed
that 'sslproto' needs an argument (red face) & added the '' .
Now it's fetching mail again (big smile).
However, my ISP is now sending me an e-mail every 5 min ,
after Fetchmail checks for mail :
From: "(Cron Daemon)" <purslow@***>
To: purslow@***
Subject: Cron <purslow@localhost> test -e /var/run/dhcpcd.pid &&
/usr/bin/fetchmail -s 2> /dev/null
fetchmail: Query status=2 (SOCKET)
Can anyone tell me how to suppress these msgs ?
Are you sure the message is coming from your ISP, and not locally
generated, perhaps by cron?
Jack
