Random Chinese Characters in Exchange 2010 SP1 Emails

I have been sent a few emails from a client that start like this:

格tml> 格ead> 猼tyle㰾!– .hmmessage P { margin:0px; padding:0px } body.hmmessage { font-size: 10pt; font-family:Tahoma } –>⼼style> ⼼head> 㰊body class=’hmmessage’>

The HTML characters repeat throughout the message, but not on every message, though those sent from Hotmail are typically affected (but it is not always Hotmail).

The problem is due to the email having character encoding in the charset META tag that differs from the character encoding in the MIME part and a HTML disclaimer having been added. When Exchange 2010 SP1 adds the HTML disclaimer it re-encodes the message and this results in a corrupt message because the wrong character set information is read.

The fix for this has been documented in KB969129, which refers to Exchange 2007, but the same fix is true for Exchange 2010 SP1.

The fix is to add the DisableDetectEncodingFromMetaTag attribute to EdgeTransport.exe.config. This file can be found at \Program Files\Microsoft\Exchange Server\V14\bin and can be opened in Notepad. Make a backup of the file before you change it and then add to the area of the file the following


After you save the config file you need to restart the Microsoft Exchange Transport service for the setting to take effect.



, , , , , , ,




5 responses to “Random Chinese Characters in Exchange 2010 SP1 Emails”

  1. James W avatar

    YES! Thank you so much.

    this post solved my issue. After shouting at my SPAM Filter for causing it… then the dog, then my colleagues.

  2. Anonymous avatar

    SHow I do this only at our 2 Edge Servers or should I do it at our 2 Hub Transport Servers too?

  3. Brian Reid avatar

    @Anon. You only need do this on all your Hub Transport servers as this problem is an issue caused by the Transport Rules agent and this agent is only found on Hub Transport servers. The Edge Rules agent (on Edge servers funnily enough) does not do disclaimers.

  4. Phat avatar

    Hello, i’m facing this problem in Exchange Server 2013. Does the above instruction works for Exchange Server 2013?
    Please help!

    1. Brian Reid avatar

      I’ve not tried, but the code underlying transport is similar across versions so I would say give it a go and let me know.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.