Re: [Asrg] Summary of junk button discussion

Alessandro Vesely <vesely@tana.it> Tue, 02 March 2010 08:52 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 2F3D63A67FB for <asrg@core3.amsl.com>; Tue, 2 Mar 2010 00:52:19 -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 rL8clvqeITQw for <asrg@core3.amsl.com>; Tue, 2 Mar 2010 00:52:18 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id F17AE3A82A8 for <asrg@irtf.org>; Tue, 2 Mar 2010 00:52:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tana.it; s=test; t=1267519933; bh=McnBe9b6/VjYPs4CtGMrgWQITjcUb4Hn2cyslSkiHr4=; l=1078; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ae9me8E+rkCqS1Ls1gyeqG4WmhokrUbbxby04sICX771HspzJdNlQPChutGn4XzTY DpyeqokNxMeFOFU+mLag6eCSz3bbMTuib9+/0/agRAk/jmPdaVn9hgHAQ4KolFfFXJ WQ9qkDYNVEsnB2bdhsLgs8ZCmHDWyhQzbXc1//AU=
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 09:52:13 +0100 id 00000000005DC02F.000000004B8CD1BD.00000B44
Message-ID: <4B8CD1BC.9000901@tana.it>
Date: Tue, 02 Mar 2010 09:52:12 +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: <20100301192508.57924.qmail@simone.iecc.com>
In-Reply-To: <20100301192508.57924.qmail@simone.iecc.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Summary of junk button discussion
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 08:52:19 -0000

On 01/Mar/10 20:25, John Levine wrote:
>> This is very sensible, but when you say "single<user action>", are you voicing support for the notion that only a single bit of data will be transmitted? Or will the vocabulary be richer than that? How about an extensible vocabulary?
>
> If it sends an ARF report, you can put whatever you want in the ARF, although I wouldn't want to attempt to standardize a lot of stuff that nobody uses.

But what is the relationship between the report and the button? 
Apparently, "single<user action>" excludes automated reports.

> If you want to encode stuff in the ARF report to say whether the opinion is from a human or from software, you can, although it is again not clear how useful that would be.

That field may be useful in sorting out a report's consumers in a 
generalized FBL. Some mailbox providers notify via FBL when users hit 
that button, but not when messages are automatically blocked.

Also, humans make errors in a different way than software, hence any 
correction mechanism should be differently tailored.