An e-mail message remains in the local SMTP queue when the first SMTP connection fails in Exchange Server 2003

When you try to send an e-mail message through the Simple Mail Transfer Protocol (SMTP) service on a server that is running Microsoft Exchange Server 2003, the SMTP service may try to connect to the remote server whose IP address is included in the lowest-cost mail exchanger (MX) resource record. If the connection to the remote server fails, the SMTP service tries to connect to another remote server whose IP address in included in a higher cost MX resource record. However, if the remote SMTP server responds with a "220 Service is ready" message, the SMTP service on the local server sends a Quit command to close the connection.

When this problem occurs, the message remains in the local SMTP queue in a Retry state. Then, the SMTP service tries to resend the message. However, the same problem occurs again. Therefore, the message remains in the local SMTP queue.

Note This issue occurs when Exchange Server 2003 is running on a Microsoft Windows Server 2003-based computer.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the SMTP service after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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.

Windows Server 2003, 32-bit editions (x86)Windows Server 2003, 64-bit editions (IA-64)

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

After you apply this hotfix or install Windows Server 2003 Service Pack 1, the problem that is described in the "Symptoms" section no longer occurs. When the lowest-cost SMTP server not available, the SMTP service sends the message to the SMTP server whose IP address is included in the secondary MX resource record.