On 10/28/2015 11:04 PM, Bill Cole wrote: > On 28 Oct 2015, at 15:06, Viktor Dukhovni wrote: > >> On Wed, Oct 28, 2015 at 02:51:43PM -0400, Bill Cole wrote: >> >>> From that point onward there are 5 distinct messages. >>> >>> If those are 5 different mailing lists, subscribers to multiple lists >>> will >>> receive multiple copies. >> >> Not on properly configured systems. We're not talking about >> subscribers who are on multiple lists. Rather each list received >> 5 copies. If some subscriber was on two lists, that subscriber >> would have received 10 copies. > > I am very sorry, you are absolutely correct. I see from a more careful > reading of the rest of the thread that I definitely misinterpreted the > problem description. Thank you for pointing it out. > >>> This seems to me like it was entirely the work of the *sender* of that >>> message. A single message was sent to 5 mailing list addresses and it >>> got >>> delivered to the subscribers of each of 5 mailing lists. This is a >>> highly >>> predictable (i.e.: perfectly normal) pattern of behavior by Mailman & >>> Postfix. >> >> No, cross-posting is perfectly fine and is not the sender's fault. >> What's misconfigured is the interaction of the upstream multi-drop >> mailbox and fetchmail. >> >>> If you want the duplication to stop, get the sender to stop sending to >>> multiple lists. >> >> Please don't mislead the OP, he's got a difficult enough problem >> to address. > > Indeed, and I *THINK* (for what little that may be worth...) that it may > be addressed here: http://www.fetchmail.info/fetchmail-FAQ.html#M7 > > Fetchmail is retrieving messages that have 3 existing Received headers > like these on "message5" of the post dated "Tue, 27 Oct 2015 17:40:35 > +0100" > (Numbering and blank lines between them added for clarity): > > 1: Received: from [212.227.15.41] ([212.227.15.41]) by mx.kundenserver.de > (mxeue002) with ESMTPS (Nemesis) id 0MPww6-1Zu9SD394E-0054aD for > <mailmanser...@waldorfkindergarten-erlangen.de>; Thu, 22 Oct 2015 10:37:47 > +0200 > > 2: Received: from mout.web.de ([212.227.15.3]) by mx.kundenserver.de > (mxeue002) > with ESMTPS (Nemesis) id 0MKz7Q-1ZpBNb35bE-0006Vb for > <beis...@waldorfkindergarten-erlangen.de>; Thu, 22 Oct 2015 10:37:47 +0200 > > 3: Received: from Klamotten ([84.168.195.183]) by smtp.web.de (mrweb003) > with > ESMTPSA (Nemesis) id 0MTh7A-1Zy14E1g36-00QRsw; Thu, 22 Oct 2015 10:37:47 > +0200 > > > Headers 1 & 2 are a quirky pair: both added by nominally the same server > delivering to 2 different envelope recipients. #1 has the address > "mailmanser...@waldorfkindergarten-erlangen.de" as it does in all 5 > messages in that set (which also have identical line #3's, indicating > they were sent as one). Line #2 has the address that needs to be > detected by fetchmail: beis...@waldorfkindergarten-erlangen.de. However, > the Fetchmail FAQ and man page say only that the first Received header > is examined, implying strongly that no others will be checked if that > fails, falling back to the inherently broken scanning of To/Cc headers. > > Based on that and the Fetchmail docs, it seems to me (imperfect as my > analysis has proven to be...) that a likely solution is for the OP to > add the directive "envelope 1 Received" to the relevant stanza of his > .fetchmailrc file, telling fetchmail to skip the first Received header > in fetched messages. > Thx Bill and Viktor! as I discussed this topic in parallel in the mailman mailinglist, we came there today also to the conclusion, that fetchmail is the root cause, due to missing envelope information/maildrop capabilities.
Based on the Fetchmail docs 'envelope 1 Received' is only half of the solution. I have to set an alias for the postfix mailserver in addition cause fetchmail.log shows 'fetchmail: line rejected, mx.kundenserver.de is not an alias of the mailserver' How do I set the alias for the mailserver? BR Marco
