RE: [Asrg] CRI Header

"Eric D. Williams" <eric@infobro.com> Sun, 15 June 2003 05: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 BAA11766 for <asrg-archive@odin.ietf.org>; Sun, 15 Jun 2003 01:31:38 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5F5V9S21696 for asrg-archive@odin.ietf.org; Sun, 15 Jun 2003 01:31:09 -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 h5F5V9m21693 for <asrg-web-archive@optimus.ietf.org>; Sun, 15 Jun 2003 01:31:09 -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 BAA11761; Sun, 15 Jun 2003 01:31:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RQ4V-0001jU-00; Sun, 15 Jun 2003 01:28:55 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19RQ4V-0001jR-00; Sun, 15 Jun 2003 01:28:55 -0400
Received: from optimus.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5F3BOa14473; Sat, 14 Jun 2003 23:11:24 -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 h5F3Arm14458 for <asrg@optimus.ietf.org>; Sat, 14 Jun 2003 23:10:53 -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 XAA10251 for <asrg@ietf.org>; Sat, 14 Jun 2003 23:10:44 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RNsf-0001L9-00 for asrg@ietf.org; Sat, 14 Jun 2003 23:08:33 -0400
Received: from black.infobro.com ([63.71.25.39] helo=infobro.com) by ietf-mx with smtp (Exim 4.12) id 19RNsf-0001L5-00 for asrg@ietf.org; Sat, 14 Jun 2003 23:08:33 -0400
Received: from red (unverified [207.199.136.153]) by infobro.com (EMWAC SMTPRS 0.83) with SMTP id <B0002821203@infobro.com>; Sat, 14 Jun 2003 23:08:10 -0400
Received: by localhost with Microsoft MAPI; Sat, 14 Jun 2003 23:08:31 -0400
Message-ID: <01C332C9.DF290A90.eric@infobro.com>
From: "Eric D. Williams" <eric@infobro.com>
To: 'Yakov Shafranovich' <research@solidmatrix.com>, "asrg@ietf.org" <asrg@ietf.org>, Peter Kay <peter@titankey.com>
Subject: RE: [Asrg] CRI Header
Organization: Information Brokers, Inc.
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: Sat, 14 Jun 2003 23:08:10 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, June 09, 2003 2:39 PM, Yakov Shafranovich 
[SMTP:research@solidmatrix.com] wrote:
8<...>8
> HOWEVER, the same section states:
>
> "Whenever an SMTP transaction is used to send a DSN, the MAIL FROM command
> MUST use a NULL return address, i.e., "MAIL FROM:<>"."

A proper intepretation of that statement requires its full context.  The intent 
is to prevent message looping.  As such the CRI or other systems SHOULD ensure 
that specfied addresses do not violate that tenet.


   The envelope sender address of the DSN SHOULD be chosen to ensure
   that no delivery status reports will be issued in response to the DSN
   itself, and MUST be chosen so that DSNs will not generate mail loops.
   Whenever an SMTP transaction is used to send a DSN, the MAIL FROM
   command MUST use a NULL return address, i.e., "MAIL FROM:<>".


> That means that C/R systems such as yours MUST support the empty return
> path (<>).

No it does not, IMO, given the full context of the requirement.

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