MSExchangeTransport 2020

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 indicates a message delivery failure between the Send connector on a Microsoft Exchange Server 2010 Transport server and another SMTP server. In Exchange Server 2010, the SMTPSend component is the transport component that sends messages from the Delivery Queue to other destinations. This event is triggered when the SmtpSend component cannot transfer a message that includes Originator Requested Alternate Recipient (ORAR) information to an SMTP Receive connector.

Note   ORAR information is transferred during the RCPT TO SMTP command.

This issue may occur if the SMTP Receive connector on the remote server does not support ORAR. To support ORAR, the OrarEnabled parameter must be set to True. By default, this parameter is set to False on Receive connectors. When the parameter is set to True ($true), the Receive connector advertises ORAR support by displaying the XORAR keyword in the EHLO response.

Additionally, if the ORAR information contains a long X.400 e-mail address, the LongAddressEnabled parameter must be set to True on the Receive connector. The X.400 e-mail addresses are encapsulated in SMTP e-mail addresses by using the Internet Mail Connector Encapsulated Address (IMCEA) encapsulation method. If the LongAddressEnabled parameter is False, the maximum length for a complete SMTP e-mail address is 571 characters. When the parameter is set to True, X.400 e-mail addresses may be up to 1,860 characters after IMCEA encapsulation. The Receive connector advertises support for long addresses by using the XLONGADDR keyword in the EHLO response. This parameter may be set only on Receive connectors that are configured on Hub Transport servers.

For more information, see the following topics:

• Understanding Message Classifications

• Managing Message Classifications

• Set-ReceiveConnector

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.

• Examine the ORAR address in the event description to determine its length.

• Remove, and then reinstall any installed Antispam program to determine whether the issue is resolved.

• 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. Determine whether the XORAR and/or XLONGADDR keywords are advertised.

• If the XORAR verb is not advertised, determine whether the OrarEnabledParameter is set to True on the remote SMTP server's Receive connector. To do this, run the following command from the Exchange Management Shell:

  Get-ReceiveConnector "ConnectorName" | Format-List
  

• If the ORAR information contains a long X.400 e-mail address, determine whether the LongAddressEnabled parameter is set to True on the remote SMTP server's Receive connector. To do this, run the following command from the Exchange Management Shell:

  Get-ReceiveConnector "ConnectorName" | Format-List
  

• Use the Set-ReceiveConnector cmdlet to enable ORAR and long address support on the remote SMTP Receive connector. For more information, see Set-ReceiveConnector.

• 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.