IETF Logo Mail Archive

Re: IESG Statement on Spam Control on IETF Mailing Lists

Eliot Lear <lear@cisco.com> Mon, 14 April 2008 18:13 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 4FB1028C1C5; Mon, 14 Apr 2008 11:13:08 -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 8363828C18A for <ietf@core3.amsl.com>; Mon, 14 Apr 2008 11:13:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 yyB17l8gIBaW for <ietf@core3.amsl.com>; Mon, 14 Apr 2008 11:13:04 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 1F43A3A6A65 for <ietf@ietf.org>; Mon, 14 Apr 2008 11:13:03 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.25,656,1199660400"; d="scan'208";a="6252834"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 14 Apr 2008 20:13:23 +0200
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m3EIDN8x029934; Mon, 14 Apr 2008 20:13:23 +0200
Received: from adsl-247-3-fixip.tiscali.ch (ams3-vpn-dhcp4557.cisco.com [10.61.81.204]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m3EIDNfk026844; Mon, 14 Apr 2008 18:13:23 GMT
Message-ID: <48039EC3.6010108@cisco.com>
Date: Mon, 14 Apr 2008 20:13:23 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: IESG Statement on Spam Control on IETF Mailing Lists
References: <20080414153938.0A5153A6D4D@core3.amsl.com> <2788466ED3E31C418E9ACC5C316615572EF8A7@mou1wnexmb09.vcorp.ad.vrsn.com> <20080414172440.7E8943A6D83@core3.amsl.com>
In-Reply-To: <20080414172440.7E8943A6D83@core3.amsl.com>
X-Enigmail-Version: 0.95.6
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=698; t=1208196803; x=1209060803; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20IESG=20Statement=20on=20Spam=20Control= 20on=20IETF=20Mailing=20Lists |Sender:=20; bh=odVuo7LcEyxUTb+gUWAqS7ijGP6S/JtoZ9r0hDWDHvg=; b=dzWt+0aU0IE2ix669uxWPQnUmfrcn6aTQcyYaM1b0vEyAjCqoytrDgZdKc ZjEH1xsGuXVrP5mhAxynyMfWfbbjj6zpizDIQyO8wVzRan9rcYgNHsxafS4O I0UEBrqCel;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
Cc: IETF Discussion <ietf@ietf.org>
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

Russ,

> When IETF lists are housed somewhere other than ietf.org, they are 
> supposed to include an archive recipient so that there is an archive 
> available at ietf.org (perhaps in addition to the one kept at the 
> place where the list is housed).
>   

I'll agree with Phill's conclusion on this one.

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.   Also, it  probably is easier to effect and audit policy 
(such as we have any) in terms of message retention, uniform access, etc.

Regards,

Eliot


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

v2.23.0 | Report a Bug | By Email