aboutsummaryrefslogtreecommitdiffstats
path: root/fetchmail-FAQ.html
diff options
context:
space:
mode:
Diffstat (limited to 'fetchmail-FAQ.html')
-rw-r--r--fetchmail-FAQ.html11
1 files changed, 6 insertions, 5 deletions
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html
index 712273b6..74d6394b 100644
--- a/fetchmail-FAQ.html
+++ b/fetchmail-FAQ.html
@@ -4,14 +4,13 @@
<TITLE>The Fetchmail FAQ</TITLE>
<link rev=made href=mailto:esr@snark.thyrsus.com>
<meta name="description" content="Frequently asked questions about fetchmail.">
-<meta name="keywords" content="fetchmail, POP, IMAP, remote mail">
+<meta name="keywords" content="fetchmail, POP, POP2, POP3, IMAP, remote mail">
</HEAD>
<BODY>
<H1>Frequently Asked Questions About Fetchmail</H1>
-$Id: fetchmail-FAQ.html,v 1.10 1997/05/06 07:18:59 esr Exp $<p>
-
-(New: <a href="#T2">T2</a> on using fetchmail with exim.)<p>
+The current version of fetchmail is 3.9.3. New in the FAQ: <a
+href="#T2">T2</a> on using fetchmail with exim.<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
@@ -154,7 +153,7 @@ If the bug involves a core dump or hang, a gdb stack trace is good to have.
giving the process ID as a second argument.)<p>
Best of all is a mail file which, when fetched, will reproduce the
-bug.<p>
+bug under the latest (current) version.<p>
Any bug I can reproduce will usually get fixed very quickly, often
within 48 hours. Bugs I can't reproduce are a crapshoot. If the
@@ -948,6 +947,8 @@ 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>
+$Id: fetchmail-FAQ.html,v 1.11 1997/05/07 15:49:28 esr Exp $<p>
+
<HR>
<ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com">&lt;esr@snark.thyrsus.com&gt;</A></ADDRESS>
</BODY>