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.1.0 was generated for recipient <recipient>.
Cause: This is categorizer failure caused by a bad address.
For more information, click http://www.microsoft.com/contentredirect.asp.
Solution: Either the recipient address is incorrectly formatted or the categorizer was not able to properly resolve the recipient. Checking the recipient address and re-sending the message is the first step to resolving this error.
|English: Request a translation of the event description in plain English.|
This event occurs when you enable the envelope journaling feature in Microsoft Exchange Server 2003 Service Pack 2 because the envelope journaling feature uses the domain controller instead of the global catalog server to resolve the journaling mailbox GUID to the domain name of the user account. This process occurs when the e-mail message is re-categorized and then is journaled again. See ME925379 for a hotfix applicable to Microsoft Exchange Server 2003.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated