Re: [Asrg] Adding a spam button to MUAs

Seth <sethb@panix.com> Thu, 10 December 2009 18:16 UTC

Return-Path: <sethb@panix.com>
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 028533A68A4 for <asrg@core3.amsl.com>; Thu, 10 Dec 2009 10:16:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.938
X-Spam-Level:
X-Spam-Status: No, score=-1.938 tagged_above=-999 required=5 tests=[AWL=0.505, 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 xpUqnLUYYOMs for <asrg@core3.amsl.com>; Thu, 10 Dec 2009 10:16:57 -0800 (PST)
Received: from mail2.panix.com (mail2.panix.com [166.84.1.73]) by core3.amsl.com (Postfix) with ESMTP id 019C63A6849 for <asrg@irtf.org>; Thu, 10 Dec 2009 10:16:57 -0800 (PST)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail2.panix.com (Postfix) with ESMTP id 614B138E55 for <asrg@irtf.org>; Thu, 10 Dec 2009 13:16:45 -0500 (EST)
Received: by panix5.panix.com (Postfix, from userid 756) id 41A9424218; Thu, 10 Dec 2009 13:16:45 -0500 (EST)
From: Seth <sethb@panix.com>
To: asrg@irtf.org
In-reply-to: <4B20AB1E.10400@bofhland.org> (message from Skull on Thu, 10 Dec 2009 09:02:38 +0100)
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> <4B20AB1E.10400@bofhland.org>
Message-Id: <20091210181645.41A9424218@panix5.panix.com>
Date: Thu, 10 Dec 2009 13:16:45 -0500 (EST)
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 18:16:58 -0000

Skull <skull@bofhland.org> wrote:
>On 12/10/09 6:39 AM, Seth wrote:

>> Problem: if the ISP gets the report and doesn't know that the
>> forwarder is legitimate, it will damage the reputation of the
>> forwarder.
>
> This is obvious, but it's up to the ISP preventing this. Once they have
> the message with full headers, he's expected to see what's inside it and
> which path it took to reach his network, not only look at the last hop
> and fire...
>
> Expecting to find a techincal solution to let *end users* correct their
> ISPs misbehaviour doesn't seem a good path to me...

Who else can do it?  Whatever headers a legitimate forwarder sends, a
spammer can fake exactly; the only difference is the connecting IP
address.

Seth