From 6ddd8c9505a4620fd4b8f2a16a2de7ae1930897f Mon Sep 17 00:00:00 2001
From: "Eric S. Raymond"
@@ -31,31 +31,6 @@ fetchmail is now pretty mature and I have many other projects, so I
don't personally chase obscure or marginal problems. Help with any
of these will be cheerfully accepted.Back to Eric's Home Page
Up to Site Map
-$Date: 2002/07/30 13:31:23 $
+$Date: 2002/09/17 09:36:00 $
Matthias Andree writes: I believe fetchmail should not iterate -over protocols when we have a DNS failure.
- --> BTW, I found a bug in 5.9.7: -> ./fetchmail -Nvd0 jads.asdkjaldsf.com -> Enter password for emma@jads.asdkjaldsf.com: -> fetchmail: 5.9.7 querying jads.asdkjaldsf.com (protocol auto) at Mit 20 -> Feb 2002 06:35:07 CET: poll started -> fetchmail: 5.9.7 querying jads.asdkjaldsf.com (protocol IMAP) at Mit 20 -> Feb 2002 06:35:07 CET: poll started -> fetchmail: couldn't find canonical DNS name of jads.asdkjaldsf.com -> fetchmail: 5.9.7 querying jads.asdkjaldsf.com (protocol IMAP) at Mit 20 -> Feb 2002 06:35:08 CET: poll completed -> fetchmail: 5.9.7 querying jads.asdkjaldsf.com (protocol POP3) at Mit 20 -> Feb 2002 06:35:08 CET: poll started -> fetchmail: couldn't find canonical DNS name of jads.asdkjaldsf.com -> fetchmail: 5.9.7 querying jads.asdkjaldsf.com (protocol POP3) at Mit 20 -> Feb 2002 06:35:08 CET: poll completed -> fetchmail: 5.9.7 querying jads.asdkjaldsf.com (protocol auto) at Mit 20 -> Feb 2002 06:35:08 CET: poll completed -> fetchmail: Query status=11 (DNS) -> fetchmail: normal termination, status 11 --
IDLE is not fully implemented. Fetchmail does not time out the idle connection every 30 minutes or less as required by RFC2177. Some servers (including UW IMAPD compiled without the @@ -64,10 +39,6 @@ connection after 30 minutes, resulting in a spurious socket error in your logs and no mail being picked up until the next poll cycle.
-The UIDL code seems rather broken. It's a nasty swamp. Somebody -who actually uses it should fix it -- every time I try I seem to -make things worse....
-POP3 can't presently distinguish a wedged or down server from an authentication failure. Possible fix: after issuing a PASS command. wait 300 (xx) seconds for a "-ERR" or a "+OK" . If nothing comes @@ -108,7 +79,7 @@ reports.