MSExchangeTransport 2004

This article provides an explanation and possible resolutions for a specific Exchange event. If you don't find what you’re looking for here, try searching Exchange 2010 Help.

Details

Explanation

This event describes a message delivery failure between the Send connector on a Microsoft Exchange Server 2010 Transport server and another SMTP server. The SMTPSend component is the transport component that sends messages from the Delivery Queue to other destinations. In this event, the SmtpSend component received an SMTP acknowledgement message that the message was not delivered successfully.

For more information, see the following topics.

• Understanding Transport Pipeline

• Understanding Transport Queues

User Action

To troubleshoot this issue, do one or more of the following:

• Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.

• Temporarily disable any e-mail antivirus program that may be running on the destination server to determine whether the issue is caused by a third-party program.

• Determine whether the following conditions are true:

  • The destination server is subscribed to a block list provider

  • The domain or IP address from which the Transport server sends the message is listed on the block list

  You can use third-party tools such as www.mxtoolbox.com to determine whether a domain or IP address is listed on one or more block lists.

• Determine whether a message size restriction on the destination server is configured to block the affected messages.

• Determine whether a third-party disclaimer program is running on the Transport server. In some cases, a disclaimer program may try to add a disclaimer as an attachment, and this can corrupt the message.

• Use a program such as network monitor to trace the network connection. Determine whether a network issue exists in which the server keeps the connection open to the destination server. In this scenario, the destination server may disconnect the connection and return a 421 4.2.2 Error: timeout exceeded result. In this scenario, examine networking components such as firewalls or routers that are placed between the Transport server and the destination server.

• You may want to increase diagnostics logging to log the components in the transport pipeline. To increase diagnostics logging for the Transport components, follow these steps:

  1. In the Exchange Server 2010 Management Console, expand Server Configuration, and then click Hub Transport.

     Note   For an Edge Transport server, click Edge Transport.

  2. In the Actions pane, click Manage Diagnostic Logging Properties for the appropriate server.

  3. Expand MSExchangeTransport.

  4. Click the following components, and then click Expert, then click Configure for each component:

  • Smtpreceive

  • Smtpsend

  • DSN

  • Components

  • Remote Delivery

  • Categorizer

• Resolve your issue by using self-support options, assisted support options, and other resources. You can access these resources from the Exchange Server Solutions Center. From this page, click Self-Support Options in the navigation pane to use self-help options. Self-help options include searching the Microsoft Knowledge Base, posting a question at the Exchange Server forums, and other methods. Alternatively, in the navigation pane, you can click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Product Support Services, be sure to review your organization's guidelines first.

For more information about the transport pipeline in Exchange 2010, see the following topics:

• Understanding Transport Pipeline

• Exchange 2010 Transport Architecture Diagrams Available for Download

The content of each blog and its URL are subject to change without notice. The content within each blog is provided "AS IS" with no warranties, and confers no rights. Use of included script samples or code is subject to the terms specified in the Microsoft Terms of Use.