Re: [Asrg] Adding a spam button to MUAs

Ian Eiloart <iane@sussex.ac.uk> Thu, 10 December 2009 10:29 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 46D303A68F1 for <asrg@core3.amsl.com>; Thu, 10 Dec 2009 02:29:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[AWL=0.333, 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 lCnLDy-KT000 for <asrg@core3.amsl.com>; Thu, 10 Dec 2009 02:29:09 -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 585CA3A686D for <asrg@irtf.org>; Thu, 10 Dec 2009 02:29:09 -0800 (PST)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.134.43]:58845) by sivits.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KUFMH5-000G3F-FA for asrg@irtf.org; Thu, 10 Dec 2009 10:29:29 +0000
Date: Thu, 10 Dec 2009 10:28:55 +0000
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <F6557152DC6E14E3757B7328@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <20091210053916.10F9124218@panix5.panix.com>
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>
Originator-Info: login-token=Mulberry:01gfosu+pbmiDCZ4Ad7SD0b58u53JNFeQg9mU=; 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 10:29:10 -0000

--On 10 December 2009 00:39:16 -0500 Seth <sethb@panix.com> wrote:

> Steve Atkins <steve@blighty.com> wrote:
>
>> If the mail delivery path is "spammer -> forwarder -> isp ->
>> recipient" then the only useful places to report it are the ISP, the
>> forwarder and (potentially) the spammer. If, instead, it's
>> "spammer-pretending-to-be-a-forwarder -> isp -> recipient" then the
>> only useful place to send it is the ISP, but sending it to the
>> spammer as well has no real cost.
>
> Problem: if the ISP gets the report and doesn't know that the
> forwarder is legitimate, it will damage the reputation of the
> forwarder.

Forwarders who aren't taking care about what they forward *should* have a 
damaged reputation.

>> I might have missed a suggestion to not send it to the ISP, only to
>> the apparent forwarder, when there was something that looked like a
>> forwarder - if so, don't do that. :)
>
> Not "looked like" but "was verified by the user, by the server sending
> a magic message to the user-supplied 'this is my other address' and
> seeing it come back from the forwarder".
>
> Seth
> _______________________________________________
> Asrg mailing list
> Asrg@irtf.org
> http://www.irtf.org/mailman/listinfo/asrg



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