Skip to main content

How to Troubleshoot an Outbound Message Rejected by a Remote Server

This article helps a SmarterMail System Administrator identify and resolve issues where an outgoing email is rejected by the recipient's mail server. You will use SmarterMail's internal logs and the message spool to determine if the failure is due to...

This article helps a SmarterMail System Administrator identify and resolve issues where an outgoing email is rejected by the recipient's mail server. You will use SmarterMail's internal logs and the message spool to determine if the failure is due to local configuration, authentication issues, or remote server restrictions.

Before you begin

You will need:

  • System Administrator access to the SmarterMail management interface.

  • The specific email address of the sender and the recipient.

  • The specific timestamp of the failed delivery (if known).

Check the SmarterMail Spool

The SmarterMail spool contains messages that are currently waiting to be sent or have encountered a delivery issue.

  1. Log in to the SmarterMail administration interface.

  2. Navigate to Tools > Spool.

  3. Locate the message in the list. You can search by the sender's email address or the recipient's email address.

  4. View the details of the message.

  5. Check the Status and Error columns.

If the message is in the spool with an error message, the error text will indicate why the remote server rejected the message (e.g., "550 5.1.1 User Unknown" or "450 4.7.1 Timeout").

Analyze the Delivery Logs

If the message is no longer in the spool but failed to deliver, you must examine the delivery logs to see the full communication between SmarterMail and the remote server.

  1. Navigate to Tools > Logs.

  2. Select Delivery from the log type options.

  3. Filter the logs by the sender's email address or the recipient's email address.

  4. Locate the specific attempt and click on the entry to view the full log.

  5. Review the SMTP transaction. Look for the "250" or "550" response codes from the remote server.

Note: A "5xx" error code indicates a permanent failure (e.g., the email address does not exist), while a "4xx" error code indicates a temporary failure (e.g., the remote server is busy or a greylisting policy is in effect).

Identify the Cause of Rejection

Based on the information gathered from the Spool or Delivery logs, identify the specific cause:

  • Recipient Address Errors: If the log shows a "550" error regarding an "Invalid" or "Unknown" user, the recipient's email address is likely mistyped.

  • Authentication Failures: If the log shows an authentication error, verify that the SmarterMail server is correctly authenticated to send on behalf of the domain.

  • Relay/Gateway Issues: If the message is rejected because the SmarterMail server is not "authorized to relay," verify your outbound gateway settings.

  • Reputation/Blacklist Issues: If the remote server rejects the mail with a message regarding "Spam" or "Blacklist," check the outbound IP address against global RBLs.

Contact Hostek support

If you cannot identify the cause of the rejection from the logs, or if the logs do not provide a specific error code, gather the following information before contacting Hostek support:

  • The sender's email address.

  • The recipient's email address.

  • The date and time of the failed attempt.

  • A copy of the full delivery log for the specific message (available in Tools > Logs).

  • The specific error message found in the SmarterMail Spool.

Did this answer your question?