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.
Message delivery to the remote domain '<domain name>' failed. The error message is "An SMTP protocol error occurred. '. The SMTP verb which caused the error is '<smtp command>'. The response from the remote server is '<server response>'
|English: Request a translation of the event description in plain English.|
- Server response: "550 This system has been configured to reject your mail" - From a newsgroup post: "A program called Mailsweeper caused the issue; the client had added our email address to the list of banned address".
- Server response: "553 malformed address" - See ME284442.
RCPT - '550 Unable to relay for <domain name>' - the remote server does not allow SMTP relay so the message was not accepted. In certain conditions, this happens because the remote smtp server is configured to reject emails from certain servers in order to avoid spam. For example, if the IP adress of the host does not resolve to a domain name, than the server will drop the connection.
MAIL - '501 bogus mail from' - no info - it could be that the email address of the sender (mail from) is invalid (wrong format)
MAIL - '452 <email address>... DNS lookup for domain failed --- try again later' - Cause: there is no reverse name resolution for the sender domain and the remote mail server is configured to only allow mail from servers whose IP address resolve.
|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