[Asrg] Re: SPF: Objection 5

Meng Weng Wong <mengwong@dumbo.pobox.com> Mon, 16 June 2003 19:09 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 PAA26253 for <asrg-archive@odin.ietf.org>; Mon, 16 Jun 2003 15:09:01 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5GJ8YY28121 for asrg-archive@odin.ietf.org; Mon, 16 Jun 2003 15:08:34 -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 h5GJ8Xm28118 for <asrg-web-archive@optimus.ietf.org>; Mon, 16 Jun 2003 15:08:33 -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 PAA26191; Mon, 16 Jun 2003 15:08:30 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RzJ2-0005LX-00; Mon, 16 Jun 2003 15:06:16 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19RzJ1-0005LU-00; Mon, 16 Jun 2003 15:06:15 -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 h5GGA1a15400; Mon, 16 Jun 2003 12:10:01 -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 h5GG9Nm15365 for <asrg@optimus.ietf.org>; Mon, 16 Jun 2003 12:09:23 -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 MAA19373 for <asrg@ietf.org>; Mon, 16 Jun 2003 12:09:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RwVf-0003fR-00 for asrg@ietf.org; Mon, 16 Jun 2003 12:07:07 -0400
Received: from dumbo.pobox.com ([208.210.125.24]) by ietf-mx with esmtp (Exim 4.12) id 19RwV3-0003fB-00 for asrg@ietf.org; Mon, 16 Jun 2003 12:06:29 -0400
Received: by dumbo.pobox.com (Postfix, from userid 505) id EF972DE44; Mon, 16 Jun 2003 12:08:43 -0400 (EDT)
From: Meng Weng Wong <mengwong@dumbo.pobox.com>
To: asrg@ietf.org
Message-ID: <20030616160843.GD25291@dumbo.pobox.com>
References: <20030614055858.GB12997@dumbo.pobox.com> <5.2.0.9.2.20030615114312.00ba1d90@std5.imagineis.com> <20030616160157.GC12997@dumbo.pobox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20030616160157.GC12997@dumbo.pobox.com>
User-Agent: Mutt/1.3.25i
Subject: [Asrg] Re: SPF: Objection 5
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: Mon, 16 Jun 2003 12:08:43 -0400

On Mon, Jun 16, 2003 at 12:01:57PM -0400, Meng Weng Wong wrote:
| 
| ...some objections to SPF have come from people who
| 
| 5) misunderstand some technical detail of SPF, and take up arms
|    against a chimera;

(5): SPF doesn't say anything about RFC822 header addresses.  It only
has to do with the RFC821 envelope sender address.  You may still
forge whatever headers you wish.  Forwarding systems and kiosks can
easily achieve SPF compliance by using a sender rewriting scheme
(SRS); I am developing a simple I-D to describe one possible SRS.

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