regarding IETF lists using mailman: nodupes considered harmful
Keith Moore <moore@cs.utk.edu> Thu, 25 August 2005 22:20 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8Q4u-0002iq-3W; Thu, 25 Aug 2005 18:20:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E8Q4r-0002iR-SH for ietf@megatron.ietf.org; Thu, 25 Aug 2005 18:20:05 -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 SAA24381 for <ietf@ietf.org>; Thu, 25 Aug 2005 18:20:03 -0400 (EDT)
Received: from shu.cs.utk.edu ([160.36.56.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E8Q5S-0004OF-H5 for ietf@ietf.org; Thu, 25 Aug 2005 18:20:43 -0400
Received: from localhost (shu [127.0.0.1]) by shu.cs.utk.edu (Postfix) with ESMTP id E0FE213B41 for <ietf@ietf.org>; Thu, 25 Aug 2005 18:20:03 -0400 (EDT)
Received: from shu.cs.utk.edu ([127.0.0.1]) by localhost (shu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29226-01; Thu, 25 Aug 2005 18:20:02 -0400 (EDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43]) by shu.cs.utk.edu (Postfix) with ESMTP id 26E7F13B31; Thu, 25 Aug 2005 18:20:02 -0400 (EDT)
Date: Thu, 25 Aug 2005 18:20:01 -0400
From: Keith Moore <moore@cs.utk.edu>
To: ietf@ietf.org
Message-Id: <20050825182001.28000793.moore@cs.utk.edu>
X-Mailer: Sylpheed version 2.0.0rc (GTK+ 2.6.7; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new with ClamAV and SpamAssasin at cs.utk.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Content-Transfer-Encoding: 7bit
Subject: 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>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
I'm sending this to the ietf list because mailman is widely used for IETF mailing lists. Recent versions of mailman appear to have a flaw that allows the sender of a message to send a copy to everyone in a mailing list _except_ some set of explicitly specified recipients, and there will be no indication that those recipients were excluded. In the context of an IETF mailing list this can be used to exclude participation by certain individuals. 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. It also appears (from emperical testing with a limited sample) that the list may also remove that recipient's address from the CC field of the copy of the message sent to the list. Recent versions of mailman set "nodupes" by default. List participants can change it if they know about it, but they might have no idea of how this setting works and how it can be used to exclude them from participation. The workaround is to set "new_member_options" (under General Options) so that "Filter out duplicate messages to list members" is NOT set. "Do not send a copy of a member's own post" should probably not be set either. Keith _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- regarding IETF lists using mailman: nodupes consi… Keith Moore
- Re: regarding IETF lists using mailman: nodupes c… Jeroen Massar
- Re: regarding IETF lists using mailman: nodupes c… Ken Raeburn
- Re: regarding IETF lists using mailman: nodupes c… Jari Arkko
- Re: regarding IETF lists using mailman: nodupes c… Ken Raeburn
- Re: regarding IETF lists using mailman: nodupes c… Jeroen Massar
- Re: regarding IETF lists using mailman: nodupes c… Bill Fenner
- Re: regarding IETF lists using mailman: nodupes c… Bill Fenner