On Mon, 2004-09-13 at 13:03, Jim Lyon wrote:
[snip]
So, what's Resent-From for? It's for when a message arrives at the
destination mailbox, and the owner of that mailbox gives instructions,
either manually or automatically, that the message should instead or
additionally be delivered to a different mailbox. A Unix ".forward"
file is the canonical example of such automated instruction.
Well, if your going to use the Unix ".forward" file as a canonical
example, then you should check what that does on a typical Unix box
today (and historically). Frankly, that's an honest suggestion, because
although I'm not too sure what they've done historically, I did just
check it out on a Linux box of mine and sure enough, there are no
Resent-* fields added whatsoever.
In at least two places in section 3.6.6 of RFC2822, Resent-* fields
are said to be used to identify a message as re-introduced *by a user*
into the transport system. Furthermore, it also says this:
"They MUST NOT be used in the normal processing of replies
or other such automatic actions on messages."
Which directly contradicts part of your interpretation above. It's not
for 'manually or automatically' re-inserted messages, but only manually,
given that the automatic re-insertion is excluded from using Resent-*
fields according to the above line I've quoted from section 3.6.6 of
RFC2822.
It would probably be a good idea for Pete Resnick (editor of RFC 2822)
to chime in on this interpretation.
Hmm, agreed. That would probably put an end to the discussion :-).
--
-Paul Iadonisi
Senior System Administrator
Red Hat Certified Engineer / Local Linux Lobbyist
Ever see a penguin fly? -- Try Linux.
GPL all the way: Sell services, don't lease secrets