Consider the following scenario:
- You create a disclaimer transport rule in an environment that has Update Rollup 1 for Microsoft Exchange Server 2010 Service Pack 3 (SP3) installed.
- The transport rule is applied to all messages, and appends some text to email messages.
- The disclaimer transport rule tries to apply the disclaimer to an HTML-formatted message.
In this scenario, the HTML-formatted message cannot be delivered to recipients, and the EdgeTransport.exe process crashes on the Hub Transport server. Additionally, the following event is logged in the Application log:
Log Name: Application
Source: MSExchange Common
Event ID: 4999
Task Category: General
Watson report about to be sent for process id: Process ID, with parameters: E12, Build Type, Version Number, edgetransport, unknown, M.E.D.T.E.P.M.E.D.T.E.IBody.GetContentWriteStream, System.NullReferenceException, Call Stack Hash, Assembly Version.
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:
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:
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:
For more information about how to configure a disclaimer, go to the following Microsoft website: