Re: [Asrg] Adding a spam button to MUAs

Skull <skull@bofhland.org> Thu, 10 December 2009 08:02 UTC

Return-Path: <skull@bofhland.org>
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 4912C3A6822 for <asrg@core3.amsl.com>; Thu, 10 Dec 2009 00:02:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level:
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[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 TiSBPMAOckmI for <asrg@core3.amsl.com>; Thu, 10 Dec 2009 00:02:58 -0800 (PST)
Received: from mta-out2.spin.it (mta-out2.spin.it [IPv6:2a02:9a8:1::ff7f]) by core3.amsl.com (Postfix) with ESMTP id EF1113A62C1 for <asrg@irtf.org>; Thu, 10 Dec 2009 00:02:57 -0800 (PST)
Received: from mail.spin.it (mail.spin.it [IPv6:2a02:9a8:1::ff77]) by mta-out2.spin.it (Postfix) with ESMTP id 87CC25C0A1 for <asrg@irtf.org>; Thu, 10 Dec 2009 09:02:45 +0100 (CET)
Received: from mithrandir.bofhland.org (mithrandir.bofhland.org [IPv6:2a02:9a8:94::b]) by mail.spin.it (Postfix) with ESMTP id 52F003429C for <asrg@irtf.org>; Thu, 10 Dec 2009 09:02:45 +0100 (CET)
Received: from zarathustra.local (baggins.skullkrusher.net [147.123.72.2]) by mithrandir.bofhland.org (Postfix) with ESMTPSA id 37C5E6004E for <asrg@irtf.org>; Thu, 10 Dec 2009 09:02:45 +0100 (CET)
Message-ID: <4B20AB1E.10400@bofhland.org>
Date: Thu, 10 Dec 2009 09:02:38 +0100
From: Skull <skull@bofhland.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.1.5) Gecko/20091130 Thunderbird/3.0
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.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>
In-Reply-To: <20091210053916.10F9124218@panix5.panix.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Null-Tag: 3d834676b014fab602445f1af0025996
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 08:02:59 -0000

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...

-- 
Professional System & Network Sarcazzer
http://bofhskull.wordpress.com/