[rfc-dist] RFC 9228 on Delivered-To Email Header Field
rfc-editor@rfc-editor.org Thu, 14 April 2022 06:06 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 56DBB3A0404; Wed, 13 Apr 2022 23:06:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1649916369; bh=AUF6Ysga+NWf7kNp4OWXd4nBeMZQ8IZU+s9jfueVju8=; h=To:From:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc; b=dmdFgSVC+5ZAsetOd+grjQkEjaDFHlNJQ5YuinN7w0fDkwLIEMe3WWIECt0zqnp7z V65xtOioRYofXmT0mLSC0ktHdWm2vm0hRrqdcMlB49ZawyVoTOpRIjE9z/BZPqt75H 6T+bgRBgCjHZoBXIHvRJPavummiYc6Vf5u9FWyxg=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Wed Apr 13 23:06:00 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CBDC53A02D0; Wed, 13 Apr 2022 23:04:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1649916274; bh=AUF6Ysga+NWf7kNp4OWXd4nBeMZQ8IZU+s9jfueVju8=; h=To:From:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc; b=cO1Xgf6dzluCpg4H+5IDPe/xoTKNnE6ambP7iFzDbf2DRr7BP7tMU4zTKF3qVwRwP xn1iffayk+wYJmcaGeImqpExI8ByiyeUTJ1a8jqKbrNfouOP5U4p8m/VrXjUuYiKc1 6DMc2ZfPv/URP8tbUGW16Gq6PdoSDxi7kJnL0csk=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D60AA3A006A; Wed, 13 Apr 2022 23:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.659
X-Spam-Level:
X-Spam-Status: No, score=-6.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 3vMWxJO3wjlH; Wed, 13 Apr 2022 23:04:22 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F23573A0120; Wed, 13 Apr 2022 23:04:21 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 3E0BE6AA5B; Wed, 13 Apr 2022 23:04:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20220414060421.3E0BE6AA5B@rfcpa.amsl.com>
Date: Wed, 13 Apr 2022 23:04:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/SEx1ctCUyK_HJiVyVv6CDas8j9E>
Subject: [rfc-dist] RFC 9228 on Delivered-To Email Header Field
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9228
Title: Delivered-To Email Header Field
Author: D. Crocker, Ed.
Status: Experimental
Stream: Independent
Date: April 2022
Mailbox: dcrocker@bbiw.net
Pages: 10
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-crocker-email-deliveredto-10.txt
URL: https://www.rfc-editor.org/info/rfc9228
DOI: 10.17487/RFC9228
The address to which email is delivered might be different than any
of the addresses shown in any of the content header fields that were
created by the email's author. For example, the address used by the
email transport service is provided separately, such as through
SMTP's "RCPT TO" command, and might not match any address in the To:
or cc: fields. In addition, before final delivery, handling can
entail a sequence of submission/delivery events, using a sequence of
different destination addresses that (eventually) lead to the
recipient. As well, a receiving system's delivery process can produce
local address transformations.
It can be helpful for a message to have a common way to record each
delivery in such a sequence, noting each address used in the sequence
to that recipient, such as for (1) analyzing the path a message has
taken, (2) loop detection, or (3) formulating the author's address in
a reply message. This document defines a header field for this
information.
Email handling information discloses details about the email
infrastructure, as well as about a particular recipient; this can
raise privacy concerns.
A header field such as this is not automatically assured of
widespread use. Therefore, this document is being published as an
Experimental RFC, looking for constituency and for operational
utility. This document was produced through the Independent
Submission Stream and was not subject to the IETF's approval process.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org