Thanks for the contribution..
One thing that isn't addressed in that Dave, is cases where the
Delivered To address exists, and the message is routed back out the
internet,. Still seeing cases in the wild where the Delivered To is
added, but it isn't really the transfer of responsibility, but rather a
routing of email to another system that will be doing that.
I think a comment on what to do with Delivered To headers that are added
that really shouldn't exist.
This is also common to see in email replay spam etc.
Also, a direct statement that Delivered TO is a type of trace header
might be in order.
-- Michael --
On 2022-04-14 06:34, Dave Crocker via mailop wrote:
Folks,
This was just issued. It will aid in evaluating handling history of a
messsage, especially through aliasing and mailing list sequences.
d/
-------- Forwarded Message --------
Subject: RFC 9228 on Delivered-To Email Header Field
Date: Wed, 13 Apr 2022 23:04:21 -0700 (PDT)
From: [email protected]
To: [email protected], [email protected]
CC: [email protected], [email protected]
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: [email protected]
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 [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
--
"Catch the Magic of Linux..."
------------------------------------------------------------------------
Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
------------------------------------------------------------------------
604-682-0300 Beautiful British Columbia, Canada
This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
