Re: [Asrg] Adding a spam button to MUAs

Rich Kulawiec <rsk@gsp.org> Tue, 09 February 2010 12:35 UTC

Return-Path: <rsk@gsp.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 5A4FD3A7377 for <asrg@core3.amsl.com>; Tue, 9 Feb 2010 04:35:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.423
X-Spam-Level:
X-Spam-Status: No, score=-6.423 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 A+e+k9r25oFs for <asrg@core3.amsl.com>; Tue, 9 Feb 2010 04:35:41 -0800 (PST)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by core3.amsl.com (Postfix) with ESMTP id 64D393A71BD for <asrg@irtf.org>; Tue, 9 Feb 2010 04:35:41 -0800 (PST)
Received: from squonk.gsp.org (bltmd-207.114.17.180.dsl.charm.net [207.114.17.180]) by taos.firemountain.net (8.14.4/8.14.4) with ESMTP id o19CakF0009972 for <asrg@irtf.org>; Tue, 9 Feb 2010 07:36:47 -0500 (EST)
Received: from avatar.gsp.org (avatar.gsp.org [192.168.0.11]) by squonk.gsp.org (8.14.3/8.14.3) with ESMTP id o19CdRjM014612 for <asrg@irtf.org>; Tue, 9 Feb 2010 07:39:27 -0500 (EST)
Received: from avatar.gsp.org (localhost [127.0.0.1]) by avatar.gsp.org (8.14.3/8.14.3/Debian-9ubuntu1) with ESMTP id o19CaeqO010711 for <asrg@irtf.org>; Tue, 9 Feb 2010 07:36:40 -0500
Received: (from rsk@localhost) by avatar.gsp.org (8.14.3/8.14.3/Submit) id o19CadeW010710 for asrg@irtf.org; Tue, 9 Feb 2010 07:36:39 -0500
Date: Tue, 9 Feb 2010 07:36:39 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <20100209123639.GA10572@gsp.org>
References: <alpine.BSF.2.00.0912082138050.20682@simone.lan> <201002051204.37682.ar-asrg@acrconsulting.co.uk> <1265372705.19873.45.camel@tardis.isode.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1265372705.19873.45.camel@tardis.isode.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
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: Tue, 09 Feb 2010 12:35:42 -0000

On Fri, Feb 05, 2010 at 12:25:05PM +0000, David Wilson wrote:
> Some messages had List-unsubscribe headers. However, some were mailto:
> URLs, which is probably the best. Others were http: URLs. Most of these
> took you to a page where you had to enter information in order to
> unsubscribe.

They should all have email addresses of the form

	listname-request@example.com

which support this function per RFC 2142.  Other addresses, as well
as web-based mechanisms, are fine too, but this is something that
every mailing list should support.  (As an aside, it's quite remarkable
how many supposedly-professional mailing list operations fail to
pass this rudimentary test of their baseline expertise.)

> Related to this is the common folklore that you should not attempt to
> unsubscribe from a spam, as this could tell the spammer that the email
> address is 'live', thus exposing you to more spam. Is there actually any
> evidence that this is true? It certainly does not seem to be the case
> that spammers remove from their lists unresponsive email addresses.

Yes, there is conclusive evidence that this is true *of some spammers*.
Carefully-constructed experiments have repeatedly demonstrated that while
in some cases the result of such will be an unsubscribe, in other cases
it's led to (a) more spam from the same spammer, same domain (b) more
spam from the same spammer, different domain, (c) more spam from a different
spammer (d) various combinations and variations of (a)-(c).  This is
entirely sensible on their part of course: anyone so helpful as to
respond to spam is not only providing this information to the
enemy, but is signalling that they make a suitable victim.  And while
there are of course many clueless spammers out there who won't
recognize the opportunity thus presented, there are some who will.

But the more general principle that this falls under is that it's a
strategic error to provide spammers with any usable intelligence, as
they've long since displayed both the inclination and the ability to
aggregate it and process it.  And of course it's laughable to even
suggest to that they will do so in any way that benefits us.

---Rsk