diff options
| -rw-r--r-- | fetchmail-FAQ.html | 9 |
1 files changed, 7 insertions, 2 deletions
diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index f6ade859..84b93f35 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: 2001/02/23 08:28:11 $ +<td width="30%" align=right>$Date: 2001/03/07 20:09:05 $ </table> <HR> <H1>Frequently Asked Questions About Fetchmail</H1> @@ -264,6 +264,11 @@ 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 you upgraded your fetchmail and something broke, you should include +session transcripts with -v -v of both the working and failing +versions. Very often, the source of the problem can instantly +identified by looking at the differences in protocol transactions.<P> + If the bug involves a core dump or hang, a gdb stack trace is good to have. (Bear in mind that you can attach gdb to a running but hung process by giving the process ID as a second argument.) You will need to @@ -2922,7 +2927,7 @@ switching to IMAP and using a short expunge interval.<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: 2001/02/23 08:28:11 $ +<td width="30%" align=right>$Date: 2001/03/07 20:09:05 $ </table> <P><ADDRESS>Eric S. Raymond <A HREF="mailto:esr@thyrsus.com"><esr@snark.thyrsus.com></A></ADDRESS> |