MSExchangeTransport 2007

上一次修改主题： 2012-09-19

本文对特定 Exchange 事件进行了说明并提供了可能的解决方案。如果您在此处未找到所需内容，请尝试在 Exchange 2010 帮助中进行搜索。

Details

Explanation

This event may indicate 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. This event describes a scenario in which the SmtpSend component has started a new session to retry delivery after previously being unable to deliver the message.

This issue may occur if an issue affects the destination domain. For example, this issue may occur if a DNS-related issue hinders obtaining the MX record for the domain or a networking issue.

For more information, see the following topics:

• 了解传输管道

• 了解传输队列

User Action

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

• 有关相关事件，请查看 Exchange 2010 服务器上的应用程序日志和系统日志。例如，在此事件之前和之后发生的事件可能会提供有关导致出现此错误的根本原因的详细信息。

• 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 the destination domain has an accessible MX record. To do this, use a third-party program such as www.mxtoolbox.com.

• Verify that you can resolve the MX record for the affected domain. To do this, use any of the following methods:

  • Examine the hosts file on the Transport server to determine whether any incorrect entries exist.

  • Determine whether any firewall rules are configured that may block DNS queries for specific domains.

  • Log on to a client computer that is pointed to your internal DNS servers. Then, use the Nslookup command to determine whether you can resolve the external domain and the MX record for that domain. For more information about how to use the Nslookup command, see Microsoft Knowledge Base article 200525, Using NSlookup.exe.

  • If you cannot resolve the MX record from a client that is pointed to the internal DNS servers, point the same client computer to an external DNS server, and then repeat the Nslookup requests. For example, point the client computer to 4.2.2.2 for DNS queries.

• 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

• 使用自助支持选项、协助支持选项及其他资源来解决您的问题。您可以从 Exchange Server 解决方案中心访问这些资源。在该页中，单击导航窗格中的“自助支持选项”可使用自助服务选项。自助服务选项包括搜索 Microsoft 知识库、在 Exchange Server 论坛上发布问题及其他方法。或者，您可以在导航窗格中单击“协助支持选项”来联系 Microsoft 支持专业人员。由于您的组织可能已有直接与 Microsoft 产品支持服务联系的特定流程，因此，请您务必先查看您组织的准则。

For more information about the transport pipeline in Exchange 2010, see 了解传输管道.

To obtain transport architecture diagrams, see the Exchange Server Team blog article, Exchange 2010 Transport Architecture Diagrams Available for Download.

每个博客的内容及其 URL 如有更改，恕不另行通知。每个博客中的内容均“原样”提供，既不承担任何担保，也未赋予任何权利。对包含的脚本示例或代码的使用受 Microsoft 使用条款中指定的条款的约束。