Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
XIMS: Extended Characters Are Not Displayed Correctly in the Subject Field
Article ID: 314927 - View products that this article applies to.
This article was previously published under Q314927
If a message from a Microsoft Mail Connector with code page 850 comes to an Exchange 2000 server by means of another Exchange 2000 server that is running the Microsoft Mail Connector, extended characters in the subject of that message may seem to be garbled.
Exchange 2000 receives the message with valid Transport-Neutral Encapsulation Format (TNEF) with code page 850. Exchange 2000 decodes TNEF, gets PR_MESSAGE_CODEPAGE (850), and then sets it correctly in the cache, but converter's code page (1252) overwrites that setting. Therefore, Exchange 2000 has an incorrect code page set to 1252 instead of 850. Because there is no valid conversion between 850 and 1252, Exchange 2000 converts the message incorrectly:
Received: from dlg2-04.dlgleo.com ([188.8.131.52]) by dlg2-05.dlgleo.com with Microsoft SMTPSVC(5.0.2195.2966);
Fri, 5 Oct 2001 02:34:54 -0700 content-class: urn:content-classes:message Return-Path: IMCEAMS-CYB_BP1_Admin@dlgleo.com X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
X-OriginalArrivalTime: 05 Oct 2001 09:34:54.0903 (UTC)
Date: Thu, 4 Oct 2001 14:42:00 -0700
From: "Administrator" IMCEAMS-CYB_BP1_Admin@dlgleo.com
To: "Jorge Pinero" firstname.lastname@example.org
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378The English version of this fix should have the following file attributes or later:
(http://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Component: Information store
Collapse this tableExpand this table
NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.