Re: regarding IETF lists using mailman: nodupes considered harmful

Jeroen Massar <jeroen@unfix.org> Fri, 26 August 2005 07:15 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8YRB-0004bw-HZ; Fri, 26 Aug 2005 03:15:41 -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@megatron.ietf.org; 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@ietf.org>; 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@ietf.org; Fri, 26 Aug 2005 03:16:22 -0400
Received: 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@unfix.org>
To: Keith Moore <moore@cs.utk.edu>
In-Reply-To: <20050825182001.28000793.moore@cs.utk.edu>
References: <20050825182001.28000793.moore@cs.utk.edu>
Organization: Unfix
Date: Fri, 26 Aug 2005 09:14:55 +0200
Message-Id: <1125040495.2232.41.camel@firenze.zurich.ibm.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.2.3
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: ietf@ietf.org
Subject: Re: regarding IETF lists using mailman: nodupes considered harmful
X-BeenThere: ietf@ietf.org
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@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0208067608=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

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@ietf.org +
himself, and expects everything to come from the list directly.

But how exactly does this cause a problem?

Greets,
 Jeroen


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf