XFOR: Fail to Decode Inbound Messages with 1522 UTF Encoding

 Last reviewed: February 12, 1998
Article ID: Q177961
The information in this article applies to:
  • Microsoft Exchange Server, version 5.0

SYMPTOMS

When you log on as a user to a computer running Exchange Server 5.5 (server A) with Outlook client and send a message with MIME and RTFHTML to a user on a computer running Exchange 5.0 with Service Pack 1 (server B), the recipient may see garbled symbols and characters in the message body when the message is opened.

The two Exchange Server computers are connected through the Internet. The Internet Mail Service on the sending and receiving Exchange Server computers is set for both MIME and non-MIME.

CAUSE

This garbled text appears in the received message due to content conversion failure. This content conversion failure may be due to interoperability issues between Exchange 5.0 schema and Exchange 5.5 schema.

STATUS

Microsoft has confirmed this to be a problem in 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

Keywords          : kbbug5.00 kbfix5.00.sp2 XFOR
Version           : WinNT: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.