Re: [Asrg] Adding a spam button to MUAs

Ian Eiloart <iane@sussex.ac.uk> Mon, 21 December 2009 12:44 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 3DF6D3A6995 for <asrg@core3.amsl.com>; Mon, 21 Dec 2009 04:44:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.776
X-Spam-Level:
X-Spam-Status: No, score=-0.776 tagged_above=-999 required=5 tests=[AWL=-0.747, BAYES_40=-0.185, 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 85pV4vYdlwN5 for <asrg@core3.amsl.com>; Mon, 21 Dec 2009 04:44:28 -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 2E79C3A6804 for <asrg@irtf.org>; Mon, 21 Dec 2009 04:44:27 -0800 (PST)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.134.43]:53076) by sivits.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KV063W-000I5R-FB; Mon, 21 Dec 2009 12:45:32 +0000
Date: Mon, 21 Dec 2009 12:44:02 +0000
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: dcrocker@bbiw.net, Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <7900A9D500C81291D8931A75@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <4B2E61EB.1050009@dcrocker.net>
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> <AF09C4BE1E9DB501F0D2CDF3@paine.local> <4B2E61EB.1050009@dcrocker.net>
Originator-Info: login-token=Mulberry:01fG1BIuXOr4e92pWE6JPv4rSV4uVifN+T8dg=; token_authority=support@its.sussex.ac.uk
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: Mon, 21 Dec 2009 12:44:29 -0000

--On 20 December 2009 09:42:03 -0800 Dave CROCKER <dhc@dcrocker.net> wrote:

>
>
> On 12/20/2009 4:09 AM, Ian Eiloart wrote:
>> 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.
>
>
> Only if there is reason to believe the buttons are being used
> consistently and validly and without negative impact.  The mere existence
> of the buttons guarantees neither of the first two.

Think of the user as a voter instead of a judge and jury, when they click 
the "report" button.

Of course, a "block" button is purely an expression of wish - though you 
might want to have them confirm a block, and undo would be useful too.

What we already do know is that many people use "report as spam" when they 
mean "block". Why? Because they have no alternative.

>
> What the mere existence of the buttons DOES guarantee is greater
> complexity to the user interface.
>
> d/



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