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 3d5bb89e..e0c4a691 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: 1998/10/16 14:00:02 $
+<td width="30%" align=right>$Date: 1998/10/17 15:10:42 $
</table>
<HR>
<H1>Frequently Asked Questions About Fetchmail</H1>
@@ -207,10 +207,11 @@ lots of ways for other programs in the mail chain to screw up that
look like fetchmail's fault, but you may be able to fix these by
tweaking your configuration.<P>
-A transcript of the failed session with -v on is almost always useful.
+A transcript of the failed session with -v -v (yes, that's
+<em>two</em> -v options, enabling debug mode) will almost always be useful.
It is very important that the transcript include your POP/IMAP server's
-greeting line, so I can identify it in case of server problems. Doing
-this will not reveal your passwords, which are specially masked
+greeting line, so I can identify it in case of server problems. This
+transcript will not reveal your passwords, which are specially masked
out precisely so the transcript can be passed around.<P>
If the bug involves a core dump or hang, a gdb stack trace is good to have.
@@ -2181,7 +2182,7 @@ Re-ordering messages is a user-agent function, anyway.<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: 1998/10/16 14:00:02 $
+<td width="30%" align=right>$Date: 1998/10/17 15:10:42 $
</table>
<P><ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com">&lt;esr@snark.thyrsus.com&gt;</A></ADDRESS>