On Tue, 2004-09-07 at 07:08 +0100, Graham Murray wrote:
And by the same RFC, some of the situations which some discussion on
this last has suggested that Resent-* headers might be inserted (by
the MTA) are not valid usage of those fields. If the mail is
originally addressed to me(_at_)alumni(_dot_)org and is then forwarded to my
"real" address me(_at_)example(_dot_)com, then it is valid for alumni.org to
add
Resent-* headers.
Says §3.6.6 of RFC2822:
"Resent fields SHOULD be added to any message that is reintroduced by
a user into the transport system."
Note 'by a user'. This implies that it shouldn't be done when the
message is forwarded automatically. But there's no need for inference --
it's made quite explicit a couple of paragraphs further down:
"Note: Reintroducing a message into the transport system and using
resent fields is a different operation from "forwarding".
"Forwarding" has two meanings: One sense of forwarding is...
<...irrelevant to us right now ...>
...On the other hand, forwarding is also
used to mean when a mail transport program gets a message and
forwards it on to a different destination for final delivery. Resent
header fields are not intended for use with either type of
forwarding."
It is _not_ valid for 'alumni.org' to add Resent-* headers when
forwarding mail to your current address.
--
dwmw2