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