RE: [Asrg] criteria for spam V2

Scott Nelson <scott@spamwolf.com> Fri, 06 June 2003 18:04 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05083 for <asrg-archive@odin.ietf.org>; Fri, 6 Jun 2003 14:04:03 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h56I3bU15481 for asrg-archive@odin.ietf.org; Fri, 6 Jun 2003 14:03:37 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56I3bB15478 for <asrg-web-archive@optimus.ietf.org>; Fri, 6 Jun 2003 14:03:37 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA05073; Fri, 6 Jun 2003 14:03:32 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OLWz-0004vR-00; Fri, 06 Jun 2003 14:01:37 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19OLWy-0004vO-00; Fri, 06 Jun 2003 14:01:36 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56HxnB15274; Fri, 6 Jun 2003 13:59:49 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h56Hu2B15002 for <asrg@optimus.ietf.org>; Fri, 6 Jun 2003 13:56:02 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04684 for <asrg@ietf.org>; Fri, 6 Jun 2003 13:55:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OLPd-0004o7-00 for asrg@ietf.org; Fri, 06 Jun 2003 13:54:01 -0400
Received: from adsl-66-120-64-133.dsl.snfc21.pacbell.net ([66.120.64.133] helo=magic1.org) by ietf-mx with smtp (Exim 4.12) id 19OLPb-0004o4-00 for asrg@ietf.org; Fri, 06 Jun 2003 13:53:59 -0400
Message-Id: <aT5vaIe86J8qbrGQG02@x>
To: asrg@ietf.org
From: Scott Nelson <scott@spamwolf.com>
Subject: RE: [Asrg] criteria for spam V2
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Fri, 06 Jun 2003 10:56:02 -0700

At 04:04 PM 6/5/03 -1000, Peter Kay wrote:
>> 
>> Ok, but building software is quite distinct from defining 
>> offenses. Let's first define the offense of "spam" and then 
>> decide how to approximately characterize it for our stupid 
>> computers.  Let's also be entirely clear when we are talking 
>> about spam and when we are talking about whatever our 
>> computers can detect or defend against.
>> 
>
>Isn't that what we're trying to do? Did I miss something? Aren't we
>trying to define what is spam and what is not? Or is the definition of
>an "offense" something else entirely.
>

Yes, you missed something.

The question is;
"Are we trying to decide what spam is supposed to mean,
or are we trying to redefine spam as 'the class of emails that we can
do something about'?".

I think Vernon's point was that we should clearly delineate the two.

For example, IMO Spam is excessive unwanted email, not unsolicited bulk.
But most use the term "unsolicited" because "unwanted" is such a 
fuzzy concept.  To my way of thinking, "unsolicited" is the just
the best test we can apply to determine if an email is in the class
of things we can do something about.  So we filter UBE because
it's much easier to understand what that should do, and how to do it.
"Spam" isn't "UBE" exactly, (though there's a lot of overlap),
and the concept is "don't try and claim UBE is the definition of spam,
but rather, say we're going after UBE which is close enough to what
most people think of as spam that it's good enough".


Bulk is also a fuzzy concept.  But just because there are
shades of gray, it doesn't mean we can't tell black from white.
Rather than defining the line, we could define the gray area.
I.e.  1000 or more is bulk.  1 or less is not.
Between 1 and 1000 may or may not be bulk, but the dividing
line requires human judgement and depends on circumstances,
so we're not going be any more precise than that.

In my experience, this sort of "fuzzy area" definition is
accepted immediately by spam fighters, though they question
if we can't be less generous and reduce the number to say 100,
or maybe even 20. 
But it's completely unacceptable to spammer fighters.
Just suggesting it can polarize the group and ultimately 
result in one camp storming off.

I fear nothing good will come of this thread.

Scott Nelson <scott@spamwolf.com>


_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg