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. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
A non-delivery report with a status code of 5.4.4 was generated for recipient <user>@<domain> (Message-ID <ID>).
Cause: Exchange cannot determine a route for this message or no next hop can be determined. A routing group topology does not have a routing group connector set up between the routing groups. Mail destined to a routing group that does not have a routing group connector to connect it to other groups cannot be sent.
Solution: Add or configure your RGC between RGs.
|English: Request a translation of the event description in plain English.|
Mohammed Athif Khaleel
Numeric Code: 5.4.4 is due to "No route to message next hop not found". For more information see ME284204.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
Send comments or solutions
- Notify me when updated