What prompted me to post the question was the high priority assigned
to the Errors-To: header record.
Doing some e-mail header lawyering:
Header precedence sequence as per RFC 822, paragraphs 4.4.2, and
4.4.4, (RFC 2076 discourages use of Errors-To:, used in mailing
lists; From_, which is used as a UUCP header as per RFC 976; Path:,
as per RFC 1036 defined USENET headers; and Return-Receipt-To:, all
of which are non-standard, as per 2076,) Sender: followed by From:,
and Resent-Sender: followed by Resent-From: for the machine
generated address.
For the trusted address, (i.e., formail -rt,) its similar, with a
header precedence sequence as per RFC 822, paragraphs 4.4.1, and
4.4.4; Reply-To: followed by From:, and Resent-Reply-To: followed by
Resent-From:.
However, the Return-Path: must be used for notification of
non-delivery as per RFC 2821 paragraph 4.4, (unless the return path
contains a null address, as per RFC 2821 paragraph 6.1 and RFC 1123,
paragraph 5.3.3, in which case notification is forbidden because of
mail looping issues.)
How well such strict formality would work in the real world is another
issue, entirely.
John
BTW, there can be multiple Resent-* groupings, the grouping near the
top of the message has the precedence. And, something I didn't know,
there can be multiple From_ records in a message-the first one has the
precedence.
David W. Tamkin writes:
Alan wrote,
| I have a file here called ... formail.html. Don't know where it came
| from.
It came from the distant past; its listing is obsolete. Philip gave the
current precedences in his post.
--
John Conover, conover(_at_)rahul(_dot_)net, http://www.rahul.net/~conover
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail