Re: [Asrg] draft-irtf-asrg-criteria (was Re: request for review for a non FUSSP proposal)

Steve Atkins <steve@blighty.com> Tue, 30 June 2009 23:04 UTC

Return-Path: <steve@blighty.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 1E3583A6B2E for <asrg@core3.amsl.com>; Tue, 30 Jun 2009 16:04:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level:
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_RAND_LETTRS4=0.799]
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 f3-NVvvvfCiV for <asrg@core3.amsl.com>; Tue, 30 Jun 2009 16:04:32 -0700 (PDT)
Received: from m.wordtothewise.com (fruitbat.wordtothewise.com [208.187.80.135]) by core3.amsl.com (Postfix) with ESMTP id 4B8D03A6B09 for <asrg@irtf.org>; Tue, 30 Jun 2009 16:04:32 -0700 (PDT)
Received: from [192.168.80.34] (184.wordtothewise.com [208.187.80.184]) by m.wordtothewise.com (Postfix) with ESMTP id 686DC806FE for <asrg@irtf.org>; Tue, 30 Jun 2009 16:04:39 -0700 (PDT)
Message-Id: <CFF41897-E082-47C1-938D-4D747CC1FB59@blighty.com>
From: Steve Atkins <steve@blighty.com>
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
In-Reply-To: <5ec229170906300004m687af225vf5a3f621646f5fcb@mail.gmail.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 30 Jun 2009 16:04:51 -0700
References: <4A43B696.2000106@cybernothing.org> <4A449A7C.6070106@tana.it> <4A452A12.2070302@cybernothing.org> <5ec229170906300004m687af225vf5a3f621646f5fcb@mail.gmail.com>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [Asrg] draft-irtf-asrg-criteria (was Re: request for review for a non FUSSP proposal)
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, 30 Jun 2009 23:04:33 -0000

On Jun 30, 2009, at 12:04 AM, Danny Angus wrote:

> On Fri, Jun 26, 2009 at 9:05 PM, J.D. Falk<jdfalk-lists@cybernothing.org 
> > wrote:
>> Alessandro Vesely wrote:
>>
>>> However, I think an it could, and should, go beyond that. For
>>> example, why is it not in the scope of that document "to attempt to
>>> distinguish or justify any more detailed definition of [the term  
>>> spam]"?
>>
>> Because attempting to define "spam" is the very best way to ensure  
>> that a
>> document is never finished.
>
>
> In fact trying to define spam would ensure it never got started!
>
> Actually I would have liked to have included *some* definition, but
> because members of this group hold pretty entrenched opinions covering
> most possible definitions I felt that on the one hand it would be
> impossible and on the other hand it would be unecessary.
>
> I believe that it is unnecessary for two reasons, the first being that
> this group cannot agree a definition, yet operates reasonably
> successfully, and secondly there can be an empirical test for a
> solution, even if there is no agreed definition of spam itself.

One issue is that there are a number of definitions of spam that
are useful in different contexts. The definition that's useful for
operational handling at an abuse desk is different to that for
operational handling of inbound mail filters, different again to
that useful for someone developing content based filters, different
again for someone drafting legislation and very different again
for someone litigating.

All of these definitions are fairly well defined and extremely useful
in the context in which they're used. And they'll generally agree
on the categorization of the vast majority of emails, but there are
emails where they'll disagree. This isn't a problem.

The problem arises when someone, anyone, claims that there is
One True Definition of spam. The fact that that's blatantly false
isn't the problem. That it causes hordes of people to come out of
the woodwork to argue for their One True Definition of spam, causing
yet another rerun of the Thread That Would Not Die is the problem.

(A problem that's usually best solved by killfiling anyone participating
in that sort of thread).

Cheers,
   Steve