Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XADM: You Receive a Non-Delivery Report When You Send Mail Over an X.400 Connection


View products that this article applies to.

Symptoms

When you try to send mail to a recipient over an X.400 connection, you receive a non-delivery report (NDR), and the recipient does not receive the mail. When you look in Event Viewer on your Exchange Server computer, you see the following events:

Event Type: Information
Event Source: MSExchangeIS Private
Event Category: Transport Delivering
Event ID: 2025
Description: The delivery of a message failed due to error FFFFFBFE. A non-delivery report is being sent to the message's originator



Event Type: Information
Event Source: MSExchangeMTA
Event Category: X.400 Service
Event ID: 270
Description: A permanent error has occurred with Entity /O=ORGANIZATION/OU=SITE_NAME/CN=CONFIGURATION/CN=SERVERS/CN=SERVER_NAME/CN=MICROSOFT PRIVATE MDB. Entity is a Message Object is a Normal Priority Message. Object: 06000032. Message ID: C=US;A= ;P=ORGANIZATION;L=XMX9LONIB-030318093332Z-332858 Content length: 462576, External Trace information (first 100 bytes) = 30806380618013025553000062801301200000130B436F6D6D65727A62616E6B0000318080113033303331383039333333322B303130308201016380618013025553000062801301200000130B436F6D6D65727A62616E6B000083020600000000003080, PDU dump reference 2 [MTA SUBMIT 14 74] (14)



Event Type: Warning
Event Source: MSExchangeMTA
Event Category: X.400 Service
Event ID: 290
Description: A non-delivery report (reason code transfer-failure and diagnostic code Omit any diagnostic code) is being generated for message C=US;A= ;P=ORGANIZATION;L=XMX9LONIB-030318093332Z-332858. It was originally destined for DN:/o=ORGANIZATION/ou=SITE_NAME/cn=RECIPIENTS/cn=RECIPIENT�C=DE;A=DBP;P=ORGANIZATION;O=SITE_NAME;S=Recipient;G=Recipient; (recipient number 1), and was to be redirected to . [MTA DISP:RESULT 18 136] (12)

↑ Back to the top


Cause

This problem may occur when the message transfer agent (MTA) creates custom properties that support content conversion and saves them in Transport-Neutral Encapsulation Format (TNEF). The problem occurs if the custom properties are not removed and are saved in the final message. This can increase the size of the message and trigger the JET_errRecordTooBig error.

The MTA uses the Metamorf process to correctly map MAPI message properties to the corresponding X.400 Message attributes. If Allow MS Exchange Contents is selected in the X.400 Connector, the MAPI properties that do not map directly to X.400 Message attributes are placed in an attachment to the message. If the recipient server is an Exchange Server-based computer, the contents of the attached file are directly mapped back to the corresponding MAPI properties. If the recipient server is not an Exchange Server-based computer, the end recipient receives a Winmail.dat file attachment in the message that contains the unmatched MAPI attributes.

↑ Back to the top


Resolution

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 systems that are experiencing this specific problem.

To resolve this problem, 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Component: MTA

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version            Size    File name
   --------------------------------------------------------------
   19-May-2003  20:30  5.5.2657.43       491,280  Mdbmsg.dll       
   19-May-2003  20:33  5.5.2657.43     2,630,416  Store.exe                           

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

↑ Back to the top


Keywords: KB819851, kbqfe, kbbug, kbfix, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 819851
Revision : 4
Created on : 10/26/2006
Published on : 10/26/2006
Exists online : False
Views : 281