diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2002-09-17 09:36:00 +0000 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2002-09-17 09:36:00 +0000 |
| commit | 6ddd8c9505a4620fd4b8f2a16a2de7ae1930897f (patch) | |
| tree | f0023cf3ace75fa8f7b0304a74d802b04c1f65d0 | |
| parent | 8f4a52422003ec63e851d60fc0d0441a9eca7c58 (diff) | |
| download | fetchmail-6ddd8c9505a4620fd4b8f2a16a2de7ae1930897f.tar.gz fetchmail-6ddd8c9505a4620fd4b8f2a16a2de7ae1930897f.tar.bz2 fetchmail-6ddd8c9505a4620fd4b8f2a16a2de7ae1930897f.zip | |
Fix a minor bug reported by Matthias Andree.
svn path=/trunk/; revision=3722
| -rw-r--r-- | fetchmail.c | 5 | ||||
| -rw-r--r-- | todo.html | 33 |
2 files changed, 5 insertions, 33 deletions
diff --git a/fetchmail.c b/fetchmail.c index 74ccc4f4..6eb0a39e 100644 --- a/fetchmail.c +++ b/fetchmail.c @@ -1327,8 +1327,9 @@ static int query_host(struct query *ctl) ctl->server.protocol = autoprobe[i]; do { st = query_host(ctl); - } while (st == PS_REPOLL); - if (st == PS_SUCCESS || st == PS_NOMAIL || st == PS_AUTHFAIL || st == PS_LOCKBUSY || st == PS_SMTP || st == PS_MAXFETCH) + } while + (st == PS_REPOLL); + if (st == PS_SUCCESS || st == PS_NOMAIL || st == PS_AUTHFAIL || st == PS_LOCKBUSY || st == PS_SMTP || st == PS_MAXFETCH || st == PS_DNS) break; } ctl->server.protocol = P_AUTO; @@ -19,7 +19,7 @@ content="Known bugs and to-do items in fetchmail" /> <tr> <td width="30%">Back to <a href="/~esr">Eric's Home Page</a></td> <td width="30%" align="center">Up to <a href="/~esr/sitemap.html">Site Map</a></td> -<td width="30%" align="right">$Date: 2002/07/30 13:31:23 $</td> +<td width="30%" align="right">$Date: 2002/09/17 09:36:00 $</td> </tr> </table> @@ -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.</p> -<p>Matthias Andree writes: I believe fetchmail should not iterate -over protocols when we have a DNS failure.</p> - -<pre> -> 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 -</pre> - <p>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.</p> -<p>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....</p> - <p>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.</p> <tr> <td width="30%">Back to <a href="/~esr">Eric's Home Page</a></td> <td width="30%" align="center">Up to <a href="/~esr/sitemap.html">Site Map</a></td> -<td width="30%" align="right">$Date: 2002/07/30 13:31:23 $</td> +<td width="30%" align="right">$Date: 2002/09/17 09:36:00 $</td> </tr> </table> |