[hashcash] Re: Exchange mucking with the headers
- From: John Honan <jhonan@xxxxxxxxx>
- To: hashcash@xxxxxxxxxxxxx
- Date: Wed, 31 Aug 2011 16:02:40 +0100
Could it be the Exchange 2010 Address Rewriter agent messing with the
header?
http://technet.microsoft.com/en-us/library/aa996806.aspx#SMTP
You can check out the rewriter rules for your server;
http://technet.microsoft.com/en-us/library/aa997185.aspx
But if this is the default behaviour of Exchange, then a more robust
solution would be... a workaround!
John.
On 31 August 2011 15:47, Aaron Toponce <aaron.toponce@xxxxxxxxx> 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.
>
> 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
>
--
www.payback.ie
Irish Payroll Software
Other related posts:
