XFOR: IMC NDRs Messages Stating the Message was Malformed

 Last reviewed: November 7, 1997
Article ID: Q164315
The information in this article applies to:
  • Microsoft Exchange Windows 3.x client, versions 4.0 and 5.0
  • Microsoft Exchange Windows 95 client, versions 4.0 and 5.0
  • Microsoft Exchange Windows NT client, versions 4.0 and 5.0
  • Microsoft Exchange Server, versions 4.0 and 5.0

SUMMARY

Some users can not send mail from Microsoft Exchange Server out the Internet Mail Connector (IMC) or Internet Mail Service (IMS). These users are not notified of the message failure and will be under the impression that the mail was sent successfully. However, the administrator of the IMC or IMS will receive a Non-Delivery Report (NDR) message.

MORE INFORMATION

When the administrator opens the NDR they will notice the following subject line and body content: 

   Subject: Notification: Outbound Mail Failure - Message could not be
            processed.

   Body: The mail message was not sent - The message was Malformed.

   The message that caused this notification was:

   <copy of message>2
Upon opening the copy of the message, the following error will be displayed. 

   The message could not be displayed the object could not be opened
   Launching the default form instead.
The default form will display a new message with an UNKNOWN entry in the From field. Another copy of the message will be in the body and may be opened successfully. This message will show the original message. If this message has a True Type font that comes with Office 97 the IMC or IMS may fail reading this font. The IMC's or IMS's failure is related to a fix in Windows NT Server 3.51 Service Pack 5 (SP5). A known font that causes this problem is Monotype Corsiva.

For more information about this problem, please see the follwing articles in the Microsoft Knowledge Base: 

   ARTICLE-ID: Q152051
   TITLE: IBM Gothic Box Font Appears Garbled

   ARTICLE-ID: Q142798
   TITLE: AutoCorrect Incorrectly Expands Words in a Table

   ARTICLE-ID: Q128531
   TITLE: README.TXT: Windows NT Version 3.51 U.S. Service Pack
To overcome this problem, upgrade Windows NT 3.51 to SP5 or NT 4.0 and reapply the most recent Microsoft Exchange Service Pack.

Additional query words:
Keywords : XFOR kberrmsg
Version : 4.0 5.0
Platform : WINDOWS
Issue type : kberrmsg kbtshoot
Solution Type : kbworkaround

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