Exchange mucking with the headers

Aaron Toponce <[email protected]> Wed, 31 Aug 2011 08:47:20 -0600
Newsgroups gmane.mail.spam.hashcash
Message-ID <[email protected]>
--RYJh/3oyKhIjGcML
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

I've come to the knowledge that Exchange is mucking with the mail headers,
stripping out any duplicate fields. This is troublesome for me, as sending
a mail to multiple recipients, means minting many Hashcash tokens, and
placing each token in the header with "X-Hashcash". There may be more than
one present. However, Exchange changes "X-Hashcash" to "x-hashcash", and
removes any dupe "x-hashcash" fields.

I could stamp each mail upon delivery, rather than mail creation, but that
would meach changing the way I handle SMTP with Mutt, and that's not
something I'm really interested in persuing. AFAIK, there is no "standard"
against duplicate header fields, so my multiple "X-Hashcash" tokens should
be just fine.

Has anyone else noticed this? Is there a server-side setting on Exchange
that prevents Exchange from mucking with the headers?

Thanks,

--
. o .   o . o   . . o   o . .   . o .
. . o   . o o   o . o   . o o   . . o
o o o   . o .   . o o   o o .   o o o

--RYJh/3oyKhIjGcML
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: http://tinyurl.com/aarongpg

iQEcBAEBCgAGBQJOXkl4AAoJEM55Ebf8BAiP+HAH+waaMrBhBMq8vWfy833e0svM
EYTI5HTglzNjDUnupg+VYUow+w32DphdDLM75bIXXgynFo1y4W2WKid4w0wbO4wu
xGGvcL4RhDjuwLhvjpsi6gRdhc825NudBph+xuct16Q+73yhuHv8HaGpuwRucFTZ
2bvZhQ60iItqrXTPTfz4IAOJURSJyDbrRYcrkwE2qeAy0H/yWB6gYE2Fv1JwUi+W
/A7fe4JFfV32ZCOfbsy5i14tRzBf3UubpmHnigPthAQw92LmXva5L+qCoP4Wcgm+
oXE5Q9b9c8K/7bKVxbL28PlrTEYFH5MLOa3zIbzgfXtvzyQOumQZeqHH7H90eAE=
=+0BC
-----END PGP SIGNATURE-----

--RYJh/3oyKhIjGcML--