From 609231042254dd5e1cc5f9071dfd972ee6856396 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Mon, 31 Jan 2000 04:07:30 +0000 Subject: Added M8. svn path=/trunk/; revision=2721 --- fetchmail-FAQ.html | 26 ++++++++++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) (limited to 'fetchmail-FAQ.html') diff --git a/fetchmail-FAQ.html b/fetchmail-FAQ.html index f182dfc1..6107b829 100644 --- a/fetchmail-FAQ.html +++ b/fetchmail-FAQ.html @@ -10,7 +10,7 @@
Back to Fetchmail Home Page To Site Map -$Date: 2000/01/29 20:01:01 $ +$Date: 2000/01/31 04:07:30 $

Frequently Asked Questions About Fetchmail

@@ -124,6 +124,7 @@ messages but before deleting them
M6. How do I get multidrop mode to work with majordomo?
M7. Multidrop mode isn't parsing envelope addresses from my Received headers as it should.
+M8. Users are getting multiple copies of messages.

Mangled mail:

@@ -2224,6 +2225,27 @@ before accepting `ksturgeon@fbceg.org' as an envelope address. This check might fail if your DNS were misconfigured, or if you were using `no dns' and had failed to declare iserv.ttns.net as an alias of your server.

+

+

M8. Users are getting multiple copies of messages.

+ +It's a consequence of multidrop. What's happening is that you have +N users subscribed to the same list. The list software sends N +copies, not knowing they will end up in the same multidrop box. Since +they are both locally addressed to all N users, fetchmail delivers N +copies to each user.

+ +Fetchmail tries to eliminate adjacent duplicate messages in a +multidrop mailbox. However, this logic depends on the message-ID +being identical in both copies. It also depends on the two copies +being adjacent in the server mailbox. The former is usually the case, +but the latter condition sometimes fails in a timing-dependent way if +the server was processing multiple incoming mail streams. + +I could eliminate this problem by keeping a list of all message-IDs +received during a poll so far and dropping any message that matches a +seen mail ID. The touble is that this is an O(N**2) operation that +might significantly slow down the retriweval of large mail batches.

+

X1. Spurious blank lines are appearing in the headers of fetched mail.

@@ -2556,7 +2578,7 @@ terminate it.

Back to Fetchmail Home Page To Site Map -$Date: 2000/01/29 20:01:01 $ +$Date: 2000/01/31 04:07:30 $

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