Export (0) Print
Expand All
Expand Minimize

A message was rejected by the remote server

 

Topic Last Modified: 2007-12-06

The Microsoft Exchange Server 2007 Management Pack for Operations Manager monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.

To learn more about this alert, if you are using Microsoft Operations Manager 2005, do one or more of the following:

  • From the Operator Console, select this alert, and then click the Properties tab. Review the description of the alert that includes the variables specific to your environment.

  • From the Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description. Review the events that have been logged that meet the criteria of this Operations Manager alert.

To learn more about this alert, if you are using System Center Operations Manager 2007, do one or more of the following:

  • From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.

  • From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the events that have been logged that meet the criteria of this Operations Manager alert.

 

Product Name

Exchange

Product Version

8.0 (Exchange Server 2007)

Event ID

8010

Event Source

MSExchangeTransport

Alert Type

Critical Error

MOM Rule Path

Microsoft Exchange Server/Exchange 2007/Common Components/Hub Transport and Edge Transport/Transport

MOM Rule Name

A message was rejected by the remote server. This message will be deferred and retried because it was marked for retry if rejected.

This Error event indicates that at least one journal message could not be delivered to a journal report mailbox.

When a journal message is rejected for any reason, the transport process intercepts the non-delivery report (NDR) process and tries to transfer the message again in retry mode. Journal messages do not cause an NDR to be sent.

Note   If you do not resolve this error, it is very possible that messages will build in the queues. Eventually the server may stop processing e-mail at all.

To resolve this error, determine the reason that a journal message is rejected. Then correct the issue. Follow these steps:

  • Run the Exchange Management Shell Get-Message cmdlet with the IncludeRecipientInfo parameter. The cmdlet should return the error message that explains why the message was rejected.

  • Fix the issue based on the information in the error specified in the Exchange Management Shell. After you fix the issue, message delivery should continue.

For more information, see Get-Message.

To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.

To review Exchange 2007 event message articles that may not be represented by Exchange 2007 alerts, see the Events and Errors Message Center.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft