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

Alessandro Vesely <vesely@tana.it> Tue, 02 March 2010 14:46 UTC

Return-Path: <vesely@tana.it>
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 9830E28C102 for <asrg@core3.amsl.com>; Tue, 2 Mar 2010 06:46:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.563
X-Spam-Level:
X-Spam-Status: No, score=-4.563 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 P3QmB2V-q3h0 for <asrg@core3.amsl.com>; Tue, 2 Mar 2010 06:46:02 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 4170B28C0FC for <asrg@irtf.org>; Tue, 2 Mar 2010 06:46:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tana.it; s=test; t=1267541162; bh=PXUZF8we2dgv2jaWjZHD3+OsXZT1uT1Lgkbi4vtZwHc=; l=2216; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Type:Content-Transfer-Encoding; b=aO41I2bv2khCbhdpM7IEoJtz4ye09qCjQ2WPcxFTkOiZxYxZmrV6MI511jdHAsmep /VOh7dDrl1fplpkEt5RQatqYYvMxMQYC4Xv6KjDtqjZ1iMjdn5p635MGhLddP1sB1L c4mETNKum9L7HpAhCSQ4OhsxK7JKhanx3Sc8S5iY=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 02 Mar 2010 15:46:02 +0100 id 00000000005DC02F.000000004B8D24AA.00001DA2
Message-ID: <4B8D24A9.5060605@tana.it>
Date: Tue, 02 Mar 2010 15:46:01 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: asrg@irtf.org
References: <20100302131810.GA22938@gsp.org> <Pine.GSO.4.64.1003020824500.16639@nber6.nber.org>
In-Reply-To: <Pine.GSO.4.64.1003020824500.16639@nber6.nber.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
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 14:46:03 -0000

On 02/Mar/10 14:40, Daniel Feenberg wrote:
> On Tue, 2 Mar 2010, Rich Kulawiec wrote:
>
>> This is a *summary* and not an attempt to provide every nuance of every argument, so nitpicking is discouraged.  You may rest assured that I read the traffic on this list and have been paying close attention to the spam problem for the past several decades. ;-)
>
> This message ignores the existence of TIS buttons on existing MUAs for webmail operators, and the actual experience that those operators have.

In addition, it apparently assumes that users send reports directly to 
spammers.

>> 5. Duplicates existing functionality
>>
>>     All competently-run sites support the RFC 2142-stipulated
>>     "abuse" role address and have appropriately experienced,
>>     trained, qualified and diligent staff reading every message
>>     sent there.  It's trivially easy for any user to forward
>>     questionable mail traffic (with full headers of course) to
>>     the abuse address of their own mail provider, who can then
>>     decide what to do about it.  These personnel are far better
>>     situated to decipher headers, correlate against logs,
>>     assess threat severity, etc.  They're also much less likely --
>>     presuming that they're competent -- to hand over useful
>>     information to the enemy.  See next point as well.
>>
>
> I have never gotten a usefull spam complaint from a user, but it isn't because the messages weren't spam. It was always because the user didn't include the headers. All users find it difficult to include headers with forwarded messages, and will always drop the issue when asked to resend with headers. The TIS button solves this problem.

+1, we're just talking about a neat and convenient tool to send 
complaints. Extra optimizations, such as using an IMAP flag to 
simultaneously synchronize with server's Bayesian data, move a message 
to a different folder, _and_ send the complaint, are possible for more 
competent users.

If spammers want to abuse abuse@ mailboxes, they can do so now, 
without having to wait for those buttons. The button makes that job 
easier for the user. The spammer (or 0wner) probably has easier ways.