If an inbound email is rejected by SmarterMail, it is typically due to a security policy, a configuration mismatch, or a reputation issue with the sending server. As a System Administrator, you can identify the specific cause of the rejection by examining the SmarterMail logs and the mail server's transport logs.
Before you begin
You will need:
System Administrator access to the SmarterMail management interface.
Access to the server's command line or a management tool to view mail transport logs.
The specific email address of the rejected message and, if possible, the sender's email address.
Check the SmarterMail Delivery Logs
The SmarterMail delivery logs provide the first indication of whether a message was accepted by the SmarterMail application but failed during a specific internal process.
Log in to the SmarterMail administration interface.
Navigate to Tools > Log Viewer.
Select Delivery from the log type options.
Use the search or filter tools to locate the recipient's email address or the sender's email address.
Review the log entry for the specific message.
Note: If the message appears in the Delivery log with a "Rejected" or "Failed" status, the log will often include a specific error code or reason (e.g., "SPF_FAIL", "REJECTED_BY_FILTER", or "MAX_SIZE_EXCEEDED").
Check the SmarterMail SMTP Logs
If the message does not appear in the Delivery logs, it may have been rejected by the mail server before it reached the SmarterMail application.
Navigate to Tools > Log Viewer.
Select SMTP from the log type options.
Search for the sender's email address or the recipient's email address.
Examine the transaction for the specific message.
Note: SMTP logs will show the "handshake" between the sending server and your server. Look for the specific SMTP response code (e.g., 550) and the accompanying text, which describes why the server refused the connection.
Check the System Event Log
If the issue is related to a system-wide configuration or a service-level rejection, check the System Events.
Navigate to Tools > System Events.
Look for entries timestamped at the time the message was sent.
Identify any errors related to "Mail," "SMTP," or "Security."
Identify the specific rejection cause
Based on the logs above, identify the common causes of inbound rejections:
SPF/DKIM/DMARC Failures: If the logs indicate a failure in these protocols, the sending server may have rejected the mail because the sender's DNS records do not authorize the sending IP.
Size Limits: If the log indicates a "Message Too Large" error, the email exceeds the limit defined in Tools > Mail Settings.
Blacklisted IP: If the SMTP log shows a rejection from the local server's firewall or a security module, the sender's IP may be blocked.
Spam Filtering: If the message is caught by a local filter, it may be moved to a quarantine or rejected based on the rules in Tools > Spam Settings.
Confirm the result
The specific reason for the rejection (e.g., SPF failure, size limit, or blacklisted IP) is identified in the logs.
You can determine if the issue is with the sender's configuration or your local SmarterMail configuration.
If the message is not found in any logs
If the message does not appear in the SmarterMail Delivery or SMTP logs, the email likely never reached your server.
Verify DNS Records: Ensure your MX records correctly point to your server's IP address.
Check Firewall Rules: Ensure port 25 (or your configured inbound port) is open and accepting traffic from the sender's IP.
Check Upstream Provider: If you use a third-party gateway or a hosted service, contact that provider to see if they are dropping the mail before it reaches your server.
Contact Hostek support
If you have identified the error in the logs but are unsure how to adjust the SmarterMail configuration to allow the message, contact Hostek support. Provide the following information:
The recipient and sender email addresses.
The specific timestamp of the failed delivery.
A copy of the relevant entry from the Delivery or SMTP logs.
