[Emailcore] Ticket #7: Trace header field related text in rfc5321bis

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 23 July 2021 14:30 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: emailcore@ietfa.amsl.com
Delivered-To: emailcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3813A0B6C for <emailcore@ietfa.amsl.com>; Fri, 23 Jul 2021 07:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 (1024-bit key) header.d=isode.com
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 j3K8xnyb_CIX for <emailcore@ietfa.amsl.com>; Fri, 23 Jul 2021 07:29:57 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id B0FF33A0B37 for <emailcore@ietf.org>; Fri, 23 Jul 2021 07:29:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1627050596; d=isode.com; s=june2016; i=@isode.com; bh=tpkx+eHOloxdfCS66HFZg/ypbONjKCsIhuM14TKe3i8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=LqEUebBV1PO5fi00k4K4fSG7hDPilWC7x5lGMrea71su4/xR7inZqnNQwBwtI2fBolXYwG T6S5ydUIcNSDdjUOcq7V6cm1yDXgyxyEw+Vf6/+fOPaM2Z+NmcwUR8j7J0FXGBs5treSJo P0Gx4WWYGlpUuH4wXxZByuVeiHHRkfc=;
Received: from [192.168.1.222] (host5-81-100-7.range5-81.btcentralplus.com [5.81.100.7]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <YPrSZAAX7iyu@waldorf.isode.com>; Fri, 23 Jul 2021 15:29:56 +0100
To: emailcore@ietf.org
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <39fea9e5-907e-2dfd-ba88-5e0e21e9685f@isode.com>
Date: Fri, 23 Jul 2021 15:29:49 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/mjqqTjF6Rlc6suNNaz6nycEsY-Y>
Subject: [Emailcore] Ticket #7: Trace header field related text in rfc5321bis
X-BeenThere: emailcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EMAILCORE proposed working group list <emailcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emailcore>, <mailto:emailcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emailcore/>
List-Post: <mailto:emailcore@ietf.org>
List-Help: <mailto:emailcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emailcore>, <mailto:emailcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jul 2021 14:30:08 -0000

Hi all,

I scanned the draft and hopefully captured all cases where trace header 
fields/Received are mentioned. Below is a strawman of what might be a 
good idea to update:

Add a new section that introduces Trace header fields. Possibly change 
4.4 to be that section and move definition of the Received header field 
into a subsection of 4.4 (e.g. 4.4.1). I found the following text in RFC 
822, which seems like a good definition:

      Trace information is used to provide an audit trail of  mes-
      sage  handling.   In  addition,  it indicates a route back to the
      sender of the message.

2.3.10.  Originator, Delivery, Relay, and Gateway Systems

    A "relay" SMTP
    system (usually referred to just as a "relay") receives mail from an
    SMTP client and transmits it, without modification to the message
    data other than adding trace information, to another SMTP server for
    further relaying or for delivery.

Add a reference to the new 4.4. after "trace information".

3.6.3.  Message Submission Servers as Relays

    As discussed in Section 6.4, a relay SMTP has no need to inspect or
    act upon the header section or body of the message data and MUST NOT
    do so except to add its own "Received:" header field (Section 4.4)

Add "and possibly other trace header fields" at the end of the above line.

    and, optionally, to attempt to detect looping in the mail system (see
    Section 6.3).  Of course, this prohibition also applies to any
    modifications of these header fields or text (see also Section 7.9).


7.6.  Information Disclosure in Trace Fields

    In some circumstances, such as when mail originates from within a LAN
    whose hosts are not directly on the public Internet, trace
    ("Received") header fields produced in conformance with this

Change '("Received")' to '(e.g. "Received")'

    specification may disclose host names and similar information that
    would not normally be available.


Thoughts?

Best Regards,

Alexey