XFOR: IMC Can’t Handle MIME w/ Content Type of Multipart/Digest

Last reviewed: March 24, 1997
Article ID: Q157705
4.00 WINDOWS kbusage kbbug4.00

The information in this article applies to:

  • Microsoft Exchange Server, version 4.0

SYMPTOMS

If the Internet Mail Connector (IMC) receives an incoming message that contains MIME bodyparts with content type = multipart/digest, the message remains stuck in the Imcdata\In directory and never reaches the destined recipient.

The IMC reports the Event ID 4037 (Internal Processing Error). The message remains stuck and can be seen (but not deleted) in the IMC queue ( for inbound messages awaiting conversion) of the Microsoft Exchange Server Administrator program. The file has to be removed by manually deleting it with File Manager or Windows Explorer (only after the service has been stopped).

CAUSE

One of the digest messages is a different code page. When this happens, the IMC needs to re-create the embedded message in code page 932. If code page 932 is not installed on the Microsoft Exchange server, it will fail. When this happens, two released pointers are not made NULL and they are freed again.

WORKAROUND

There only workaround is for an administrator to find the message in the Imcdata\In directory and pass this message on to the intended recipient.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange version 4.0. This problem was corrected in the latest Microsoft Exchange Server 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


KBCategory: kbusage
KBSubcategory: XFOR
Additional reference words:
Keywords : XFOR kbusage
Version : 4.00
Platform : WINDOWS


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