Re: [Asrg] Adding a spam button to MUAs

Ian Eiloart <iane@sussex.ac.uk> Sun, 20 December 2009 12:09 UTC

Return-Path: <iane@sussex.ac.uk>
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 AC9093A6846 for <asrg@core3.amsl.com>; Sun, 20 Dec 2009 04:09:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.157
X-Spam-Level:
X-Spam-Status: No, score=0.157 tagged_above=-999 required=5 tests=[BAYES_50=0.001, 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 s1rGurAwnMM0 for <asrg@core3.amsl.com>; Sun, 20 Dec 2009 04:09:34 -0800 (PST)
Received: from sivits.uscs.susx.ac.uk (sivits.uscs.susx.ac.uk [139.184.14.88]) by core3.amsl.com (Postfix) with ESMTP id BED823A67B2 for <asrg@irtf.org>; Sun, 20 Dec 2009 04:09:32 -0800 (PST)
Received: from ianeiloart.plus.com ([212.159.124.126]:60494 helo=[192.168.1.13]) by sivits.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KUY9TM-000FB1-JU for asrg@irtf.org; Sun, 20 Dec 2009 12:10:35 +0000
Date: Sun, 20 Dec 2009 12:09:09 +0000
From: Ian Eiloart <iane@sussex.ac.uk>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <AF09C4BE1E9DB501F0D2CDF3@paine.local>
In-Reply-To: <4B2A7E8D.8060104@nd.edu>
References: <alpine.BSF.2.00.0912082138050.20682@simone.lan> <20091216014800.GA29103@gsp.org> <DBF77720-200E-4846-949F-924388F9CC15@blighty.com> <20091216120742.GA28622@gsp.org> <20091216185904.3B9032421D@panix5.panix.com> <4B296458.5070603@mail-abuse.org> <16C1C8A4-D223-435B-93BC-A9D44F5965A1@guppylake.com> <B14EC7430355853625D0D4EA@lewes.staff.uscs.susx.ac.uk> <BBF2AC03-3C88-4557-9346-343347C196A9@guppylake.com> <240DB04672256506ED548857@lewes.staff.uscs.susx.ac.uk> <4B2A7E8D.8060104@nd.edu>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Sussex: true
X-Sussex-transport: remote_smtp
Subject: Re: [Asrg] Adding a spam button to MUAs
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: Sun, 20 Dec 2009 12:09:35 -0000

--On 17 December 2009 13:55:09 -0500 Paul Russell <prussell@nd.edu> wrote:

> On 12/17/2009 13:04, Ian Eiloart wrote:
>> Anyway, the worst case scenario is that users hit one of the two buttons
>> at  random. In that situation, you simply treat the buttons as
>> equivalent, and  take the same action for each.
>>
>
> If you're going to do that, why do you need two buttons?

I'm not going to do that - it's a worst case scenario. I don't believe it's 
necessary with my users. However, some people have such low opinion of 
their users that they might well wish to do that.

The point is that if your users have a mail client with two buttons, it's 
capable of making a distinction that will be useful to some admins. Other 
admins my chose not to make use of the distinction, but if you extinguish 
the information before it reaches the admin, then it's impossible to 
reconstruct it.



-- 
Ian Eiloart
IT Services, University of Sussex
01273-873148 x3148
For new support requests, see http://www.sussex.ac.uk/its/help/