MSExchangeTransport 1039

 

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

Product Name

Exchange

Product Version

14.0

Event ID

1039

Event Source

MSExchangeTransport

Category

SmtpReceive

Symbolic Name

SmtpReceiveProhibitSendQuotaDeniedTempAuthFailure

Message Text

SMTP rejected a message from '%1' on '%2' connector. The user was authenticated as '%3'. The Active Directory lookup returned the following error: %4

Explanation

This Error event indicates that a problem affects the validation of the e-mail address of a sender who was submitting a message to the SMTP Receive component. The Active Directory directory service lookup to authenticate the sender returned the specified validation errors. This event indicates that a problem may exist that prevents the Microsoft Exchange Transport service (MSExchangeTranspore.exe) from enforcing SMTP message submission quotas for the 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 controls message sending when a user's mailbox limit has been exceeded. This includes message submissions that use SMTP.

In this scenario, the SMTP Receive component performs a protocol-level check to verify that users do not submit messages by using the SMTP protocol if they have exceeded their message limits To perform this check, the SMTP Receive component must contact Active Directory. If the SMTP Receive component is unable to contact Active Directory to enforce the submission quota for the user, the SMTP Receive component rejects the message.

For more information, see the following topics.

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.

  • 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

  • You may have to enable tracing for ActiveManagerClientTracer. Contact Microsoft Product Support Services to help enable tracing. For more information about how to contact Microsoft Support, see https://support.microsoft.com/oas/default.aspx?gprid=13965&st=1.

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