Re: [ietf-smtp] Delivered-to and Return-path
John C Klensin <john-ietf@jck.com> Sat, 20 February 2021 04:27 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1DF53A0E07 for <ietf-smtp@ietfa.amsl.com>; Fri, 19 Feb 2021 20:27:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N9il1GBoWH_7 for <ietf-smtp@ietfa.amsl.com>; Fri, 19 Feb 2021 20:27:43 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74C633A0DEE for <ietf-smtp@ietf.org>; Fri, 19 Feb 2021 20:27:43 -0800 (PST)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1lDJrp-0003Rj-Ie; Fri, 19 Feb 2021 23:27:41 -0500
Date: Fri, 19 Feb 2021 23:27:35 -0500
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, ietf-smtp@ietf.org
Message-ID: <94F55A24F02653C27537ED12@PSB>
In-Reply-To: <4418b352-d25b-e831-93b7-74f188fd1d1b@dcrocker.net>
References: <3073462D484914E07B452E20@PSB> <4418b352-d25b-e831-93b7-74f188fd1d1b@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/kos_e4XHYH49qgLQm3ZDUDtTW6E>
Subject: Re: [ietf-smtp] Delivered-to and Return-path
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Feb 2021 04:27:46 -0000
--On Friday, February 19, 2021 19:36 -0800 Dave Crocker <dhc@dcrocker.net> wrote: > On 2/17/2021 9:55 PM, John C Klensin wrote: >> If I correctly understand the intended use of Delivered-to and >> the meaning of "added at the time of delivery", I believe that >> the examples in Section 4 are in error. The example does not >> show a Return-path and I'm having trouble figuring out a case >> in > You appear to be adding a requirement for the example to be > exhaustively complete. No. I am just suggesting that, given the obvious relationship between one as a forward pointer and the other as a backward pointer, both assigned at or after the time SMTP hands the message off to something other than another SMTP server (acting as such), an example that shows "Return-path:" as well as "Delivered-to:" and "Received:" would be a bit more clear and helpful. Please note "suggesting" in the previous sentence, which I do not believe to be a synonym for "a requirement". > That isn't claimed or intended in the current example text. It > merely seeks to show a sequence of Delivered-To fields, with a > bit more context. Then, as an alternative to the suggestion above, I would suggest a sentence somewhere that makes it explicit that the examples show only those header fields that are relevant to what you are illustrating. Dave, I am not the enemy. Given that the header field is already implemented and deployed, I favor having a spec go forward that provides implementation and interpretation guidance. I am just trying to constructively point out a place where the document might be made more clear for the benefit of those who do not already understand how the field is used and who are looking for implementation guidance. john
- [ietf-smtp] Delivered-to and Return-path John C Klensin
- Re: [ietf-smtp] Delivered-to and Return-path Sam Varshavchik
- Re: [ietf-smtp] Delivered-to and Return-path John Levine
- Re: [ietf-smtp] Delivered-to and Return-path Dave Crocker
- Re: [ietf-smtp] Delivered-to and Return-path John C Klensin
- Re: [ietf-smtp] Delivered-to and Return-path Dave Crocker
- Re: [ietf-smtp] this draft is dead, was Delivered… John Levine
- Re: [ietf-smtp] this draft is dead, was Delivered… Dave Crocker