XFOR: Garbled Attachments Between Exchange 4.0 and 5.0 IMCs

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

SYMPTOMS

When you send multiple attachments across Internet Mail Connectors (IMCs) between a computer running Microsoft Exchange Server 5.0 and another computer running Microsoft Exchange Server 4.0, every other attachment will be garbled if the IMCs are configured to transfer messages in binhex.

CAUSE

The binhex decoder consumes the blank line that separates each binhex bodypart. If the message contains consecutive binhex bodyparts with no blank lines between these bodyparts, every second binhex bodypart is copied to PR_BODY undecoded.

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 4.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 : kbbug4.00 kbfix4.00.sp4 kbusage XFOR
Version : 4.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: April 6, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.