XCON: MTA Unable to Deliver NDR When Message Fails Because of Size Restriction

ID: Q196663

The information in this article applies to:

Microsoft Exchange Server, version 5.5

SYMPTOMS

Microsoft Exchange Server 5.5 does not deliver the non-delivery report (NDR) to the original recipient if a message encounters a message size limit on another server's message transfer agent (MTA) in certain circumstances.

CAUSE

The receiving server will generate a NDR for the message and send the report to the sending server, which will attempt to reroute the message after triggering the routing restricted value, eventually failing, and is then unable to complete delivery.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 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 on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/support/supportnet/default.asp

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

Component: Message Transfer Agent (MTA)


   File Name      Version
   -------------------------
   Dbserver.sch   5.5.2500.0
   Dcprods.cat    5.5.2500.0
   Ems_rid.dll    5.5.2500.0
   Emsmta.exe     5.5.2500.0
   Info4log.cfg   5.5.2500.0
   Infodlog.cfg   5.5.2500.0
   Infollog.cfg   5.5.2500.0
   Infotlog.cfg   5.5.2500.0
   Mtacheck.exe   5.5.2500.0
   Mtamsg.dll     5.5.2500.0
   P2.xv2         5.5.2500.0
   X400om.dll     5.5.2500.0
   X400omv1.dll   5.5.2500.0

NOTE: If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If Your Product Is Eligible for No-Charge Technical Support

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.

Additional query words: rerouting failing


Keywords          : 
Version           : WinNT:5.5
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: August 3, 1999