IETF Logo Mail Archive

Re: [Emailcore] Delivered-To issues

Dave Crocker <dhc@dcrocker.net> Thu, 07 January 2021 16:56 UTC

Return-Path: <dhc@dcrocker.net>
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 E4E603A128A for <emailcore@ietfa.amsl.com>; Thu, 7 Jan 2021 08:56:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.381
X-Spam-Level:
X-Spam-Status: No, score=-2.381 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.262, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 8vHZeqp-T8bD for <emailcore@ietfa.amsl.com>; Thu, 7 Jan 2021 08:56:42 -0800 (PST)
Received: from cross.elm.relay.mailchannels.net (cross.elm.relay.mailchannels.net [23.83.212.46]) (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 10F2A3A1289 for <emailcore@ietf.org>; Thu, 7 Jan 2021 08:56:41 -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 1F6AB10274B for <emailcore@ietf.org>; Thu, 7 Jan 2021 16:56:41 +0000 (UTC)
Received: from nl-srv-smtpout4.hostinger.io (100-96-27-97.trex.outbound.svc.cluster.local [100.96.27.97]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 8DAC310255E for <emailcore@ietf.org>; Thu, 7 Jan 2021 16:56:38 +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 DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.11); Thu, 07 Jan 2021 16:56:41 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Bottle-Cellar: 680a81405c68a0dd_1610038600985_3094493784
X-MC-Loop-Signature: 1610038600985:3345894047
X-MC-Ingress-Time: 1610038600985
Received: from [192.168.0.109] (c-24-130-62-181.hsd1.ca.comcast.net [24.130.62.181]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout4.hostinger.io (smtp.hostinger.com) with ESMTPSA id A558B30AB5FD for <emailcore@ietf.org>; Thu, 7 Jan 2021 16:56:36 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1610038597; bh=jf1Lb5w9ubVr/nGzbvH2BynlLxCbyuhdcVcQpftwIuo=; h=Reply-To:Subject:To:References:From:Date:In-Reply-To; b=QPteIH7h6qrfqGXM42wqjKj61sqqiH8XaRIdIaCjFl9QuKO2yPJrQCuOj0r+y64OK r1DAnJosaXFqgfasCbCPLKC/O11bz4Sq2QoZAmsnPhq7ndvfeSgD0XjiPCouFbJUnW uZVCdcc4ZZjPONnybbxhN23ryx1S4HgHSdn1Ig/k8O6gfff4fNK01sorPEQmeYACux TT2R9R1SAdhEF2BQ0DQ+fPud3SKq7Z8it9V5uAJ/rDhY/AkAlDcuCfQ/GIWw0WlVCG VTBJ6Vo0O7dAuoMkqK7E5Jl/zqs1Z8ZLooEzFNYSG1SeSzqkabE4Wf9NrphKnPAJlD 8nW124aCvduaw==
Reply-To: dcrocker@bbiw.net
To: emailcore@ietf.org
References: <20210106170718.9F6335CC249C@ary.qy>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <deb7fc3a-37a9-edc2-e22a-7a5fe19cd114@dcrocker.net>
Date: Thu, 07 Jan 2021 08:56:34 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210106170718.9F6335CC249C@ary.qy>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/emailcore/pVJXl4X-HA_u9pow1nETL8KUohw>
Subject: Re: [Emailcore] Delivered-To issues
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: Thu, 07 Jan 2021 16:56:44 -0000

On 1/6/2021 9:07 AM, John Levine wrote:
> In article <9f27f29f-2b4e-57ad-3d54-c2a5e04d8c62@tana.it> you write:
>> This discussion brought up another defect of RFC 5321, methinks.  It does not
>> define a straight line between an MTA and an MDA. ...
> 
> I think the problem is worse than that. What we're calling an MDA
> combines two separate things.  RFC 5598 calls them the hMDA and rMDA.
> 
> The hMDA is more or less the thing that takes an incoming message and
> disposes of it, by storing it in a file or otherwise. Most MTAs have a
> few simple default hMDA and ways to call out to more complex ones
> like procmail, maildrop, and Sieve.
> 
> I don't see any point in trying to rewrite 5321 to try to separate out
> an hMDA that might be in the MTA and might not.


For the purposes of 5321bis, the hMDA/rMDA distinction is almost 
certainly overly precise.  It distinguishes between two components 
within a functional unit.

What's needed for the bis document is merely to slightly modify the 
current language to add MDA language and citation, rather than to do any 
substantial rewriting.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email