--On July 13, 2006 6:40:07 PM -0500 wayne <wayne(_at_)schlitt(_dot_)net> wrote:
RFC2822 directly talks about adding Resent-* headers and forwarding:
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 that a
mail reading program can be told by a user to forward a copy of a
message to another person, making the forwarded message the body of
the new message. A forwarded message in this sense does not appear
to have come from the original sender, but is an entirely new
message from the forwarder of the message. 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.
Please note the last sentence: the Resent-* headers are not
intended for use with forwarding.
The second kind of forwarding is not referring to Resending a
message, it is referring to user forwarding, for example sendmail
.forward files. Note that in the second case the message never
leaves the transport system (and thus the never ever directly acts on
it). Neither of those use or should use Resent.
eric
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html