When EventReporter is configured to send email message, several SMTP error codes might happen while connecting to the mail server. These are:
| Error | Cause | Suggested Action |
| -1 | EventReporter could not at all connect to the mail server. | Check that the mail server’s IP address or host name is correctly configured. Check that the port used is correctly configured (port 25 is a good bet if in doubt). |
| -2 | Mail server sent an unsuccessful reply during session setup (HELO). | Make sure your mail server is correctly configured to accept mails from the system EventReporter is running on. This error probably is the result of a mail server locked-down to prevent SPAM and/or other unauthorized use. Please check with you mail server administrator – there might be additional diagnostic available in the mail server logs. |
| -3 | Mail server sent an unsuccessful reply during session setup (MAIL FROM). The sender email address was not accepted. | Make sure that the sender email address configured in EventReport is correct. Specifically, ensure that it is present and has valid format (for example, does not contain spaces in it).This error could also indicate a permission issue. If in doubt, please check with you mail server administrator – there might be additional diagnostic available in the mail server logs. |
| -4 | Mail server sent an unsuccessful reply during session setup (RCPT TO). The recipient email address was not accepted. | Make sure that the recipient email address configured in EventReport is correct. Specifically, ensure that it is present and has valid format (for example, does not contain spaces in it).This error could also indicate a permission issue. Most specifically, it could result in a mail server being locked-down to prevent SPAM and/or other unauthorized use. If in doubt, please check with you mail server administrator – there might be additional diagnostic available in the mail server logs.
|
| -5 | Not currently assigned. | |
| -6 | Error during message transmittal (DATA). | This most probably is the result of a broken connection. If so, it should be self-healing as EventReporter retries on the next iteration. If this problem persists, please contact your mail system administrator for assistance. Most probably there is additional diagnostic information available in the mail server logs. In rare cases, we have seen this to be a result of a locked-down mail server. In such cases, please work with your mail system administrator to see what configuration settings need to be changed. |
SMTP Error Codes