XADM: Message Forwarded Through Chinese Traditional Client Not Displayed Correctly

If a rule is applied that forwards a message from an English client to a Chinese Traditional (CHT) client, and then another rule is applied that forwards the message from the Chinese Traditional client to itself (or to another Chinese Traditional client on the same server), the second forwarded message may not be displayed properly. This message contains a copy of the first forwarded message, which contains a copy of the original message. In the copy of the first forwarded message, the From, Sent, To, and Subject fields and the "Auto forwarded by a Rule" text are all displayed as question marks (?). For example, the body of the second forwarded message may appear similar to the following: Note that this problem only occurs with plain text messages or with Rich Text Format (RTF) messages that do not contain any text in the message body. RTF messages with no message body are sent as plain text. The problem does not occur with Hypertext Markup Language (HTML) messages.

This problem is known to occur with Outlook 98 and Outlook 2000, but it may also occur with other e-mail clients.

When you send a plain text message, Exchange Server converts the message to RTF and adds the \fromplain tag to the RTF header. When this tag exists, Outlook 98 and Outlook 2000 convert the message back to plain text when it is received.

When the Chinese Traditional client forwards the message, it adds Chinese Traditional characters to the body of the message. However, when Outlook 98 and Outlook 2000 convert the message to plain text, they use the message's original character set. In this case, the original character set does not support the Chinese Traditional characters that are added when the message is forwarded. Therefore, the characters are not converted properly.

To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: The English version of this fix should have the following file attributes or later:

Component: Information Store

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3.