Re: [Asrg] Adding a spam button to MUAs

Ian Eiloart <iane@sussex.ac.uk> Wed, 09 December 2009 11:56 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 CCFD43A67F5 for <asrg@core3.amsl.com>; Wed, 9 Dec 2009 03:56:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.843
X-Spam-Level:
X-Spam-Status: No, score=-1.843 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_43=0.6, 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 615lA0z+IIL5 for <asrg@core3.amsl.com>; Wed, 9 Dec 2009 03:56:01 -0800 (PST)
Received: from lynndie.uscs.susx.ac.uk (lynndie.uscs.susx.ac.uk [139.184.14.87]) by core3.amsl.com (Postfix) with ESMTP id D15673A67CC for <asrg@irtf.org>; Wed, 9 Dec 2009 03:56:00 -0800 (PST)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.134.43]:64098) by lynndie.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KUDVU9-000JGZ-2O for asrg@irtf.org; Wed, 09 Dec 2009 11:56:33 +0000
Date: Wed, 09 Dec 2009 11:55:49 +0000
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <DC2A25A2C1E566508543DC5A@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <Pine.GSO.4.64.0912090126200.26971@nber6.nber.org>
References: <alpine.BSF.2.00.0912082138050.20682@simone.lan> <Pine.GSO.4.64.0912090126200.26971@nber6.nber.org>
Originator-Info: login-token=Mulberry:01yI/+ODHwbJ0J/FKaNLU7BHGrLgcfkiu1Pfo=; 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: Wed, 09 Dec 2009 11:56:01 -0000

--On 9 December 2009 01:31:36 -0500 Daniel Feenberg <feenberg@nber.org> 
wrote:

>
> Feedback is going to be controversial in this group.
>
> The first thing I would like to see was for email clients to
> automatically include headers for all mail forwarded to "postmaster" or
> "abuse". I have never gotten a complaint about incoming spam mail that
> included headers and it is generally difficult to instruct users, given
> the multiplicity of clients.
>
> Daniel Feenberg

That would make my life so much easier. Except in the quite common case 
when someone reports an email to an intermediary who doesn't use the 
postmaster address, or reports it to me at my personal address.

I quite like the idea of having the server add a "Report-Abuse" header, 
which would usually contain an email or web address. The client could make 
a POST report through a web form to a database, or forward the email with 
fill headers.  With a suitable AppleScript, it's feasible that we could 
already do this with Mail.app - given that we distribute customised OSX 
images.


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