Quoting from Sunil Shetye's mail on Mon, Jul 08, 2002 at 06:27:30PM +0530:
If a mail in a maildir folder is not readable, fetchmail parses the
responses slightly incorrectly.
Repeating the same test with maildir+pop3 reveals that fetchmail quits
immediately on getting a -ERR.
2 messages for shetye at server.bombay.retortsoft.com (2416 octets).
fetchmail: POP3> LIST
fetchmail: POP3< +OK POP3 clients that break here, they violate STD53.
fetchmail: POP3< 1 0
[this mail is unreadable]
fetchmail: POP3< 2 2416
fetchmail: POP3< .
fetchmail: POP3> RETR 1
fetchmail: POP3< -ERR Can't open the message file - it's gone!
fetchmail: Can't open the message file - it's gone!
fetchmail: POP3> QUIT
[second mail is not downloaded]
fetchmail: POP3< +OK Bye-bye.
fetchmail: client/server protocol error while fetching from
server.bombay.retortsoft.com
Here is a patch which treats it as a transient error.
=======================================================
diff -Naur fetchmail-5.9.13.orig/pop3.c fetchmail-5.9.13/pop3.c
--- fetchmail-5.9.13.orig/pop3.c Tue Jul 9 10:17:08 2002
+++ fetchmail-5.9.13/pop3.c Tue Jul 9 10:28:12 2002
@@ -70,7 +70,9 @@
}
else if (strncmp(buf,"-ERR", 4) == 0)
{
- if (stage > STAGE_GETAUTH)
+ if (stage == STAGE_FETCH)
+ ok = PS_TRANSIENT;
+ else if (stage > STAGE_GETAUTH)
ok = PS_PROTOCOL;
/*
* We're checking for "lock busy", "unable to lock",
=======================================================
Sunil Shetye.