XFOR: Message Characters Corrupted When Different Locale Used

 Last reviewed: July 15, 1997
Article ID: Q166615

The information in this article applies to:

  • Microsoft Exchange Server, version 5.0

SYMPTOMS

When a computer running Microsoft Exchange Client or a POP3 client is configured with a different code page than the computer running Microsoft Exchange Server version 5.0 uses to send a MIME-encoded message, the message body becomes corrupted.

An example of this scenario is when the Microsoft Exchange Server computer is configured with standard settings (US-ASCII for POP3, ISO-8859-1 for the Internet Mail Service) and the client being used has another code page installed.

CAUSE

The message body becomes corrupted because the MIME header does not match the message body type. This will affect all outbound MIME messages where the code page on the server differs from the client locale.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.0. This problem was corrected in the latest Microsoft Exchange Server 5.0 U.S. Service Pack. 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.sp1 kbusage XFOR
Version : 5.0
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

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: July 15, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.