XFOR: Corrupted Message When Using Hebrew or Arabic

 Last reviewed: April 15, 1997
Article ID: Q157012
The information in this article applies to:
  • Microsoft Exchange Server, version 4.0

SYMPTOMS

Messages sent from an Arabic or Hebrew edition of the Microsoft Exchange Server to an Arabic or Hebrew edition of MS-Mail 3.x, or vice versa, with Arabic or Hebrew text in the message header and/or the message body, may appear garbled.

For example, all Arabic or Hebrew text appears as follows: 

   ????C???E???

CAUSE

The Microsoft Mail Interchange (MSMI) does not support Arabic or Hebrew language content.

RESOLUTION

To resolve this problem:

  1. Apply the fix referenced below.

2 On the Interchange tab of the MS Mail Connector object, click 
   Properties.

  • Select Arabic or Hebrew in the "Primary Language for Clients" list box.

    STATUS

    Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange 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:
    Keywords : kbbug4.00 kbfix4.00.sp3 kbnetwork XFOR
    Version : 4.0
    Platform : WINDOWS

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