MSExchangeTransport 2005

上一次修改主题： 2011-03-19

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

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:

• 了解传输管道

• 了解传输队列

User Action

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

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

• Examine the SMTP response code in the event message description. Use this information to troubleshoot the SMTP connection.

• Log on to the remote SMTP server by using the telnet command to port 25. Use the EHLO command to return a list of extended SMTP verbs that the server supports. If the SMTP response code from the Event ID 2005 description is "421 4.4.0 Remote server response was not RFC conformant," verify that the CHUNKING verb is returned in the Telnet session.

• If the CHUNKUNG verb is not returned, determine whether a firewall issue blocks the CHUNKING traffic in your organization. To verify this issue, access the remote SMTP server from a location outside your network.

• If CHUNKING is blocked to your network, temporarily disable extended SMTP verbs on the Send connector. To do this, set the ForceHelo attribute on the Send connector to True. To do this, follow these steps:

  1. On the Hub Transport server, start the Exchange Management Shell.

  2. Run the following command to return a list of the Send connectors:

     Get-SendConnector

  3. Run the following command, replacing "EdgeSync - Default-First-Site-Name to Internet" with the name of the appropriate Send connector:

     Set-SendConnector "EdgeSync - Default-First-Site-Name to Internet" -ForceHELO $true

     Note   You cannot run this command on an EdgeSync server that is subscribed to an Active Directory site. You must run the command on a Hub Transport server.

  After you run this command, the sending server uses HELO instead of EHLO. Therefore, the sending server uses the DATA command instead of the BDAT command to send messages. After you troubleshoot any network issue that blocks CHUNKING, set the -ForceHELO attribute to $False on the Send connector. For more information about CHUNKING, see SMTP Commands and Definitions.

• 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 使用条款中指定的条款的约束。