On Sun, 29 May 2005, william(at)elan.net wrote:
To be fair, I don't quite agree with how Pine did it as it put Resent-
below the reset of the message header and not above it.
Besides that Pine also quite interestingly changed the data and replaced
all trace fields with "X-" (but did not touch any other fields then
Received or Return-Path). In any case this all very clearly demonstrates that
its new message and not the original when the message is resent.
Both of these are because Pine implements the RFC 822 semantics of
Resent-* which only allow for one set of trace fields and one resending of
the message. I don't know of any sofware that implements RFC 2822 Resent-*
semantics. Exim supports resending when acting as an MSA, but uses 822
semantics; it's roughly command-line compatible with Sendmail, so I would
expect Sendmail to do something similar with resent email, though I don't
know if it is 822 or 2822 in this respect.
Sender-ID requires RFC 2822 Resent-* semantics for its forwarding
work-around to have even the slightest chance of working.
Tony.
--
f.a.n.finch <dot(_at_)dotat(_dot_)at> http://dotat.at/
BISCAY: WEST 5 OR 6 BECOMING VARIABLE 3 OR 4. SHOWERS AT FIRST. MODERATE OR
GOOD.