Re: [Asrg] Summary/outline of why the junk button idea is pre-failed

"Chris Lewis" <clewis@nortel.com> Tue, 02 March 2010 19:32 UTC

Return-Path: <CLEWIS@nortel.com>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 961083A8C75 for <asrg@core3.amsl.com>; Tue, 2 Mar 2010 11:32:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.443
X-Spam-Level:
X-Spam-Status: No, score=-6.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156]
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 E59pd87b8iUt for <asrg@core3.amsl.com>; Tue, 2 Mar 2010 11:32:43 -0800 (PST)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56]) by core3.amsl.com (Postfix) with ESMTP id A9FF43A8C6B for <asrg@irtf.org>; Tue, 2 Mar 2010 11:32:43 -0800 (PST)
Received: from zrtphxs1.corp.nortel.com (zrtphxs1.corp.nortel.com [47.140.202.46]) by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id o22JWf715289 for <asrg@irtf.org>; Tue, 2 Mar 2010 19:32:41 GMT
Received: from zrtphx5h0.corp.nortel.com ([47.140.202.65]) by zrtphxs1.corp.nortel.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 2 Mar 2010 14:32:41 -0500
Received: from [47.130.64.139] (47.130.64.139) by zrtphx5h0.corp.nortel.com (47.140.202.65) with Microsoft SMTP Server (TLS) id 8.1.340.0; Tue, 2 Mar 2010 14:32:40 -0500
Message-ID: <4B8D67D7.6030703@nortel.com>
Date: Tue, 02 Mar 2010 14:32:39 -0500
From: Chris Lewis <clewis@nortel.com>
Organization: Nortel
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: asrg@irtf.org
References: <20100302131810.GA22938@gsp.org> <Pine.GSO.4.64.1003020824500.16639@nber6.nber.org> <20100302155638.GA2653@gsp.org> <Pine.GSO.4.64.1003021158110.14693@nber6.nber.org>
In-Reply-To: <Pine.GSO.4.64.1003021158110.14693@nber6.nber.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Mar 2010 19:32:41.0420 (UTC) FILETIME=[1FE3A8C0:01CABA3F]
Subject: Re: [Asrg] Summary/outline of why the junk button idea is pre-failed
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2010 19:32:44 -0000

On 3/2/2010 12:12 PM, Daniel Feenberg wrote:

> There is one argument, not made by Kulawiec that does deserve a response.
> That is the underlying problem with the TIS button that is real. It will
> generate ARFs that are really just list-unsubscribe requests from
> perfectly legitimate sources. It will generate these in large numbers and
> it will be impractical to reduce them with user education. Anyone
> proposing to process the flood of such messages will have to come up with
> an economical way of doing so that doesn't inconvenience the list owners.

Having the report recipient automatically utilize the list unsubscribe 
headers present in the headers immediately comes to mind.

> In fact, I think most of the opposition to the TIS button comes from the
> owners of such lists who feel they would be the victims. To some extent
> they are justified - they are following the rules, why should they pay a
> penalty. But if the penalty were a small change in their operation, say an
> improvement in the standardization of list-unsubscribe headers - it might
> be justifiable.

I think most of us would be satisfied with improvements in the 
_adoption_ of the existing list unsubscribe headers.