XFOR: Messages with Non-ANSI Characters Arrive with Garbage

Last reviewed: February 12, 1998
Article ID: Q177957

The information in this article applies to:

Microsoft Exchange Server version 5.0

SYMPTOMS

E-mail messages arriving through the Internet Mail Service (US English) that contain non-ANSI characters such as DBCS (Japanese, Korean, and so on) may arrive with corruption or unusable characters such as squares or boxes in place of the originally intended characters. This can occur in messages using RTF or HTML objects as attachments.

CAUSE

The predefined RTF font table is always set to an ANSI character set. This causes non-ANSI characters to be converted into unusable or garbage characters.

STATUS

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

This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

MORE INFORMATION

Additional code added to Exchange Server version 5.5 allows an extra font in the RTF conversion table that eliminates this problem.

Keywords          : kbbug5.00 kbfix5.00.sp2 XFOR
Version           : WINDOWS:5.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbfix kbpatch

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.