aboutsummaryrefslogtreecommitdiffstats
path: root/fetchmail-FAQ.html
diff options
context:
space:
mode:
Diffstat (limited to 'fetchmail-FAQ.html')
-rw-r--r--fetchmail-FAQ.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index 5cd9e888..16bf5ffe 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -10,7 +10,7 @@
<table width="100%" cellpadding=0><tr>
<td width="30%">Back to <a href="index.html">Fetchmail Home Page</a>
<td width="30%" align=center>To <a href="/~esr/sitemap.html">Site Map</a>
-<td width="30%" align=right>$Date: 1997/10/03 16:22:54 $
+<td width="30%" align=right>$Date: 1997/10/03 16:24:26 $
</table>
<HR>
<H1>Frequently Asked Questions About Fetchmail</H1>
@@ -1133,7 +1133,7 @@ more often.<P>
Qualcomm's qpopper, used at many BSD Unix sites, is better behaved.
If its connection is dropped, it will first execute all DELE commands (as
though you had issued an QUIT -- this is a technical violation of
-the RFCs, but a good idea in a world of flaky phone lines)f. Then it
+the RFCs, but a good idea in a world of flaky phone lines). Then it
will re-queue any message that was being downloaded at hangup time.
Still, qpopper may require a noticeable amount of time to do deletions
and clean up its queue. (Fetchmail waits a bit before retrying in
@@ -1549,7 +1549,7 @@ will look right.<p>
<table width="100%" cellpadding=0><tr>
<td width="30%">Back to <a href="index.html">Fetchmail Home Page</a>
<td width="30%" align=center>To <a href="/~esr/sitemap.html">Site Map</a>
-<td width="30%" align=right>$Date: 1997/10/03 16:22:54 $
+<td width="30%" align=right>$Date: 1997/10/03 16:24:26 $
</table>
<P><ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com">&lt;esr@snark.thyrsus.com&gt;</A></ADDRESS>