On Friday June 16 2006 20:33, Rosenbaum, Larry M. wrote: > Is there anything in RFC-2822 (or other RFC) that says that an MTA can't > take those X-Spam headers that SpamAssassin so nicely put at the top of > the message and move them to the bottom? Our MTA moves these headers > and some others and I'm wondering if we have any basis for griping about > it. It seems like this would break DomainKeys, but I don't see anything > in 2822 that would prohibit this (as long as the Received: headers > aren't rearranged).
RFC 2822 says "SHOULD NOT be reordered" It is important to note that the header fields are not guaranteed to be in a particular order. They may appear in any order, and they have been known to be reordered occasionally when transported over the Internet. However, for the purposes of this standard, header fields SHOULD NOT be reordered when a message is transported or transformed. More importantly, the trace header fields and resent header fields MUST NOT be reordered, and SHOULD be kept in blocks prepended to the message. See sections 3.6.6 and 3.6.7 for more information. and SHOULD means DON'T, unless there is a VERY good reason for doing otherwise. It would definitely break DomainKeys, if signer chose to sign one of the header fields that got rearranged. Mark
