You receive "The Maximum Time for Delivering the Message Expired" NDR message when the maximum time for delivery has not expired (827092)
The information in this article applies to:
- Microsoft Exchange Server 5.5
SYMPTOMSWhen you send a message from one Microsoft Exchange Server 5.5 site to a second 5.5 site, you receive the following non-delivery report (NDR) message: The maximum time for delivering the message expired You receive this message although the maximum time for delivery has not expired.CAUSEThis problem may occur if the following conditions are true: - You have applied the changes that are described in the following Microsoft Knowledge Base article to the Exchange servers in the two sites:
178539 XCON: How to adjust message time-outs for the Exchange MTA
- You have set the message time-outs for the Exchange message transfer agent (MTA) to 60 minutes.
- You sent the message in the 60 minutes before the time changes to daylight saving time.
- The MTA on the destination Exchange server has been restarted, or the destination server uses a DCL X.400 MTA.
This problem occurs because the MTA does not automatically recalculate the Coordinated Universal Time (Greenwich Mean Time) offset time when the clock on an Exchange server changes because of daylight saving time (DST).
When the MTA on an Exchange server is restarted, the MTA recalculates the Coordinated Universal Time offset. If the MTA is restarted on the destination Exchange server, but the MTA is not restarted on the sending Exchange server, the time on the sending Exchange server is one hour behind the time on the destination Exchange server. Therefore, when the destination server receives the message, the maximum time for delivery has passed, and the NDR is sent. This problem also occurs if the destination mail server uses a DCL X.400 MTA that has not been restarted. The DCL MTA calculates the time change correctly without having to be restarted. Therefore, the same time difference exists between the servers, and the destination server sends an NDR after the change to DST.
Note Daylight saving time begins for most of the United States at 02:00 on the first Sunday of April. Time reverts to standard time at 02:00 on the last Sunday of October. RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem. To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. 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.
The English version of this hotfix 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
--------------------------------------------------------------
26-Aug-2003 23:59 3,369,576 Exchange5.5-kb827092-x86-enu.exe
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Modification Type: | Minor | Last Reviewed: | 10/3/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbfix kbBug kbprb kbQFE KB827092 kbAudITPRO |
---|
|