XADM: Message Forwarded Through Chinese Traditional Client Not Displayed Correctly

ID: Q235965

The information in this article applies to:

Microsoft Exchange Server, version 5.5
Microsoft Outlook 98

SYMPTOMS

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:


   ----------
   ???:  <recipient1>
   ????: <time2>
   ???:  <recipient2>
   ??:   FW: <subject>
   ???????

   ----------
   From: <sender>
   Sent: <time1>
   To:   <recipient1>
   Subject: <subject>
   Auto forwarded by a Rule

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.

CAUSE

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.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:

Component: Information Store

File name	Version
Store.exe	5.5.2637.0

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.

Additional query words: autoforward


Keywords          : exc55 
Version           : WINDOWS:98; winnt:5.5
Platform          : WINDOWS winnt 
Issue type        : kbbug

Last Reviewed: July 23, 1999