XADM: Reports That Do Not Return Content May Have Content Type of MDBEF

Article translations Article translations
Article ID: 298000 - View products that this article applies to.
This article was previously published under Q298000
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SYMPTOMS

The Exchange Server message transfer agent (MTA) may generate a delivery report (DR) or non-delivery report (NDR) with a content type that is set to an external value (2A 86 48 86 F7 14 05 01), which is Messaging Database Encoding Format (MDBEF). This can cause problems for non-Exchange Server MTAs that do not recognize the value.

CAUSE

This problem can occur if an MTA does not set the Return-of-Content-Requested bit on the original message. Exchange Server receives the message over the X.400 Connector, converts the P22 content to MDBEF, and delivers the content (or does not deliver it). The Exchange Server MTA then generates the report and does not add the content, but does set the content type to MDBEF. This problem does not normally occur between Exchange Server MTAs because Exchange Server MTAs always set the Return-of-Content-Requested bit on messages.

RESOLUTION

Exchange 2000 Server

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack

Exchange Server 5.5

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Exchange Server 5.5 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

Component: MTA

Collapse this tableExpand this table
File nameVersion
Emsmta.exe5.5.2655.1
X400om.dll5.5.2655.1
Mtamsg.dll5.5.2655.1
Mtaperf.dll5.5.2655.1
Ems_rid.dll5.5.2655.1
Mtacheck.exe5.5.2655.1
Dbserver.schN/A
Dcprods.catN/A
Infoplog.cfgN/A
p42.tplN/A
p772.tplN/A
p2.xv2N/A

NOTE: Because of file dependencies, this fix requires Microsoft Exchange Server version 5.5 Service Pack 4.

STATUS

Exchange 2000 Server

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.

Exchange Server 5.5

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5.

Properties

Article ID: 298000 - Last Review: October 23, 2013 - Revision: 4.5
APPLIES TO
  • Microsoft Exchange Server 5.5 Standard Edition
  • Microsoft Exchange Server 5.5 Service Pack 1
  • Microsoft Exchange Server 5.5 Service Pack 2
  • Microsoft Exchange Server 5.5 Service Pack 3
  • Microsoft Exchange Server 5.5 Service Pack 4
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbexchange2000sp2fix kbexchange550presp5fix kbfix KB298000

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com