Re: [Asrg] Summary of junk button discussion

Ian Eiloart <iane@sussex.ac.uk> Wed, 24 February 2010 14:18 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 9305828C171 for <asrg@core3.amsl.com>; Wed, 24 Feb 2010 06:18:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level:
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=-0.131, BAYES_00=-2.599, 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 pAw3AQUSAOwL for <asrg@core3.amsl.com>; Wed, 24 Feb 2010 06:18:13 -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 E806428C123 for <asrg@irtf.org>; Wed, 24 Feb 2010 06:18:12 -0800 (PST)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.135.133]:49735) by sivits.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KYCNUL-000K6F-PH; Wed, 24 Feb 2010 14:20:46 +0000
Date: Wed, 24 Feb 2010 14:20:07 +0000
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: Jose-Marcio.Martins@mines-paristech.fr
Message-ID: <F2DDD7EAE7FF60648960003D@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <4B85137A.4030508@mines-paristech.fr>
References: <20100214005320.52916.qmail@simone.iecc.com> <4B79BB27.20806@mines-paristech.fr> <9B8EB59EC57ED2AD33217BAE@lewes.staff.uscs.susx.ac.uk> <4B85137A.4030508@mines-paristech.fr>
Originator-Info: login-token=Mulberry:01xCSw4y2FHkgFkQRFMEo3mSNWKpzRPSdKOY8=; 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
Cc: Anti-Spam Research Group - IRTF <asrg@irtf.org>
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: Wed, 24 Feb 2010 14:18:14 -0000

--On 24 February 2010 12:54:34 +0100 Jose-Marcio Martins da Cruz 
<Jose-Marcio.Martins@mines-paristech.fr> wrote:

>
> I find it too restrictive to call this a "junk button" as this mechanism
> can be used more widely than just this way.

Ah, well that's a different question. This particular discussion is about 
how to get reports from the user to the administrator of the system. How 
the user triggers the report is an exercise for the MUA programmers, but 
we've been thinking that it's likely to be a button labelled "junk".

Of course, there could be more than one button, with different labels, or 
it could be simply one or more (virtual) mailboxes into which the user 
drags emails, or it could be that some smart process monitors the behaviour 
of the user (perhaps it would report emails that the user always deletes 
without reading).

Whatever triggers the reporting process, it's possible that the client may 
ask the user for more details about the report by asking questions like 
"this email came from a mailing list, do you wish to unsubscribe?", or 
"that's the third time you've reported email from this sender, do you want 
me to add the sender to a block list", or something.

But, these are all possibilities that become easier to implement if we can 
answer a few questions to standardise reports: like what messages can the 
report carry, and what's the mechanism that will carry the report.

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