Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 3005 Source: MSExchangeTransport

Level
Description
A non-delivery report with a status code of 4.4.6 was generated for recipient rfc822;<e-mail address>(Message-ID  <A1E313382664EE489C9C30FC92B826F95B8E@server.mydomain>).  
Cause: The maximum hop count was exceeded for this message. This non-delivery report can also be caused if a looping condition exists between sending and receiving servers that are not in the same Exchange organization. In this situation the message bounces back and forth until the hop count is exceeded. A configuration error in the e-mail system can also cause the message to bounce between two servers or to be forwarded between two recipients.
Solution: The maximum hop count is a property set on each virtual server and you can manually override it. The default maximum hop count is 15. Also check for any situations that might cause loops between servers.
Comments
 
As per Microsoft: "This event can be logged if a looping condition exists between sending and receiving servers that are not in the same Exchange organization". See MSEX2K3DB for information about this event.
The message is queued in "Messages queued for deferred delivery" and ME823489 suggests that there is and SMTP error.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...