Hi Jeroen, I forwared your message - not replying to show your headder: From: Jeroen Massar <jeroen@xxxxxxxxx> To: Keith Moore <moore@xxxxxxxxxx> Cc: ietf@xxxxxxxx So you had sent to moore@xxxxxxxxxxx ietf@xxxxxxxx received only a copy. Some people might have got nothing. My own Mozilla/Thunderbird behaves the same way: I would have had to manually change to/cc for all recipients. That is what we all need to do now if I got it correctly. Regards Peter and Karin -------- Original Message -------- Return-Path: <ietf-bounces@xxxxxxxx> X-Flags: 0000 Delivered-To: GMX delivery to peter@xxxxxxxxxxxxxxxx Received: (qmail invoked by alias); 26 Aug 2005 07:24:30 -0000 Received: from megatron.ietf.org (EHLO megatron.ietf.org) [132.151.6.71] by mx0.gmx.net (mx032) with SMTP; 26 Aug 2005 09:24:30 +0200 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8YRC-0004bw-Fw; Fri, 26 Aug 2005 03:15:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8YR9-0004ao-Fl for ietf@xxxxxxxxxxxxxxxxx; Fri, 26 Aug 2005 03:15:39 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02085 for <ietf@xxxxxxxx>; Fri, 26 Aug 2005 03:15:38 -0400 (EDT) Received: from 213-136-24-43.adsl.bit.nl ([213.136.24.43] helo=purgatory.unfix.org ident=postfix) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8YRo-0002xE-QX for ietf@xxxxxxxx; Fri, 26 Aug 2005 03:16:22 -0400Received: from firenze.zurich.ibm.com (pat.zurich.ibm.com [195.176.20.45]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by purgatory.unfix.org (Postfix) with ESMTP id 7A73D7FAD; Fri, 26 Aug 2005 09:14:59 +0200 (CEST)
From: Jeroen Massar <jeroen@xxxxxxxxx> To: Keith Moore <moore@xxxxxxxxxx> In-Reply-To: <20050825182001.28000793.moore@xxxxxxxxxx> References: <20050825182001.28000793.moore@xxxxxxxxxx> Organization: Unfix Date: Fri, 26 Aug 2005 09:14:55 +0200 Message-Id: <1125040495.2232.41.camel@xxxxxxxxxxxxxxxxxxxxxx> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: ietf@xxxxxxxx Subject: Re: regarding IETF lists using mailman: nodupes considered harmful X-BeenThere: ietf@xxxxxxxx X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF-Discussion <ietf.ietf.org> List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@xxxxxxxx?subject=unsubscribe> List-Post: <mailto:ietf@xxxxxxxx> List-Help: <mailto:ietf-request@xxxxxxxx?subject=help> List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@xxxxxxxx?subject=subscribe> Content-Type: multipart/mixed; boundary="===============0208067608==" Sender: ietf-bounces@xxxxxxxx Errors-To: ietf-bounces@xxxxxxxx X-GMX-Antivirus: 0 (no virus found) X-GMX-Antispam: 0 (Sender is in whitelist: ietf-bounces@xxxxxxxx) X-GMX-UID: 4aZ8Y7wSeSEkUtTJ43QhaXN1IGRvb0Ch On Thu, 2005-08-25 at 18:20 -0400, Keith Moore wrote: <SNIP>
Specifics: Mailman has a per-recipient setting called "nodupes". The effect of this setting is that any recipient address that has the nodupes flag set, and which appears in a To or CC field of a message sent to the list, will not receive a copy of the message from the list.
But they _should_ be getting the message directly already, because of the CC: or To:. Or is there something which causes the person not to get it? Indeed when some 'malicious' person would add Cc's/To's and would instruct his SMTP to not forward to the additional addresses in the Cc/To the users will effectively not receive the message. Or when the recipient doesn't accept messages to $list@xxxxxxxx + himself, and expects everything to come from the list directly. But how exactly does this cause a problem? Greets, Jeroen -- Peter and Karin Dambier Public-Root Graeffstrasse 14 D-64646 Heppenheim +49-6252-671788 (Telekom) +49-179-108-3978 (O2 Genion) +49-6252-750308 (VoIP: sipgate.de) +1-360-448-1275 (VoIP: freeworldialup.com) mail: peter@xxxxxxxxxxxxxxxx http://iason.site.voila.fr http://www.kokoom.com/iason
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf