XFOR: CCMC Not Handling Bad Messages Correctly

 Last reviewed: July 15, 1997
Article ID: Q166561

The information in this article applies to:

  • Microsoft Exchange Server, version 5.0

SYMPTOMS

When the Lotus cc:Mail Export utility version 6.0 exports messages with Macintosh file attachments, the exported file is malformed. When you read this malformed file, the Microsoft Exchange Connector for Lotus cc:Mail stops responding, a Dr. Watson is generated, or the message is sent without attachments but the message is never passed to the bad directory.

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

A fix for this problem with the Microsoft Exchange Connector for Lotus cc:Mail is planned for Microsoft Exchange Server 5.0 Service Pack 1 (SP1). The "bad" messages will be placed in the "bad" directory and/or an event will be logged by Connector for cc:Mail to indicate that a "bad" message was received. so 

   that both postoffices get the addressing information.
6. Using the cc:Mail Mac client v2.2, connect to the DB6 postoffice and 
   send a mail message to a Microsoft Exchange user.

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.