XFOR: Message Attachments Received Without Original Name

Last reviewed: March 11, 1998
Article ID: Q182273
The information in this article applies to:
  • Microsoft Exchange Server, versions 5.0 and 5.5

SYMPTOMS

Attachments received via an X.400 connector that originate from an Isocor MTA arrive without any indication of the original attachment name.

CAUSE

Isocor X.400 systems attach additional information when transferring attachments to track attachment names (attachment manifests). Prior to Exchange Server 5.0, this additional information arrived as a text attachment detailing attachment names. However, Exchange Server 5.0 and 5.5 incorrectly interprets this information to try to re-build the attachment with a name. As a result, the attachment name is no longer available.

STATUS

Microsoft has confirmed this to be a problem in Exchange Server versions 5.0 and 5.5. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.


Additional query words: isocor x.400 attachment manifest
Keywords : XFOR
Version : WINDOWS:5.0,5.5
Platform : WINDOWS
Issue type : kbbug


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