XFOR: Unable to Open Attachment from ccMail

 Last reviewed: July 15, 1997
Article ID: Q166610

  • Microsoft Exchange Server, version 5.0

SYMPTOMS

You send a message from Lotus cc:Mail to Microsoft Exchange by way of the Microsoft Exchange Connector for Lotus cc:Mail. If the message has attachments that have filename extensions containing numeric characters, the message arrives but the attachment cannot be opened due to an invalid file type.

WORKAROUND

To work around this problem:

  • When you receive the attachment with data and time appended, save the attachment using the Save As function and rename the file at that time.

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

MORE INFORMATION

The most common file type this problem occurs with is Lotus 123 WK4; however, any file extension with numeric character will experience the problem. For example if a file named Abc.wk4 is sent from cc:Mail, the attachment is received on the Microsoft Exchange side with the file name Abc.wk4 5/6/97 3:10PM. Because of the invalid file extension type, you will not be able to open the file along with the file association.

Keywords : kbbug5.00 kbfix5.00.sp1 kbusage XFOR
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.