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

Ian Eiloart <iane@sussex.ac.uk> Mon, 29 June 2009 08:41 UTC

Return-Path: <iane@sussex.ac.uk>
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 0F02D3A6969 for <asrg@core3.amsl.com>; Mon, 29 Jun 2009 01:41:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.06
X-Spam-Level:
X-Spam-Status: No, score=-3.06 tagged_above=-999 required=5 tests=[AWL=0.740, BAYES_00=-2.599, GB_I_LETTER=-2, 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 4vkUXkmo0+ud for <asrg@core3.amsl.com>; Mon, 29 Jun 2009 01:41:23 -0700 (PDT)
Received: from karpinski.uscs.susx.ac.uk (karpinski.uscs.susx.ac.uk [139.184.14.85]) by core3.amsl.com (Postfix) with ESMTP id 126743A68C4 for <asrg@irtf.org>; Mon, 29 Jun 2009 01:41:22 -0700 (PDT)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.134.43]:65267) by karpinski.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KLZS7C-000JHS-E9 for asrg@irtf.org; Mon, 29 Jun 2009 09:42:48 +0100
Date: Mon, 29 Jun 2009 09:41:42 +0100
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <5D548C8C6AB23557A0CCEF4D@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <4A4612A0.8070208@tana.it>
References: <4A43B696.2000106@cybernothing.org> <4A449A7C.6070106@tana.it> <4A452A12.2070302@cybernothing.org> <4A4612A0.8070208@tana.it>
Originator-Info: login-token=Mulberry:01hI42u+3vpCDF+4od8LT3A6ku6gZXFee0+fk=; token_authority=support@its.sussex.ac.uk
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Sussex: true
X-Sussex-transport: remote_smtp
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: Mon, 29 Jun 2009 08:41:24 -0000

--On 27 June 2009 14:37:52 +0200 Alessandro Vesely <vesely@tana.it> wrote:

> J.D. Falk 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.
>
> Finishing a document, by itself, is not a progress in the anti-spam
> endeavor, unless it contains useful knowledge for countering spam. I
> suspect that if we are not even able to agree on a definition of spam,
> there will never be much efficient anti-spam research by our group. And
> if people were to judge such research by the spam levels out there,
> they'd conclude it's all hot air.
>
> Could we start again, please?

The mistake below is to assume that "spam" is a single category that can be 
tidily defined. It can't.

The best one could do is to try to enumerate some types of spam. I'd 
suggest two, that look very different from each other: (a) submission of 
large quantities of electronic messages to an electronic messaging service 
with the deliberate aim of reducing the usability of that service, and (b) 
transmission of unsolicited communications by means of electronic mail for 
direct marketing purposes.

These are very different - the content is irrelevant in the first, but 
highly relevant in the second. The threat to the system is the motivation 
of the first, but would be harmful to the sender in the second. A recipient 
might welcome the second, but is unlikely to welcome the first.

One might wish to add other types of spam (phishing, viruses, chain 
letters...) but it's unlikely that even the longest list constructed today 
will cover all future types of spam.


> Let me try the following variation on UBE, in order to see if we can
> classify the objections against adopting it as a working definition.
>
>   *Spam* is a message or a class of messages composed automatically,
>   possibly using templates and databases of names or words, using a
>   list of destination mailbox addresses, and failing to meet both the
>   following conditions:
>   * There is a record or evidence whatsoever, even implied, that the
>     recipient has registered, subscribed, or otherwise solicited the
>     message; and
>   * it is obvious from the message content, including the headers,
>     who is in charge of controlling the processing, and how the
>     recipients can amend or delete their addresses from the list (as
>     well as any other part of their personally identifiable data from
>     any database used to compose the message), where "obvious" means
>     the relevant entity is indicated, exists, is normally reachable by
>     the recipient, and is effectual to the purpose it is referred for.
> _______________________________________________
> Asrg mailing list
> Asrg@irtf.org
> http://www.irtf.org/mailman/listinfo/asrg



-- 
Ian Eiloart
IT Services, University of Sussex
01273-873148 x3148
For new support requests, see http://www.sussex.ac.uk/its/help/