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

Seth <sethb@panix.com> Wed, 01 July 2009 04:53 UTC

Return-Path: <sethb@panix.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 841C63A6ABF for <asrg@core3.amsl.com>; Tue, 30 Jun 2009 21:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level:
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[AWL=-0.090, BAYES_00=-2.599, 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 EIPm0txTHEJU for <asrg@core3.amsl.com>; Tue, 30 Jun 2009 21:53:15 -0700 (PDT)
Received: from mail2.panix.com (mail2.panix.com [166.84.1.73]) by core3.amsl.com (Postfix) with ESMTP id D4FA43A6767 for <asrg@irtf.org>; Tue, 30 Jun 2009 21:53:15 -0700 (PDT)
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5]) by mail2.panix.com (Postfix) with ESMTP id E5A2638E47 for <asrg@irtf.org>; Wed, 1 Jul 2009 00:53:36 -0400 (EDT)
Received: by panix5.panix.com (Postfix, from userid 756) id DAA7624307; Wed, 1 Jul 2009 00:53:36 -0400 (EDT)
From: Seth <sethb@panix.com>
To: asrg@irtf.org
In-reply-to: <CFF41897-E082-47C1-938D-4D747CC1FB59@blighty.com> (message from Steve Atkins on 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> <CFF41897-E082-47C1-938D-4D747CC1FB59@blighty.com>
Message-Id: <20090701045336.DAA7624307@panix5.panix.com>
Date: Wed, 01 Jul 2009 00:53:36 -0400
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: Wed, 01 Jul 2009 04:53:16 -0000

It seems clear that different definitions are useful for different
things; in particular, different methods are better or worse depending
on the definition used.

For instance, it seems apparent that using "This Is Spam" buttons hit
by users to train filters will do best under a definition like "email
users say is spam".

My suggestion of filtering confirmations through the ISP (so the site
clicked on is theirs rather than the sender's, and they record the
click and notify the sender) works really well using an "unsolicited"
definition, and less well using a "user complaints" definition (since
it's well known that users sometimes complain about mail they
solicited).

So, it can be worthwhile to specify which definition you're using when
you suggest a method to optimize under that definition.  But that's
pure practicality, it has nothing to do with "right" or "wrong".
There's no such thing with definitions.  Rather, the purpose of a
definition is to enable discussion about something without having to
describe it in full each time it's mentioned.

Seth