IETF Logo Mail Archive

Re: [Emailcore] Ticket #8: Need a registry of header fields that are Ok to add after submission

Dave Crocker <dhc@dcrocker.net> Sun, 25 July 2021 18:28 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 EF6F43A3493 for <emailcore@ietfa.amsl.com>; Sun, 25 Jul 2021 11:28:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.091
X-Spam-Level:
X-Spam-Status: No, score=-2.091 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_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, 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 y17Hq4sYwOkN for <emailcore@ietfa.amsl.com>; Sun, 25 Jul 2021 11:28:19 -0700 (PDT)
Received: from dragonfly.birch.relay.mailchannels.net (dragonfly.birch.relay.mailchannels.net [23.83.209.51]) (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 95CD03A3462 for <emailcore@ietf.org>; Sun, 25 Jul 2021 11:28:19 -0700 (PDT)
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 4AAB7321DEF; Sun, 25 Jul 2021 18:28:18 +0000 (UTC)
Received: from gcp-us-central1-a-smtpout2.hostinger.io (100-105-161-168.trex.outbound.svc.cluster.local [100.105.161.168]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 32B413225E1; Sun, 25 Jul 2021 18:28:17 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from gcp-us-central1-a-smtpout2.hostinger.io (35.45.192.35.bc.googleusercontent.com [35.192.45.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256) by 100.105.161.168 (trex/6.3.3); Sun, 25 Jul 2021 18:28:18 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Grain-Coil: 4d836f954186b7f3_1627237698046_3375811620
X-MC-Loop-Signature: 1627237698046:2301138285
X-MC-Ingress-Time: 1627237698046
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 smtp.hostinger.com (smtp.hostinger.com) with ESMTPSA id 57A0A30B5560; Sun, 25 Jul 2021 18:28:15 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1627237696; bh=tgAaVN7KY1uU1sjO/jMApklTkrb4rQVjIgQuxHb+Wik=; h=Reply-To:Subject:To:References:From:Date:In-Reply-To; b=Zd8xh/1SBiUy5exvC5pdlUXMjaizZOOK8MJgoT1+Q/xLN246oEt9uv73cPRC/3FBD 2UNEImD5upOQx+bHx9OnwXkT3+7KTcNE1m2+o37JPYE1wCqniv5YTLlusOzTbAeIWV 1eSFowW+zVRHvwvryGMmgt+jG5mwuDjdtW8AwlzOTVTMG3R97pt58DARC9u+bXolLM zFlReRcgaY829aVdGSpfTfgduuyUu89V2js/Y8AzzV668FVJP4Waj+GGVmnoDtxI7z Qhuhf5kNaMJe1i/o+pId1uIJwM9pfKMxuAbnCaZ/Ij2NFTO3OXYj9UuJVa0SvLfk/n dfjLOqn7vpn2Q==
Reply-To: dcrocker@bbiw.net
To: Alessandro Vesely <vesely@tana.it>, emailcore@ietf.org
References: <e64e5ab8-fe18-7708-f8bf-6c5ee60658b6@isode.com> <13fcea10-e071-5707-a83d-38a2a92e1ac7@isode.com> <b91bb893-e94a-3d60-e984-dc6ab85d0883@tana.it>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <5ba9d71a-ca8b-8739-cc99-4ea63a3a6c72@dcrocker.net>
Date: Sun, 25 Jul 2021 11:28:14 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0
MIME-Version: 1.0
In-Reply-To: <b91bb893-e94a-3d60-e984-dc6ab85d0883@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/emailcore/5HPBXSIXkQyzWh9B3ZyRdeQZ15w>
Subject: Re: [Emailcore] Ticket #8: Need a registry of header fields that are Ok to add after submission
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: Sun, 25 Jul 2021 18:28:25 -0000

On 7/25/2021 3:36 AM, Alessandro Vesely wrote:
> On Fri 23/Jul/2021 14:21:51 +0200 Alexey Melnikov wrote:
>>
>> 4) Can be added by an MDA?
> 
> 
> Could we limit this, or split it into two parts?  As MDAs can re-inject 
> messages into the mail system, we should distinguish what headers can be 
> added or modified during delivery proper (rMDA, in rfc5598 parlance) — 
> such headers will never be transmitted via SMTP.
> 
> An example could be Munged-From:, the copy of a From: header that had 
> been munged by a MLM to mitigate DMARC damage.  This field is created by 
> the MDA before restoring the original value of From:.[*]


If an MDA is 're-injecting' a message, it is acting as an MUA or, at the 
least, an MSA.

As for limiting who can do what, there might be some benefit in such an 
exercise, but I'd expect it to be a long and painful effort...

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email