Why does RT alter the mail header ordering? If we get spam sent to
RT I'd like to build a Scrip to report the spam, but it appears that
RT is so misordering the mail headers that this becomes impossible.
They aren't alphabetical... or really anything I can find. They
appear to be
On Tue 27.Jan'09 at 11:59:39 -0800, Jo Rhett wrote:
Why does RT alter the mail header ordering? If we get spam sent to
RT I'd like to build a Scrip to report the spam, but it appears that
RT is so misordering the mail headers that this becomes impossible.
They aren't alphabetical...
On Jan 27, 2009, at 12:03 PM, Jesse Vincent wrote:
Last time this came up, I found the reference in RFC822 or 2822 that
said that headers weren't technically an ordered list.
Yes, but in practice everyone has shifted away from this. Received
header ordering is absolutely necessary for
On Tue, Jan 27, 2009 at 12:11:35PM -0800, Jo Rhett wrote:
Is there any place that RT stores the original, unaltered message?
Not by default, no. The first thing RT does when it gets its mitts on a
mesage is split it into seperate MIME bodies and normalize them to UTF-8.
Were I going to
Following up on my own post:
RFC 2822, 3.6:
...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
