XADM: Reports That Do Not Return Content May Have Content Type of MDBEF (298000)
The information in this article applies to:
- Microsoft Exchange Server 5.5
- Microsoft Exchange Server 5.5 SP1
- Microsoft Exchange Server 5.5 SP2
- Microsoft Exchange Server 5.5 SP3
- Microsoft Exchange Server 5.5 SP4
- Microsoft Exchange 2000 Server
This article was previously published under Q298000 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. RESOLUTIONExchange 2000 ServerTo 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.5A 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: 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 |
| Emsmta.exe | 5.5.2655.1 | | X400om.dll | 5.5.2655.1 | | Mtamsg.dll | 5.5.2655.1 | | Mtaperf.dll | 5.5.2655.1 | | Ems_rid.dll | 5.5.2655.1 | | Mtacheck.exe | 5.5.2655.1 | | Dbserver.sch | N/A | | Dcprods.cat | N/A | | Infoplog.cfg | N/A | | p42.tpl | N/A | | p772.tpl | N/A | | p2.xv2 | N/A |
NOTE: Because of file dependencies, this fix requires Microsoft
Exchange Server version 5.5 Service Pack 4.
STATUSExchange 2000 ServerMicrosoft 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.5Microsoft has
confirmed that this is a problem in Microsoft Exchange Server version 5.5.
| Modification Type: | Minor | Last Reviewed: | 10/6/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbExchange2000SP2Fix kbExchange550preSP5fix kbfix KB298000 |
|---|
|