aboutsummaryrefslogtreecommitdiffstats
path: root/fetchmail-FAQ.html
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>1997-06-14 18:15:57 +0000
committerEric S. Raymond <esr@thyrsus.com>1997-06-14 18:15:57 +0000
commit05581922ac0ad62541057bf2d7b5d28189d59cbc (patch)
tree9f4e997162673e9d29087107b82b6c19a1ac73c4 /fetchmail-FAQ.html
parentbeb2400cca418bc16c8b76dae8f08f7d4f9e400d (diff)
downloadfetchmail-05581922ac0ad62541057bf2d7b5d28189d59cbc.tar.gz
fetchmail-05581922ac0ad62541057bf2d7b5d28189d59cbc.tar.bz2
fetchmail-05581922ac0ad62541057bf2d7b5d28189d59cbc.zip
Don't rely on the size being in POP3's fetch response any more.
svn path=/trunk/; revision=1098
Diffstat (limited to 'fetchmail-FAQ.html')
-rw-r--r--fetchmail-FAQ.html28
1 files changed, 3 insertions, 25 deletions
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index d236ce39..467302a6 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -9,9 +9,8 @@
<BODY>
<H1>Frequently Asked Questions About Fetchmail</H1>
-The current version of fetchmail is 4.0. New in the FAQ: <a
-href="#O5">O5</a>, on what to do if your progress messages look
-garbled, and <a href="#T5">T5</a> on the Microsoft Exchange Server.<p>
+The current version of fetchmail is 3.9.8. New in the FAQ: <a
+href="#T5">T5</a>Using fetchmail with the Microsoft Exchange Server.<p>
Before reporting any bug, please read <a href="#G3">G3</a> for advice
on how to include diagnostic information that will get your bug fixed
@@ -1015,28 +1014,7 @@ without hacking potentially fragile startup scripts. To get around
it, just touch(1) the logfile before you run fetchmail (this will have
no effect on the contents of the logfile if it already exists).<P>
-<hr>
-<h2><a name="#O5">O5. The message lengths in my POP3 progress messages look like garbage.</a></h2>
-
-Aha. You are running a server that was written to the letter of the
-never-to-be-sufficiently-damned RFC 1725, which (among other heinous
-omissions) neglected to require that the <TT>OK</TT> response to a
-<TT>FETCH</TT> include the message length in octets. Requirement or
-not, there are very few servers that actually fail to issue this
-length. <P>
-
-There is a way to compensate for this lack using the <TT>LIST</TT> ,
-command, but it would incur a possibly significant speed penalty on
-<emph>all</emph> POP3 retrievals. Instead I have opted for a hack
-that has the unavoidable side effect of garbaging the length messages.
-This will not affect actual retrieval, and the messages will not
-even be visible when you run in daemon mode.<P>
-
-To fix this problem, install a better POP3 server like qpopper. Or
-better yet, install an <a href="http://www.washington.edu/imap">IMAP</a>
-server and chuck POP3 entirely.<p>
-
-$Id: fetchmail-FAQ.html,v 1.31 1997/06/14 17:28:11 esr Exp $<p>
+$Id: fetchmail-FAQ.html,v 1.32 1997/06/14 18:15:56 esr Exp $<p>
<HR>
<ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com">&lt;esr@snark.thyrsus.com&gt;</A></ADDRESS>