The Tuesday 2004-02-03 at 20:34 +0100, I wrote:
I don't know, I think I could make this fetchmail the default one to use, and see what happens when it handles these kind of email first hand: it could be thinking that this email has already been seen :-?
I think I can confirm that this version of fetchmail deletes emails with incorrect headers: fetchmail[8754]: POP3< +OK fetchmail[8754]: POP3> STAT fetchmail[8754]: POP3< +OK 1 101830 fetchmail[8754]: POP3> LAST fetchmail[8754]: POP3< +OK 0 fetchmail[8754]: 1 message for * at * (101830 octets). fetchmail[8754]: POP3> LIST 1 fetchmail[8754]: POP3< +OK 1 101830 fetchmail[8754]: POP3> TOP 1 99999999 fetchmail[8754]: POP3< +OK 101830 octets fetchmail[8754]: reading message *@*:1 of 1 (101830 octets) fetchmail[8754]: incorrect header line found while scanning headers fetchmail[8754]: line: This is a multi-part message in MIME format.^M fetchmail[8754]: flushed fetchmail[8754]: POP3> DELE 1 fetchmail[8754]: POP3< +OK fetchmail[8754]: POP3> QUIT fetchmail[8754]: POP3< +OK I have looked very carefully, and that email was not handled to procmail (it's not on procmail log, nor in the mail.debug log). It is completely lost (fetchmail logs it as "flushed", which is strange). Therefore, I advise against using this version of fetchmail, and instead manually retrieve these incorrect messages either using Mozilla or the ISP webmail, if possible. And I have reasons to believe it was not spam :-/ -- Cheers, Carlos Robinson