MSExchangeTransport 1010

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 Error event indicates that the Microsoft Exchange Transport service SMTP Receive component rejected an SMTP message from a particular user.

The Microsoft Exchange Transport service controls the sending and receiving of messages in Microsoft Exchange Server 2010. The Exchange 2010 transport pipeline uses the SMTP Receive component to validate the message content before the message can be submitted to the Submission queue. The SMTP Receive component applies a series of receive events and, if configured, antivirus and anti-spam events to validate the message. Additionally, the SMTP Receive component contacts the Active Directory directory service to validate users who submit messages for delivery. This includes connections that are used to distribute messages from internal users among servers.

This event represents an authentication error for a user who tries to submit an SMTP message. This event could be logged in one of the following scenarios:

• The user does not have sufficient rights to Send As a particular user.

• The Default connector does not have the Accept any Sender permission set for Authenticated users.

• The network settings on the Default receive connector do not allow include the IP address range of an IMAP4 or POP3 client that tries to submit messages.

For more information, see the following topics:

• Understanding Transport Permissions Architecture

• Understanding Receive Connectors

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.

• Review the Operations Console in Operations Manager for detailed information about the cause of this problem. For more information, see the "Introduction" section in this article.

• Enable diagnostics logging on the affected receive connector. To do this, follow these steps:

  1. Run the following commands from the Exchange Management shell:

     Set-ReceiveConnector "name of connector" -ProtocolLoggingLevel Verbose

     Set-TransportServer Exchange01 -ConnectivityLogEnabled $true

     Set-TransportServer "Exchange01" -IntraOrgProtocolLoggingLevel Verbose

  2. After Event ID 1026 is logged, examine the SmtpReceive log file. By default, this file is located in the following directory:

     %ProgramFiles%\Microsoft\Exchange Server\V14\TransportRoles\Logs\ProtocolLog\SmtpReceive

• Examine the authentication settings on the receive connector. To do this, run the following commands from the Exchange Management Shell:

  Get-ReceiveConnector "Exchange01\default Exchange01" | fl *

  Get-ReceiveConnector "Exchange01\client Exchange01" | fl *

• Assign the user Send As permissions to the mailbox. To do this, follow these steps:

  1. Start the Exchange Management Console.

  2. Expand Recipient Configuration, and then click Mailbox.

  3. Click the affected mailbox, and then click Manage Send As Permission in the Actions pane.

  4. Click Add, and then add the user to the mailbox.

  You can also run the following command from the Exchange Management Shell to assign the user Send As permissions to the mailbox. To do this, run the following command:

  Add-ADPermission -Identity 'CN=User1,CN=Users,DC=tailspintoys,DC=com' -User 'TAILSPINTOYS\User2' -ExtendedRights 'Send-As'

  In this command, replace User1 with the name of the affected mailbox. Replace User2 with the name of the user who should have Send-As permissions for the affected mailbox.

  For more information, see Manage Send As Permissions for a Mailbox.

• Use the ADSI Edit tool to verify the permission settings for the Authenticated Users group. To do this, follow these steps:

  1. Click Start, click Run, type adsiedit.msc, and then click OK.

  2. Connect to the Configuration container.

  3. Expand the following path:

  4. CN=Configuration,DC=tailspintoys,DC=com

  5. CN=Services

  6. CN=Microsoft Exchange

  7. CN=<Organization>

  8. CN=Administrative Groups

  9. CN=Exchange Administrative Group

  10. CN=Servers

  11. CN=<ServerName>

  12. CN=Protocols

  13. CN=SMTP Receive Connectors

  • In the details pane, right-click the appropriate connector (for example, CN=Default <ServerName>), and then click Properties.
  1. Click the Security tab, click Authenticated Users, and then click to select the Accept any Sender and Accept Authoritative Domain Send check boxes in the Allow column.

• Use the Exchange Management Console to verify the network settings on the Default receive connector. To do this, follow these steps:

  1. Start the Exchange Management Console.

  2. Expand Server Configuration, click Hub Transport, and then click Receive Connectors.

  3. Right-click the Default <ServerName> connector, and then click Properties.

  4. Click the Network tab, and then verify that the network range under Use these local IP addresses to receive mail includes the IP address of the affected client computer. By default, the following IP address ranges are listed:

  5. All Available IPv6

  6. All Available IPv4

  • 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 Understanding Transport Pipeline.

• To obtain transport architecture diagrams, see the Exchange Server Team blog article, 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.