| 1 |
reader@×××××××.com wrote: |
| 2 |
> Maybe if you took `set daemon 60' out of .fetchmailrc and ran it from cron? |
| 3 |
Thanks for the suggestion, but the reason I've avoided the cron approach |
| 4 |
is that I've two objectives: |
| 5 |
1. To minimise latency in delivery of messages as far as is practical |
| 6 |
(without placing stupid demands on the resources of the POP3 servers) |
| 7 |
2. To cope with very large emails (several MB) which may be present at |
| 8 |
any POP account and must be downloaded over a potentially extremely |
| 9 |
congested relatively low-bandwidth link. |
| 10 |
|
| 11 |
The advantage of daemon mode here is that I neither end up with a huge |
| 12 |
polling delay nor any risk of a collision where two processes attempt to |
| 13 |
access the same POP account at the same time (which I'd expect to cause |
| 14 |
aggravation.) |
| 15 |
|
| 16 |
I've used fetchmail for several years too - and this is the first time |
| 17 |
I've been sure it's let me down... I was wondering if it was a known |
| 18 |
(obscure) bug with the latest version... maybe, for example, one that |
| 19 |
only arises in the context of a TCP error or, maybe, a remote server |
| 20 |
failing mid-transaction? |
| 21 |
|
| 22 |
Steve |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-user@g.o mailing list |
Archives