Article ID: 2859596 - View products that this article applies to.
Consider the following scenario:
Log Name: Application
This issue occurs because the message body and the disclaimer text use the same character encoding. This causes an issue in which a null charset parameter is called in the character encoding.
To resolve this issue, install the following update rollup:
(http://support.microsoft.com/kb/2866475/ )Description of Update Rollup 2 for Exchange Server 2010 SP3
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about a similar issue, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2870028/ )EdgeTransport.exe crashes when an email message without a sender address is sent to an Exchange Server 2010 Hub Transport server
For more information about the character encoding, go to the following Microsoft website:
White Paper: Message FormattingFor more information about how to configure a disclaimer, go to the following Microsoft website:
How to configure a disclaimer
Article ID: 2859596 - Last Review: August 13, 2013 - Revision: 4.0