On Wed, 15 Dec 2004, Douglas Otis wrote:
These resent headers could be seen as optional and happen to be
unlimited in number. Resent-Sender/Resent-From is created when the
entity identified in this field resends a message with the intent of the
message appearing to be unchanged.
Resent fields prepends to a message reintroduced, where this set of
fields are added each time this is done.
You're assuming 2822 semantics here, but in my experience most
implementations follow 822 semantics for Resent-*. The implications of
this are that ordering of Resent-* does not generally follow the 2822
prepend rule, and software is likely to be confused by the presence of
more than one Resent-* set.
There's a general problem in 2822 that although it re-defines Resent-*
as being part of the trace fields, it doesn't allow for general extension
of trace fields despite the fact that this is a common requirement (e.g.
Delivered-To: headers in alias-forwarding).
Tony.
--
f.a.n.finch <dot(_at_)dotat(_dot_)at> http://dotat.at/
SHETLAND ISLES: SOUTHWEST 6 OR 7 VEERING WEST 5 OR 6 THEN VEERING NORTHWEST 7
TO SEVERE GALE 9. SQUALLY SHOWERS. MODERATE OR GOOD. VERY ROUGH, BUILDING HIGH
IN WEST LATER.