Re: [Asrg] Adding a spam button to MUAs

Ian Eiloart <iane@sussex.ac.uk> Thu, 10 December 2009 11:49 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 624C928C0D0 for <asrg@core3.amsl.com>; Thu, 10 Dec 2009 03:49:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[AWL=-0.545, 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 redXHui4T5dD for <asrg@core3.amsl.com>; Thu, 10 Dec 2009 03:49: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 492CE3A6B30 for <asrg@irtf.org>; Thu, 10 Dec 2009 03:49:28 -0800 (PST)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.134.43]:63698) by sivits.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KUFQ6U-000IWD-N6 for asrg@irtf.org; Thu, 10 Dec 2009 11:49:42 +0000
Date: Thu, 10 Dec 2009 11:49:10 +0000
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <BD545201B175E30F09477FA2@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <4B20D8BF.2090804@bofhland.org>
References: <20091209202807.81190.qmail@simone.iecc.com> <20091209235730.7958324216@panix5.panix.com> <A1AF1DFB-40D4-4E7D-AA3C-3F865CBF14C6@blighty.com> <20091210023913.F322224218@panix5.panix.com> <D70BFF28-6C34-4F1F-AF7F-3D18F6A05EA2@blighty.com> <C92A29E1-3659-4EB9-888B-F0667381D5AE@blighty.com> <20091210053916.10F9124218@panix5.panix.com> <F6557152DC6E14E3757B7328@lewes.staff.uscs.susx.ac.uk> <4B20D8BF.2090804@bofhland.org>
Originator-Info: login-token=Mulberry:012pc1j0P4o/QbBInxRr1NDKgCQA9W6T29TwI=; 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, 10 Dec 2009 11:49:29 -0000

--On 10 December 2009 12:17:19 +0100 Skull <skull@bofhland.org> wrote:

> On 12/10/09 11:28 AM, Ian Eiloart wrote:
>
>> Forwarders who aren't taking care about what they forward *should* have
>> a damaged reputation.
>
> There's also people, out there, asking loudly for filter-free accounts
> and redirecting it on another (filtered) account, just to hit the spam
> button for every junk they receive from the forwarding.
>
> Or, similar story: company here in Italy with remote office in US. info@
> role account is an alias sending to both Italian people and to an AOL
> account used by the remote office.
> Italian users give opt-in in order to their suppliers in order to
> communications from their Italian suppliers. The US guy hits the spam
> button for each one he receives. I (the forwarding ISP) receive AOL's
> FBL for each... :-\
>
>
> Who's reputation is expected to be damaged? ;-)

The one who's forwarding unwanted email. Ideally, you're using SRS to 
forward from a specific address, so the reputation can be assigned to that 
address rather than the IP address. Then, when AOL stops accepting the 
email, the company will change their subscription. Perhaps you should 
forward the reports to info@...

If the messages contain DKIM sigs, then address based repuation is already 
feasible, but SRS and SPF would make it feasible otherwise.



It's for examples like this that you need a "Block" as well as a "Report 
for spam" button - like Twitter has.



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