XFOR: CCMC Not Handling Bad Messages Correctly

 Last reviewed: January 30, 1998
Article ID: Q169221
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 MAC file attachments; the exported file is malformed. When reading this malformed file; the ccmc will hang; Dr. Watson; or the message will be sent with no attachments but the message is never passed to the bad directory.

REPRO STEPS.

1) Setup Two ccMail POs 1DB8 and 1DB6 and configure the cc:Mail router to rout mail between the two. 2) Change the Save Exported/Imported messages Reg. options to 1. 3) Change the Max. number of message to Export/Import reg.options to 1 4) Connect the ccmc to a DB8 PO and start the ccmc using the Export/Import 6.0 utilities. 5) Run Dirsync on the ccmc so that both PO’s get the addressing information. 6) Using the cc:Mail Mac client v2.2 connect to the DB6 PO and send a mail message to an Exchange users.

MORE INFORMATION

This problem with the Microsoft Exchange Connector for Lotus cc:Mail has been fix. The new results are the “bad” messages are placed in the “bad” directory and/or an event is logged by CCMC to indicate that a “bad” message was received. eliminate this problem

Additional query words: ccmail mac tshoot
Keywords : XFOR
Version : WinNT:5.0
Platform : winnt
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: January 30, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.