IETF Logo Mail Archive

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

Dave Crocker <dhc@dcrocker.net> Thu, 18 February 2021 16:12 UTC

Return-Path: <dhc@dcrocker.net>
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 DA5AF3A13CB for <ietf-smtp@ietfa.amsl.com>; Thu, 18 Feb 2021 08:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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=dcrocker.net
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 FyqiA1hg4pgp for <ietf-smtp@ietfa.amsl.com>; Thu, 18 Feb 2021 08:12:13 -0800 (PST)
Received: from antelope.elm.relay.mailchannels.net (antelope.elm.relay.mailchannels.net [23.83.212.4]) (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 5D25A3A1C37 for <ietf-smtp@ietf.org>; Thu, 18 Feb 2021 08:09:23 -0800 (PST)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 2C0803243A3; Thu, 18 Feb 2021 16:09:23 +0000 (UTC)
Received: from nl-srv-smtpout4.hostinger.io (100-96-16-16.trex.outbound.svc.cluster.local [100.96.16.16]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id D71AD3241E6; Thu, 18 Feb 2021 16:09:21 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout4.hostinger.io ([UNAVAILABLE]. [145.14.159.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.96.16.16 (trex/6.1.1); Thu, 18 Feb 2021 16:09:22 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Descriptive-Little: 479092f961261432_1613664562885_106266522
X-MC-Loop-Signature: 1613664562885:4108393009
X-MC-Ingress-Time: 1613664562885
Received: from [192.168.0.109] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout4.hostinger.io (smtp.hostinger.com) with ESMTPSA id 7A9FB31A9861; Thu, 18 Feb 2021 16:09:18 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1613664560; bh=tdIztlnH5oZjLdbT4uL+ctmVcSxLPzcouCvapgnxCn0=; h=Reply-To:Subject:To:References:From:Date:In-Reply-To; b=Fd/N8Dcu8XM8PcMsMz6eTEvxehNus8jVTDQvLFfUIIa/dz/wtcYYk6OpU5qU8qLvA 03ClSUIMj9MvnaPP5AjsyVnr8ThaOyVBXSTF07gStXAfasqGc1GRKUm2daQUesryLs YV/onEU4syHDwAQkF2mlgdxs1ji9jLtr4CdvWBfY2r+bo5KPRc283twHSeIzAmQGqC fyx1deCjeELdYW51OzlkSMQ7vFLG75R3Pb/xN6j7pUqZEdA96csh997E6VElMbC3JF F+6I1tzNNUxijHLYB3mxBqfvdevdKbfPI5PssxMVw7ZKoblU5a7js2YfzdFGQXJW/5 GACelVL/WbzRQ==
Reply-To: dcrocker@bbiw.net
To: Alessandro Vesely <vesely@tana.it>, ietf-smtp@ietf.org
References: <20210217225220.562696E1F35B@ary.qy> <5f987531-4d58-9dc0-54c0-845e60ac2ebe@dcrocker.net> <612894d1-89a9-eb77-20dc-1bdebe0a32e@taugh.com> <af165aa5-1858-f466-71e6-b9e8f1535e74@dcrocker.net> <6cc4f874-7e00-ed48-b0c6-c2941a3b14e4@tana.it>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <61dc841b-c96f-9678-0c80-c5bac87b6792@dcrocker.net>
Date: Thu, 18 Feb 2021 08:09:16 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1
MIME-Version: 1.0
In-Reply-To: <6cc4f874-7e00-ed48-b0c6-c2941a3b14e4@tana.it>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/DY0JuSJu1kUlorzf1iw4heiIfH8>
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: Thu, 18 Feb 2021 16:12:15 -0000

On 2/18/2021 7:58 AM, Alessandro Vesely wrote:
> 
> OLD:
>     in a fashion similar to some fields specified in [SMTP],
>     such as in Section 4.1.1.4.
> 
> NEW:
>     in a fashion similar to the trace fields specified in
>     Section 4.1.1.4 of [SMTP].
> 
> 
> That doesn't imply that Delivered-To: /is/ a trace field.  Just that it 
> should be treated in the same way.  (The trace attribute is not 
> registered at IANA.)


My goodness.  How diplomatic.  I like it.  done!



d/

ps. Notwithstanding making the change to the draft, it's important to 
realize that RFC 5321 is quite explicit that Received: is THE trace 
header field.  The only language in 5321 that says otherwise is 
commentary, not definition.  Here's the clearest documentation of this fact:

    4.4.  Trace Information

    When an SMTP server receives a message for delivery or further
    processing, it MUST insert trace ("time stamp" or "Received")
    information at the beginning of the message content, as discussed in
    Section 4.1.1.4.


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email