XCON: MTA Deferred Delivery Message NDRs "Maximum Time for Deliverying the Message Has Expired

ID: Q214682

The information in this article applies to:

Microsoft Exchange Server, version 5.5

SYMPTOMS

The following Non-Delivery Report (NDR) may be received when sending messages with a deferred delivery time after the message timeout:

From: System Administrator
To: 'x400 to user1'
Sent: Monday, November 23, 1998 5:00 PM
Subject: Undeliverable: test 2 on friday
Your message did not reach some or all of the intended recipients.

Subject: test 2 on friday
Sent: 11/13/98 9:21 AM

The following recipient(s) could not be reached:

'x400 to user1' on 11/23/98 5:00 PM
The maximum time for delivering the message expired
MSEXCH:MSExchangeMTA:Site:Server

The NDR is received on the deferred delivery date, not immediately upon sending.

CAUSE

The Message Transfer Agent (MTA) returns the message if the deferred delivery date is after the message timeout. The default message timeout period is seven days. When the deferred delivery date arrives, the MTA checks the message timeout value, and displays the NDR for this message based on that date, instead of delivering the message.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it 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://www.microsoft.com/support/supportnet/overview/overview.asp

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

Component: Message Transfer Agent

File name	Version
Dbserver.sch	5.5.2534
Dcprods.cat	5.5.2534
Ems_rid.dll	5.5.2534
Emsmta.exe	5.5.2534
Info4log.cfg	5.5.2534
Infoblog.cfg	5.5.2534
Infodlog.cfg	5.5.2534
Infollog.cfg	5.5.2534
Infotlog.cfg	5.5.2534
Mtacheck.exe	5.5.2534
Mtamsg.dll	5.5.2534
P2.xv2	5.5.2534
X400om.dll	5.5.2534
X400omv1.dll	5.5.2534

Please note that this fix must be applied to all Microsoft Exchange servers in the message path, as each MTA on each server evaluates the deferred delivery time and message time-out.

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

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

Q154871 Determining If You Are Eligible for No-Charge Technical Support

STATUS

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


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

Last Reviewed: August 3, 1999