IETF Logo Mail Archive

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

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 15 February 2021 10:54 UTC

Return-Path: <alexey.melnikov@isode.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 949A03A113B for <ietf-smtp@ietfa.amsl.com>; Mon, 15 Feb 2021 02:54:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level:
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-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 (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 WxRgkd4D40bM for <ietf-smtp@ietfa.amsl.com>; Mon, 15 Feb 2021 02:54:11 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 8505F3A113A for <ietf-smtp@ietf.org>; Mon, 15 Feb 2021 02:54:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1613386450; d=isode.com; s=june2016; i=@isode.com; bh=jWpNIo5SJt0btFGlLAwW2xVTKwnupfC0e0nNQFc20nw=; 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=oy2yNPEIxdNncE6LqnFmvTSA5CBMSP21b2qnUG4/nq7G0zdu33M1USPk3BJNJjXkAf/7e4 w4Ud5pY9L/ZEtj6WmPUu7DfQRNBgRNU5W/YiduL80Q3C8WuqsJqY/t+lNPLOdXOp6LciHW cToVRQjriOegphj+34zZkqLNAxcNaZc=;
Received: from [192.168.1.222] (host5-81-100-89.range5-81.btcentralplus.com [5.81.100.89]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <YCpS0QAuQY0M@waldorf.isode.com>; Mon, 15 Feb 2021 10:54:10 +0000
To: "John R. Levine" <johnl@iecc.com>, Dave Crocker <dcrocker@bbiw.net>
Cc: ietf-smtp@ietf.org
References: <20210204234602.6DB4D6D63596@ary.local> <6D7EBCFD-C4C1-4623-BB95-4F6114A93C3B@episteme.net> <a6e19810-4fe4-3b2a-8c79-0f9397b77c9f@dcrocker.net> <2F7AAE37-2D9D-4CFD-9FC1-8E174BA13693@episteme.net> <b1a67354-2edb-8ffd-af6b-aa776219d9d4@dcrocker.net> <54BC4A2C-9B44-4369-AB16-85716CD404E3@episteme.net> <37c5f99b-2369-44ea-4a05-a3f554816691@dcrocker.net> <17961157-7FA3-462F-BA36-AE515C8A9442@episteme.net> <7491fa02-aafd-524c-db7a-b3deab8161b1@dcrocker.net> <d4ef590-4026-86d8-36c7-dfd0d77df687@iecc.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <7f52c750-de14-0d82-b563-e8a23ffef3b8@isode.com>
Date: Mon, 15 Feb 2021 10:54:00 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
In-Reply-To: <d4ef590-4026-86d8-36c7-dfd0d77df687@iecc.com>
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/ietf-smtp/mDdteXR4-rS_85l4N-bApgOYOp4>
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: Mon, 15 Feb 2021 10:54:13 -0000

On 15/02/2021 01:30, John R. Levine wrote:

> On Sun, 14 Feb 2021, Dave Crocker wrote:
>> I think that calling Delivered-To: a 'trace' header field ties it to 
>> this model in ways that aren't appropriate. And it isn't the above 
>> model that should change.
>
> I took a look at 5322, in which section 3.6.6 says that Resent fields 
> are not trace headers, even though they are added in exactly the same 
> way that trace fields are.  Presumably there was a historical reason 
> for that.
>
> I see that 8601 says that A-R says that it is a trace field so I don't 
> see why Delivered-To is not also a trace field.  It's just as trace-y.
I agree.
> FYI, Delivered-To is not always added by an MDA.  Sometimes, as in the 
> example I sent a few messages back, it's added by the MTA when it 
> rewrites an address internally.

Best Regards,

Alexey

v2.23.0 | Report a Bug | By Email