Re: IESG Statement on Spam Control on IETF Mailing Lists

"Frank Ellermann" <nobody@xyzzy.claranet.de> Wed, 16 April 2008 17:40 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 3D8843A6FA6; Wed, 16 Apr 2008 10:40:58 -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 864023A6F8F for <ietf@core3.amsl.com>; Wed, 16 Apr 2008 10:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.284
X-Spam-Level:
X-Spam-Status: No, score=-3.284 tagged_above=-999 required=5 tests=[AWL=0.315, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 zTK6mHd+2YGS for <ietf@core3.amsl.com>; Wed, 16 Apr 2008 10:40:55 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id 97DE328C129 for <ietf@ietf.org>; Wed, 16 Apr 2008 10:40:48 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JmBdK-0002Pk-Qd for ietf@ietf.org; Wed, 16 Apr 2008 17:41:22 +0000
Received: from hmbg-d9b88e1e.pool.mediaways.net ([217.184.142.30]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Wed, 16 Apr 2008 17:41:22 +0000
Received: from nobody by hmbg-d9b88e1e.pool.mediaways.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Wed, 16 Apr 2008 17:41:22 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Subject: Re: IESG Statement on Spam Control on IETF Mailing Lists
Date: Wed, 16 Apr 2008 19:44:11 +0200
Organization: <http://purl.net/xyzzy>
Lines: 35
Message-ID: <fu5dnq$rlm$1@ger.gmane.org>
References: <20080414153938.0A5153A6D4D@core3.amsl.com><2788466ED3E31C418E9ACC5C316615572EF8A7@mou1wnexmb09.vcorp.ad.vrsn.com><20080414172440.7E8943A6D83@core3.amsl.com><fu09c7$bmo$1@ger.gmane.org><0777EA1F1E2A51AD8911566F@[192.168.1.2]> <fu36uq$nj$1@ger.gmane.org> <45EF9D81559100FD53D24655@[192.168.1.2]>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e1e.pool.mediaways.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
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

James Galvin wrote:

> Or did you mean some other form?

Yes, not the "request list" form, I've never used it.

I meant IETF -> lists -> note well -> other lists ->
non-WG -> non-WG posting page (five clicks deep ;-)
<https://datatracker.ietf.org/list/nonwg/update/> ->
step 1 "add new entry" -> proceed -> step 2 **THIS**.

 [gateway old <-> new list instead of list <-> archive]
> what it facilitates is using the same mechanisms in
> the same way to control the SPAM problem.  It is an
> operational simplification that obviates a bifurcation.

If it obviates bifurcation I didn't get what you were
talking about.  Maybe you want to *replace* the old 
list elsewhere by a new list at ietf.org, preserving
only the subscriptions.  

IME moving lists or groups, just renaming them, is a 
guaranteed way to lose 80% of all readers forever, and
annoying a significant part of the rest.  The "other
lists" have owners, why should they hand over their
list to the IETF ?  Change as much as lists.ietf.org
to ietf.org and it will cause havoc somewhere, and
months to figure out what's broken. 

As an example, from my POV two review lists are dead,
and I will dump review requests directly to iesg@ or
whatever it takes to get them on public record (it's
a formal thing, "tried to send" is not good enough ;-)

 Frank

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