Consider the following scenario. A mailbox that is located on a Microsoft Exchange Server 2007 server has a server-side rule that forwards e-mail messages to target recipients. The original e-mail message is included in the body of the forwarded message. In this scenario, the recipients experience the following symptoms:

•	If the original e-mail message contains double-byte character set (DBCS) characters in the subject line, the DBCS characters are converted into question marks in the forwarded e-mail message. This is also true if the original message contains DBCS characters in the display name of the recipient.
•	If the sender of the original e-mail message has a display name that contains DBCS characters, the sender's display name in the forwarded e-mail message is changed to the following legacyExchangeDN attribute: /o=<org>/ou=<AG>/cn=Recipients/cn=<xxx>

Back to the top

This problem occurs because Exchange 2007 uses English as the code page when Exchange 2007 processes the server-side rule that forwards e-mail messages to target recipients. Exchange does not use the code page of an e-mail message to process the rule. The header information for the original e-mail message is incorrect if DBCS characters are included.

Back to the top

To resolve this problem, install Update Rollup 3 for Exchange Server 2007.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

To work around this problem, use the Forward it to people or distribution list as an attachment rule so that the original message will be an attachment of the forwarded message.

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

For more information about the terminology that Microsoft uses when software is updated, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the naming schema for Exchange Server software update packages, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top