RE: [Asrg] TitanKey and "white lies"... (Faking SMTP hard errors "improves" C/R utility?)

Vernon Schryver <vjs@calcite.rhyolite.com> Fri, 30 May 2003 02:31 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 WAA05364 for <asrg-archive@odin.ietf.org>; Thu, 29 May 2003 22:31:14 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4U2UoP12740 for asrg-archive@odin.ietf.org; Thu, 29 May 2003 22:30:50 -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 h4U2UnB12737 for <asrg-web-archive@optimus.ietf.org>; Thu, 29 May 2003 22:30:49 -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 WAA05303; Thu, 29 May 2003 22:30:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LZdh-0006UW-00; Thu, 29 May 2003 22:29:05 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19LZdh-0006UT-00; Thu, 29 May 2003 22:29:05 -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 h4U2T3B12660; Thu, 29 May 2003 22:29:03 -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 h4U2SvB12630 for <asrg@optimus.ietf.org>; Thu, 29 May 2003 22:28: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 WAA04962 for <asrg@ietf.org>; Thu, 29 May 2003 22:28:51 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LZbt-0006P3-00 for asrg@ietf.org; Thu, 29 May 2003 22:27:13 -0400
Received: from calcite.rhyolite.com ([192.188.61.3]) by ietf-mx with esmtp (Exim 4.12) id 19LZbs-0006Oy-00 for asrg@ietf.org; Thu, 29 May 2003 22:27:12 -0400
Received: (from vjs@localhost) by calcite.rhyolite.com (8.12.9/8.12.9) id h4U2Spbw027834 for asrg@ietf.org env-from <vjs>; Thu, 29 May 2003 20:28:51 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305300228.h4U2Spbw027834@calcite.rhyolite.com>
To: asrg@ietf.org
Subject: RE: [Asrg] TitanKey and "white lies"... (Faking SMTP hard errors "improves" C/R utility?)
References: <01C3262E.F6068780.eric@infobro.com>
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: Thu, 29 May 2003 20:28:51 -0600

> From: "Eric D. Williams" <eric@infobro.com>

> ...
>IMHO the only relevant header information to determine 'sender' forgery is the 
> Return-Path: field reported by the receiving server.  In this case I am 
> referring to the receiver that is presented at the recipient border that 
> interacts with the 'spamming' system or (if headers are not munged and are 
> legitimately preserved as recommended RFC2822 and RFC822) by the terminating 
> end of the store-and-forward message transfer.

I'm having trouble matching those words with the middle of page 50
and continuing through page 51, section 4.4 of RFC 2821.  RFC 2821
seems to me to say that the Return-Path header is ought to be a copy
of the envelop Mail_From value.  For example, 'the delivery SMTP server
makes the "final delivery"' doesn't sound like "the receiver that is
presented at the recipient border that interacts with the 'spamming' system."

Notice the text at the top of page 51:

   any further (forwarding, gateway, or relay) systems MAY remove the
   return path and rebuild the MAIL command as needed to ensure that
   exactly one such line appears in a delivered message.

In other words, I not happy with such talk about the Return-Path header.
As far as I can see, what matters is the value that is supposed to be
copied from the envelope Mail_From command to the Return-Path line.


Vernon Schryver    vjs@rhyolite.com
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg