From b257b8ceac0f8bfefee354f7a5d3aafb2592e658 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Sun, 7 Sep 1997 01:55:50 +0000 Subject: Added O4. svn path=/trunk/; revision=1319 --- fetchmail-FAQ.html | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index 520598d6..0ee4539d 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -10,7 +10,7 @@
Back to Fetchmail Home Page To Site Map -$Date: 1997/09/03 22:32:50 $ +$Date: 1997/09/07 01:55:50 $

Frequently Asked Questions About Fetchmail

@@ -88,6 +88,8 @@ when I may have multiple login sessions going?
O2. Every time I get a POP or IMAP message the header is dumped to all my terminal sessions.
O3. Does fetchmail reread its rc file every poll cycle?
+O4. Why do deleted messages show up again when I take +a line hit while downloading?

Answers:

@@ -1241,11 +1243,30 @@ to solve the problem system-wide.

No. Fetchmail only reads the rc file once, when it starts up. To force an rc file reread, do fetchmail -q; fetchmail.

+

+

O4. Why do deleted messages show up again when I take +a line hit while downloading?

+ +Because you're using a POP2 or POP3 server. According to the POP3 RFCs, +deletes aren't actually performed until you issue the end-of-session +QUIT command. Fetchmail cannot fix this, it takes cooperation from the. +server. There are two possible remedies:

+ +One is to switch to qpopper (the freeware POP3 server from Qualcomm, +the Eudora people). The qpopper software violates the POP3 RFCs by +doing an expunge (removing deleted messages) on a line hangup, as well +as on processing a QUIT command.

+ +The other (which we recommend) is to switch to IMAP. IMAP has an explicit +expunge command and fetchmail uses it to delete messages quickly after +they are downloaded.

+

Back to Fetchmail Home Page To Site Map -$Date: 1997/09/03 22:32:50 $ +$Date: 1997/09/07 01:55:50 $

Eric S. Raymond <esr@snark.thyrsus.com>
-- cgit v1.2.3