Re: [ietf-smtp] what's not a trace field

John Levine <johnl@taugh.com> Wed, 17 February 2021 22:52 UTC

Return-Path: <johnl@iecc.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 611383A1E08 for <ietf-smtp@ietfa.amsl.com>; Wed, 17 Feb 2021 14:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=OKlC/bLi; dkim=pass (2048-bit key) header.d=taugh.com header.b=qud9lEEn
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 4eRbybY3J3ND for <ietf-smtp@ietfa.amsl.com>; Wed, 17 Feb 2021 14:52:24 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3404C3A1E07 for <ietf-smtp@ietf.org>; Wed, 17 Feb 2021 14:52:23 -0800 (PST)
Received: (qmail 26398 invoked from network); 17 Feb 2021 22:52:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=671c.602d9e25.k2102; bh=RWgNcJplfHI8KZiXPLwceUiYz2buOnQqfQYiVcwAsoQ=; b=OKlC/bLia7zQYcEXjcv7+V1nVOGBDgwyz7ufPc9zYCoOj1o4knwIJh+WmJjyqQTnZYk/NlmPaiAOmvA3+5C6ScTw66L+Sk3f7EO1RXkhdMlg36BlVfN3BsGZeF3OBNrMfxUHGhqFMSnRZRLRfNSQGQkg4GvoIiMMDURxiRJYflqTcDTPWmrELzU53wN0keZnKLghYyXiFrgIZ3lD3IuefOkWg+U8doWvGKALZWranO0Ol3EGaUu/QudxlCnQ2HFGIsfptYw2Ztk0NRiaO+hcVd72rxq+cZcurgIbH+0lrI94CkzLoI6yaix2D7kTPDHcgNiuOMiNrTVh+TzDKIKpFQ==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=671c.602d9e25.k2102; bh=RWgNcJplfHI8KZiXPLwceUiYz2buOnQqfQYiVcwAsoQ=; b=qud9lEEnhgRp1V9q3lgiUyRUyVicTvdcOtbsf2qjdYAgWOP8rHaYLSscx+Hy1TciZqh8YmCwub+uoSLd9n5f3IUUSg8KwFA9pDYUHMLuMfOv01sx4eMFkHB0R94JvQSNh/yD/2kEhxze+pIbFYpBQi30Krdzr0VlaKlQdIWYWd3BfmiA5Qr2dQgHGmOWnDFlellnjsy/TF3KiCGF22F5qWlNSrYKyaizEjo5nS0mlvNY+NQatd5ykWPrZKxVcF9fq2hs/yxrUNECAsKM1oynOEmDXZjwovMgbDiG0xdXvP8rvcvYlvzsemzMXMny8aoxsucxkivLSSgvl0Ec4O39Zw==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 17 Feb 2021 22:52:21 -0000
Received: by ary.qy (Postfix, from userid 501) id 562696E1F35B; Wed, 17 Feb 2021 17:52:19 -0500 (EST)
Date: Wed, 17 Feb 2021 17:52:19 -0500
Message-Id: <20210217225220.562696E1F35B@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: dcrocker@bbiw.net
In-Reply-To: <c4da6ead-5d52-3011-c65a-b13d7d540617@dcrocker.net>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/E7RY6jk7gqGerkIQwjCuYFPB2T8>
Subject: Re: [ietf-smtp] what's not a trace field
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: Wed, 17 Feb 2021 22:52:26 -0000

In article <c4da6ead-5d52-3011-c65a-b13d7d540617@dcrocker.net> you write:
w>OBE.  The draft I submitted text covers that concern.  Alexeys note 
>surfaced the ordering issue that I -- and based on the thread here, 
>everyone else -- had missed.
>
>See the diffs at:
>
>    https://www.ietf.org/rfcdiff?url2=draft-crocker-email-deliveredto-01

I'm still with Ned.  The new text fixes a few things but it mistakenly
took out the language that says Delivered-To is a trace header.

Oddly, it even cites RFC 5321 section 4.1.1.4 which describss what trace
headers are.

Old:

   This specification defines the "Delivered-To" header field, for
   annotating a delivery event and the individual address to which
   delivery has been effected.  A sequence of deliveries, such as when a
   message goes through multiple mailing lists, SHOULD be recorded with
   a series of Delivered-To: header fields.  As with some other
   information, each additional Delivered-To: header field MUST be
   placed at the current 'top' of the message -- as the first header
   field, in a fashion similar to some fields specified in [SMTP], such
   as in Section 4.1.1.4.  In addition, and as with other fields placed
   at the current top, the Delivered-To header field MUST NOT be
   reordered, with respect to other Delivered-to fields AND those other
   fields.

New:

   This specification defines the "Delivered-To" header field, for
   annotating a delivery event and the individual address to which
   delivery has been effected.  A sequence of deliveries, such as when a
   message goes through multiple mailing lists,May be recorded with
   a series of Delivered-To: header fields.  As with some other
   information, each additional Delivered-To: header field is a trace
   header field and so it MUST be placed at the current 'top' of the message -- as the first header
   field, in a fashion similar to other trace header fields specified in [SMTP] 
   in Section 4.1.1.4.  In addition, and as with other trace header fields
   the Delivered-To header field MUST NOT be
   reordered, with respect to other Delivered-to fields AND those other
   fields.




R's,
John