Re: preventing header tag spoofing without crypto

in my experience, RFC2822 tags are shuffled around and added if
nonexistent, unrecognized tags are left alone.  We are contemplating
introducing a new standard tag, and we may declare that its ordering
is to be left alone as part of its specification.  Systems that do
rearrange it will be out of compliance.  They will also be on the
far side of our compliant systems.  By leaving everything in order
it is simple and clear, the top of the headers is near and as we
get farther into the headers we are reading something farther and 
farther away.  Story headers get added at the top, just like
geologic strata. :^)




Laird Breyer wrote:
 >  The ordering of
 > header tags other than Received: is not necessarily honoured by a
 > transport agent.





-- 
[email protected].
I know you, junk mail. Gonna miss you when you're gone