Hello,
I'm having problems making fetchmail 6.1.0 retrieve my POP3 mailbox.
It stumbles over the first message, which is left there by the IMAP
server:
------ cut ------
From MAILER-DAEMON Fri Apr 26 12:48:07 2002
Date: 26 Apr 2002 12:48:07 +0400
From: Mail System Internal Data <MAILER-DAEMON(_at_)lrn(_dot_)ru>
Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
Message-ID: <1019810887(_at_)lrn(_dot_)ru>
X-IMAP: 1011046791 0000064979
Status: RO
This text is part of the internal format of your mail folder, and is not
a real message. It is created automatically by the mail system software.
If deleted, important folder data will be lost, and it will be re-created
with the data reset to initial values.
------ end cut ------
Here is an appropriate cut from the verbose output:
------ cut ------
fetchmail: POP3> TOP 1 99999999
fetchmail: POP3< +OK
reading message mhz(_at_)localhost(_dot_)localdomain:1 of 20 (494 octets)
About to rewrite From: Mail System Internal Data
<MAILER-DAEMON(_at_)lrn(_dot_)ru>
Rewritten version is From: Mail System Internal Data
<MAILER-DAEMON(_at_)lrn(_dot_)ru>
fetchmail: message mhz(_at_)localhost(_dot_)localdomain:1 was not the expected
length (214 actual != 494 expected)
fetchmail: retained
fetchmail: POP3> TOP 2 99999999
fetchmail: POP3< Status: RO
fetchmail: POP3> QUIT
fetchmail: POP3<
fetchmail: client/server protocol error while fetching from mail.altlinux.ru
------ end cut ------
Notice how fetchmail sends a command for the next message while
the server still spits out message headers.
Fetchmail 5.9.12 skips the message just fine, apart from the length
mismatch warning (the retrieved length in this case being 492).
--
Stay tuned,
MhZ JID: mookid(_at_)jabber(_dot_)org
___________
A woman was in love with fourteen soldiers. It was clearly platoonic.