On Thu, 8 Sep 2005, John C Klensin wrote:
Now, for this case, I am personally pretty rigid: if the mailing
list exploder starts messing with (including inserting)
non-envelope (i.e., as things are now defined, non-trace)
headers (or body information), it is performing an MUA-level
function and is hence not an MTA-level exploder at all. [...]
But 2369 could have been written, or could now be updated, to designate
the List-* headers as trace fields to be inserted by an MTA-level
exploder.
Is 2822bis going to make the set of trace fields extensible so that this
would be possible? RFCs 3864 and 4021 would probably have to be updated so
that the IANA registry documents the trace/non-trace distinction.
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.