Re: [Asrg] Requirements for anti-spam systems
"Jon Kyme" <jrk@merseymail.com> Sun, 04 May 2003 20:28 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 QAA06160 for <asrg-archive@odin.ietf.org>; Sun, 4 May 2003 16:28:24 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h44KYcJ29702 for asrg-archive@odin.ietf.org; Sun, 4 May 2003 16:34:38 -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 h44KYc829699 for <asrg-web-archive@optimus.ietf.org>; Sun, 4 May 2003 16:34:38 -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 QAA06149; Sun, 4 May 2003 16:26:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CQ67-0002Df-00; Sun, 04 May 2003 16:28:35 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CQ67-0002Da-00; Sun, 04 May 2003 16:28:35 -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 h44KWM829624; Sun, 4 May 2003 16:32:22 -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 h44KVv829605 for <asrg@optimus.ietf.org>; Sun, 4 May 2003 16:31:57 -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 QAA06100 for <asrg@ietf.org>; Sun, 4 May 2003 16:23:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CQ3S-0002Cy-00 for asrg@ietf.org; Sun, 04 May 2003 16:25:50 -0400
Received: from argon.connect.org.uk ([193.110.243.33]) by ietf-mx with esmtp (Exim 4.12) id 19CQ3M-0002Co-00 for asrg@ietf.org; Sun, 04 May 2003 16:25:44 -0400
Received: from mmail by argon.connect.org.uk with local (connectmail/exim) id 19CQ2f-0006Te-00; Sun, 04 May 2003 21:25:01 +0100
In-Reply-To: <E19CMIt-0006No-00@mail.nitros9.org>
Subject: Re: [Asrg] Requirements for anti-spam systems
To: Alan DeKok <aland@freeradius.org>
From: Jon Kyme <jrk@merseymail.com>
Cc: ASRG <asrg@ietf.org>
X-Mailer: [ConnectMail 3.4.21]
X-connectmail-Originating-IP: 193.195.0.102
Message-Id: <E19CQ2f-0006Te-00@argon.connect.org.uk>
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 21:25:01 +0100
> 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. At some point a message MUST be either accepted (in some sense) or rejected (even if silently). Unless you're thinking about schrodingers email that is. -- _______________________________________________ Asrg mailing list Asrg@ietf.org https://www1.ietf.org/mailman/listinfo/asrg