Re: [Asrg] Adding a spam button to MUAs

Ian Eiloart <iane@sussex.ac.uk> Fri, 05 February 2010 10:43 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 8C82D3A6A8F for <asrg@core3.amsl.com>; Fri, 5 Feb 2010 02:43:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level:
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=-0.011, 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 v6T7P8SxmO1d for <asrg@core3.amsl.com>; Fri, 5 Feb 2010 02:43:49 -0800 (PST)
Received: from karpinski.uscs.susx.ac.uk (karpinski.uscs.susx.ac.uk [139.184.14.85]) by core3.amsl.com (Postfix) with ESMTP id 93DCA3A6895 for <asrg@irtf.org>; Fri, 5 Feb 2010 02:43:49 -0800 (PST)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.134.43]:59134) by karpinski.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KXD76U-000228-FL for asrg@irtf.org; Fri, 05 Feb 2010 10:44:54 +0000
Date: Fri, 05 Feb 2010 10:44:38 +0000
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <23E7BA090191776EB5729804@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <20100204232046.53178.qmail@simone.iecc.com>
References: <20100204232046.53178.qmail@simone.iecc.com>
Originator-Info: login-token=Mulberry:01skj8iBupau3ztVDqHm4lvW/7GMAd4hVuJ7M=; 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: Fri, 05 Feb 2010 10:43:50 -0000

--On 4 February 2010 23:20:46 +0000 John Levine <johnl@taugh.com> wrote:

>  extract a reporting address
> from the message and send it an ARF report.

Which means that the email service provider has to decide what to do with 
messages that arrive carrying such a reporting address. I don't see what 
you can do except remove it - given that we're talking about junk email 
here.

Then it has to insert its own header into every message.

Then the client has to try to figure out whether the reporting address was 
inserted by the spammer, or by their email service provider.

Given that a "This is spam" button should only be reporting to the 
mailstore administrator, it's completely over the top to insert the address 
into every message. The address is a property of the mailstore, not the 
message.


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