From: Matthias A. <mat...@gm...> - 2007-09-07 19:04:09
|
Frederic Marchal schrieb: > What happens is that fetchmail starts retrieving the mails and marks > them for deletion as soon as they are delivered to the MDA. Then, at > some point, the connection break (usually a timeout) and the server > assumes that it should not delete the mails that were marked so (it is > the expected behaviour). > > When fetchmail starts the next poll, it sees all the old messages and do > not download nor delete them again. Instead it leaves them on the server. Frédéric, your observation is correct. I have discussed with Sunil Shetye how we can mark these messages "deleted" so fetchmail re-does the deletions at the next cycle, but there have been open issues we haven't answered at the time, and finding a solution was shelved for various reasons, not the least of which that it was rather intrusive and had unresolved borderline issues. One way to contain this with respect to the message count is --expunge (which forces the deletion to become effective by logging out and in again for POP3 or sending an EXPUNGE command for IMAP), another one --fetchlimit, as you suggest (I'm not quoting that) which proceeds to the next server after a given number of messages downloaded. The options aren't quite the same and I'm not guaranteeing anything for older fetchmail version, but either should help with "mail reappearing after broken connection" issues to some extent. -- Matthias |