XFOR: Subject Field for SMTP Outbound Mails not ECU-KR Encoded

Last reviewed: July 15, 1997
Article ID: Q166577

The information in this article applies to:

  • Microsoft Exchange Server, version 5.0

SYMPTOMS

If the Korean Microsoft Exchange Client that is connected to US Exchange Server version 5.0 with the Build 1458.15 sends an SMTP mail message with Korean characters in the subject field, the Korean characters are not readable although KSC-5601 is set on the Character Set Translation for both MIME and non-MIME in the Internet Mail tab of the Internet Mail Service Properties.

CAUSE

The "euc-kr" label should be used to encode SMTP mails with Korean characters in the subject field. If you turn on the Message Archival on the Diagnostics Logging tab, the outbound SMTP messages with Korean characters in the subject saved in the IMCDATA\OUT\ARCHIVE directory should have "euc- kr" label in the subject field. One correctly encoded header is as follows:

   Message-ID: <6180A23D98B7D011BD4800A0C90D616D051C@server.company1.com>
   From:  <user1@company1.com>
   To: "'user2@company2.com'" <user2@company2.com>
   Subject: =?euc-kr?B?Rlc6IL7GufbB9g==?=
   Date: Thu, 22 May 1997 15:55:46 -0700
   X-Priority: 3
   MIME-Version: 1.0
   X-Mailer: Internet Mail Service (5.0.1457.3)
   Content-Type: text/plain; charset="iso-2022-kr"

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


Additional query words: kbkorea
Keywords : kbbug5.00 kbfix5.00.sp1 kbusage
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.