XCLN: Mac Client Doesn't Handle MacBinary Type I Attachments

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

SYMPTOMS

When you are running a Microsoft Exchange Macintosh client and receive a message with attachments that are in MacBinary I format, the following error will be displayed when you open the message: 

   /!\ Can't get the time stamp of MacintoshHD:System Folder:
   Exchange Temporary Items:Attachment Name.
   Microsoft Exchange will assume it is dirty.  <OK>
It will be followed by: 

   /!\The application associated with this attachment could not be
   started. Attachment Name (System Error = -43) <OK>
and then when you close the message: 

   [Attachment Name]  - has actual attachment name
   /!\The temporary file has disappeared. Changes could not be saved.
   <OK>

CAUSE

Currently, the Microsoft Exchange Macintosh client does not support attachments in MacBinary I format

WORKAROUND

Originators should send you messages using any encoding other than MacBinary I.

Note: The Macintosh Client does support the MacBinary II format.

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 kbusage XCLN
Version : 4.0
Platform : MACINTOSH

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.