Re: [Asrg] Adding a spam button to MUAs

Ian Eiloart <iane@sussex.ac.uk> Thu, 17 December 2009 18:04 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 3CB4F3A68B4 for <asrg@core3.amsl.com>; Thu, 17 Dec 2009 10:04:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.391
X-Spam-Level:
X-Spam-Status: No, score=-1.391 tagged_above=-999 required=5 tests=[AWL=-0.437, BAYES_05=-1.11, 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 ilZ6SZPfQ8pJ for <asrg@core3.amsl.com>; Thu, 17 Dec 2009 10:04:44 -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 5EFC23A6811 for <asrg@irtf.org>; Thu, 17 Dec 2009 10:04:44 -0800 (PST)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.134.43]:60755) by sivits.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KUT695-000JKY-KT for asrg@irtf.org; Thu, 17 Dec 2009 18:05:29 +0000
Date: Thu, 17 Dec 2009 18:04:19 +0000
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <240DB04672256506ED548857@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <BBF2AC03-3C88-4557-9346-343347C196A9@guppylake.com>
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>
Originator-Info: login-token=Mulberry:01yWRVwTLFwyYK0akjNYo82cg0L9x2GyyKPs8=; 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: Thu, 17 Dec 2009 18:04:45 -0000

--On 17 December 2009 12:33:59 -0500 Nathaniel Borenstein 
<nsb@guppylake.com> wrote:

>
> On Dec 17, 2009, at 11:27 AM, Ian Eiloart wrote:
>
>> Twitter seems to think that users are smart enough to distinguish
>> between "unwanted" and "spam". They give you a button for each. It's an
>> important distinction that most people can make.
>
> Twitter isn't always right, and my intuition differs from yours on this
> one.  Fortunately it's something that could be resolved empirically.  I'd
> like to see such a study, because it wouldn't take very many users who
> *can't* properly make that distinction to render the two-button solution
> counterproductive.  I'd rather have one bit of meaningful data than two
> bits of muddled data.  -- Nathaniel
>

Well, then you have to make a judgment about what to do with the data. 
Application of fuzzy logic is essential here. You don't ban everyone who 
get's hit with a spam report, you wait til the reports hit a certain 
threshold, or you feed the message into your Bayesian analysis engine, or 
something.

What you can do, though, is stop delivering mail from the reported source 
to the recipient, perhaps after asking for confirmation. You need to be 
careful that this can be undone, though.

Yes, users make mistakes, and they have differing judgments about what is 
and is not spam, and those judgments may not be your judgments. But, that 
doesn't make the data useless, it just means that you have to think 
carefully about the application of the data in order to keep your false 
positive rates down.

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.

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