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

Dave Crocker <dhc@dcrocker.net> Tue, 16 February 2021 00:15 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 2B1733A08D6 for <ietf-smtp@ietfa.amsl.com>; Mon, 15 Feb 2021 16:15:17 -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 Jcjy-Qhf32ub for <ietf-smtp@ietfa.amsl.com>; Mon, 15 Feb 2021 16:15:15 -0800 (PST)
Received: from dormouse.elm.relay.mailchannels.net (dormouse.elm.relay.mailchannels.net [23.83.212.50]) (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 9D90C3A08C5 for <ietf-smtp@ietf.org>; Mon, 15 Feb 2021 16:15:15 -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 4B9FE10257C; Tue, 16 Feb 2021 00:15:14 +0000 (UTC)
Received: from nl-srv-smtpout2.hostinger.io (100-105-161-66.trex.outbound.svc.cluster.local [100.105.161.66]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 74477103839; Tue, 16 Feb 2021 00:15:13 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout2.hostinger.io ([UNAVAILABLE]. [145.14.159.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.105.161.66 (trex/6.1.1); Tue, 16 Feb 2021 00:15:14 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Daffy-Macabre: 221ce5f220ead6b0_1613434514141_2482542811
X-MC-Loop-Signature: 1613434514141:3243198096
X-MC-Ingress-Time: 1613434514140
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-smtpout2.hostinger.io (smtp.hostinger.com) with ESMTPSA id 4558930B59C5; Tue, 16 Feb 2021 00:15:10 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1613434511; bh=rlYBX5okODEYCOIbRsIUcu0yqUXWF9/itUBbg8d7oF4=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To; b=HKCvzdCRAjIC58iuw5d5noZ9s7pt9mCSvwTaIL/aXPypdBGAqpLqc1Qiv3Ckbj1sx qOpUM9dogL8iwGWQysz7l9FLasohFVgV6rKIjlJJ5PiAfL4fwgtdp6UV+pNOzwuHYA 8FXQRrO0S2/KvuXjHZ/DQWVJf+QaCeFdyeKd6iO4Z4qXAM0vGTOIJYYmJmA/WfmkPV iky1eeQcSZqUj250NyoilhtK9Nd99OtZPNqrjMRLmAXCZnUUSnKh+vq/FU+Huv2J49 eaZhxJnHLuRR4VtPEh1UM+lSYbcr4OhXyGJ/X6uEWlLpAd7XOpol/v1mjDxs1XqwIK EYHLMhshAjeRQ==
Reply-To: dcrocker@bbiw.net
To: "John R. Levine" <johnl@iecc.com>
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: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <00d88a2e-d743-8d53-55e8-d0aa1ca7628c@dcrocker.net>
Date: Mon, 15 Feb 2021 16:15:08 -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: <d4ef590-4026-86d8-36c7-dfd0d77df687@iecc.com>
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/-ybkAAzyNosl-1WbFjquCnYe5nE>
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: Tue, 16 Feb 2021 00:15:17 -0000

On 2/14/2021 5:30 PM, John R. Levine wrote:
> 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.


It's almost amusing to think that a field specific to delivery is 
affixed by a module that doesn't do deliveries.  But only almost.

The idea that an MTA does some deliveries, as an accommodation to the 
alias mechanism, encourages an approach in which it is warts, all the 
way down.  Let's fix one wart by adding another.

Preferring simplicity instead of warts, the better modeling view is that 
aliases are handled by an MDA function.

Some offline discussion has uncovered limitations in RFC 5598 -- 
especially with the architecture diagram -- and that it needs revision, 
to provide better handling of a case like this.  For example, the 
current diagram requires all deliveries to go through a message store, 
which obviously is not correct for the alias example.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net