IETF Logo Mail Archive

Re: IESG Statement on Spam Control on IETF Mailing Lists

Rich Kulawiec <rsk@gsp.org> Tue, 15 April 2008 16:37 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7703F3A6AD7; Tue, 15 Apr 2008 09:37:53 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 327D83A67F9 for <ietf@core3.amsl.com>; Mon, 14 Apr 2008 11:36:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level:
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iC9gfcNP9dmK for <ietf@core3.amsl.com>; Mon, 14 Apr 2008 11:36:29 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by core3.amsl.com (Postfix) with ESMTP id 1335A28C343 for <ietf@ietf.org>; Mon, 14 Apr 2008 11:35:52 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.17.156.dsl.charm.net [207.114.17.156]) by taos.firemountain.net (8.14.1/8.14.1) with ESMTP id m3EIaKNS021109 for <ietf@ietf.org>; Mon, 14 Apr 2008 14:36:23 -0400 (EDT)
Received: from avatar.gsp.org (avatar.gsp.org [192.168.0.11]) by squonk.gsp.org (8.14.1/8.14.1) with ESMTP id m3EIXqhf019384 for <ietf@ietf.org>; Mon, 14 Apr 2008 14:33:52 -0400 (EDT)
Received: from avatar.gsp.org (localhost [127.0.0.1]) by avatar.gsp.org (8.14.1/8.14.1/Debian-8ubuntu1) with ESMTP id m3EIcuUp026894 for <ietf@ietf.org>; Mon, 14 Apr 2008 14:38:56 -0400
Received: (from rsk@localhost) by avatar.gsp.org (8.14.1/8.14.1/Submit) id m3EIcuLA026893 for ietf@ietf.org; Mon, 14 Apr 2008 14:38:56 -0400
Date: Mon, 14 Apr 2008 14:38:56 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: IESG Statement on Spam Control on IETF Mailing Lists
Message-ID: <20080414183856.GA26437@gsp.org>
References: <20080414153938.0A5153A6D4D@core3.amsl.com> <2788466ED3E31C418E9ACC5C316615572EF8A7@mou1wnexmb09.vcorp.ad.vrsn.com> <20080414172440.7E8943A6D83@core3.amsl.com> <48039EC3.6010108@cisco.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <48039EC3.6010108@cisco.com>
User-Agent: Mutt/1.5.15+20070412 (2007-04-11)
X-Mailman-Approved-At: Tue, 15 Apr 2008 09:37:51 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Mon, Apr 14, 2008 at 08:13:23PM +0200, Eliot Lear wrote:
> I think there is probably convenience value to housing the mailing lists 
> at the IETF.  It allows for a single whitelist, reduction in those 
> annoying monthly messages that we eventually all filter into the 
> bitbucket.

I'll concur with the general sentiment here, although I don't think
there's any need for DKIM or any of the other related flavor-of-the-month
technologies (SenderID, SPF, etc).

A suggestion -- to Eliot's point about monthly reminders -- would be
to consider consolidating those into a single reminder that covers all
IETF mailing lists.  This would cut down IETF-outbound mail volume as well
as per-recipient inbound mail volume, while (I think) still serving the
same function.

---Rsk
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email