XCON: DBCS Chars in Subject of Embedded Message not Converted

Last reviewed: September 11, 1997
Article ID: Q151373

The information in this article applies to:

  • Microsoft Exchange Server versions 4.0 and 5.0

SYMPTOMS

Site A is connected by an X.400 Connector to Site B, which is in turn connected by an X.400 Connector to Site C.

NOTE: There is no replication between Site A and Site C.

A user on Site A sends a message to a user on Site C. This message contains an embedded message in which the subject field has characters from the double-byte character set (DBCS). On the destination client, the embedded message's subject line contains invalid characters.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server versions 4.0 and 5.0.

We are researching this problem in Microsoft Exchange Server version 4.0 and will post new information here in the Microsoft Knowledge Base as it becomes available.

This problem was corrected in the latest Microsoft Exchange 5.0 Server 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          : kbbug4.00 kbbug5.00 kbfix5.00.sp1 XCON kbusage
Version           : 4.0 5.0
Platform          : WINDOWS
Issue type        : kbbug
Solution 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: September 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.