XADM: Multipart MIME Message with TNEF Causes Store Failure (152937)
The information in this article applies to:
- Microsoft Exchange Server 5.0
This article was previously published under Q152937 SYMPTOMS
Receiving a multipart MIME message from a foreign SMTP system can cause the
Microsoft Exchange Server information store to fail with an access
violation. The Windows NT Event Viewer Application log may show the
following information:
Event ID: 4097
Source: DrWatson
Description:
The application, store.dbg, generated an application error The error
occurred on 8/27/1997 @ 13:42:45.955 The exception generated was
c0000005 at address 004727e0 (CmnBptMessage::cleanTNEF)
Specific information about the failure is contained in the "More
Information" section of this article.
CAUSE
A MIME Content-Type: application/ms-tnef bodypart was returned from a
foreign SMTP mail system in a manner that caused the information store to
fail during inbound processing.
WORKAROUND
One way to work around this issue is to prevent the sending of the MIME
Content-Type application/ms-tnef bodyparts (Rich-Text Information) to
Internet e-mail domains that do not have systems that handle it. This would
prevent the foreign system from returning ms-tnef bodyparts to a Microsoft
Exchange environment on forwarded mail.
This can be accomplished by using Microsoft Exchange Administrator program
and configuring the Microsoft Exchange Server Internet Mail Service by
performing the following steps:
- Open the Internet Mail property page.
- Under Specify Message Content by E-Mail Domain:, click the E-Mail
Domain button.
- Click Add and the Add E-Mail Domain dialog box appears.
- In the E-Mail Domain edit window, add the Internet E-Mail Domain you
do not want send Rich-Text Format to. For example, foreign.system.com.
- In the Send Attachments Using pane, click Interoperability.
- In the Send Microsoft Exchange Rich Text Formatting list, select
Never.
- Click OK until all the open dialog boxes are closed. This accepts
your changes.
For additional information about the purpose of the Content-Type:
application/ms-tnef message body, please refer to the following article in
the Microsoft Knowledge Base:
136204 XCLN: Sending Messages In Rich-Text Format
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server
version 5.0. This problem has been corrected in the latest U.S. Service
Pack for Microsoft Exchange Server version 5.0. For information on
obtaining the Service Pack, query on the following word in the Microsoft
Knowledge Base (without the spaces):
Modification Type: | Minor | Last Reviewed: | 4/28/2005 |
---|
Keywords: | kbbug kbfix kbQFE KB152937 |
---|
|