Re: Exchange mucking with the headers

--gDGSpKKIBgtShtf+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Aug 31, 2011 at 08:47:20AM -0600, Aaron Toponce wrote:
> 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.

I guess thinking about this a little further, I could put every token under
one "X-Hashcash" field, separated by semicolons, or something similar.
Thoughts on this approach?

--
. 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

--gDGSpKKIBgtShtf+
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

iQEcBAEBCgAGBQJOXktXAAoJEM55Ebf8BAiPmbIH/3rEwA5rAuAjR8j9hcXZ/9zK
xaA9Tyihzv3S8mMLaG4x6NQl9gfLG7DQTi1Vl4LliK+s3WdP1OLhBrixj1kNEZ7x
rb7fWthWK778ZKX6+sgFhMwSit8c2zKN2O+keL54f/1BpEL6UU6RI4qNGjhS3+YR
/2scaQjxRe9ZhEVUROgWT35Gfzc8OfZ9bkBcB1WCX78EHa+AQOl72f4bQWpkwrgu
JzaGRf7nYTUPVWVuwKL0uVurAqJmcqK885RL2CBRGmvoel7KZMxjE46cybXUy2wU
EkYiiwGnhKzezZaJS17ddD52DmSKcUOd444lS8AbZSnmeL+zEt4WQsDT80MH7Nw=
=0JTr
-----END PGP SIGNATURE-----

--gDGSpKKIBgtShtf+--