[Asrg] Requirements for anti-spam systems

"Alan DeKok" <aland@freeradius.org> Sun, 04 May 2003 16:14 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 MAA02423 for <asrg-archive@odin.ietf.org>; Sun, 4 May 2003 12:14:16 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h44GLpo17392 for asrg-archive@odin.ietf.org; Sun, 4 May 2003 12:21:51 -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 h44GLp817389 for <asrg-web-archive@optimus.ietf.org>; Sun, 4 May 2003 12:21:51 -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 MAA02415; Sun, 4 May 2003 12:13:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CM9a-0001Ta-00; Sun, 04 May 2003 12:15:54 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CM9Z-0001TX-00; Sun, 04 May 2003 12:15:53 -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 h44GKD817354; Sun, 4 May 2003 12:20:13 -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 h44GJf817306 for <asrg@optimus.ietf.org>; Sun, 4 May 2003 12:19:41 -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 MAA02393 for <asrg@ietf.org>; Sun, 4 May 2003 12:11:36 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CM7U-0001TI-00 for asrg@ietf.org; Sun, 04 May 2003 12:13:44 -0400
Received: from giles.striker.ottawa.on.ca ([192.139.46.36] helo=mail.nitros9.org ident=root) by ietf-mx with esmtp (Exim 4.12) id 19CM7O-0001TE-00 for asrg@ietf.org; Sun, 04 May 2003 12:13:38 -0400
Received: from aland by mail.nitros9.org with local (Exim 3.34 #1) id 19CMIt-0006No-00 for asrg@ietf.org; Sun, 04 May 2003 12:25:31 -0400
From: Alan DeKok <aland@freeradius.org>
To: asrg@ietf.org
Message-Id: <E19CMIt-0006No-00@mail.nitros9.org>
Subject: [Asrg] Requirements for anti-spam systems
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: Sun, 04 May 2003 12:25:31 -0400

  Based on recent discussions, I would suggest an update to the requirements:

> 1.	must minimize unwanted messages to some acceptable level
> 2.	must not affect delivery(latency, integrity, cost, reliability) of
>  	wanted messages to a point that would effect the normal use of email

  2a) must not require that any message be accepted or rejected

  Much of the discussion around anti-spam systems indicates that most
people think that anti-spam systems are "either-or" type of systems.
i.e. As a result of applying the system to the message, it is either
accepted or rejected.  I would like to discourage such thinking.

  Anti-spam systems should be designed to give the local administrator
more information with which to make accept/reject decisions.  The
systems themselves hould not require that the adminstrator do anything
with the message, as the action taken after deciding a message is spam
is entirely up to local site policy.

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