If an incoming email is rejected by the Exim mail server, it is typically due to a security filter, a configuration mismatch, or a reputation issue with the sending server. This guide helps a WHM Server Administrator identify and resolve the specific cause of the rejection.
Before you begin
You will need:
Root access to the server via WHM.
The specific email headers or the "Mail Delivery Report" for the failed message.
The sender's email address and the receiving email address.
Check the Exim Mail Queue
To determine if the message is currently stuck in the queue or was rejected immediately, you must examine the mail queue.
Log in to WHM.
Navigate to Email > Mail Queue Manager.
Search for the recipient's email address or the sender's email address.
If the message is found, click View to see the status.
If the message is not in the queue, it was likely rejected immediately by the Exim filter and was not accepted by the server.
Trace the email delivery
To find the specific reason for a rejection, you must examine the mail logs.
In WHM, navigate to Email > Mail Delivery Report.
Enter the recipient's email address and click Search.
Review the results to see if the system identifies a specific failure reason (e.g., "Rejected by Exim" or "Relay Access Denied").
If the internal report is insufficient, you must check the raw mail logs:
Access the server via SSH or use the Terminal tool in WHM.
View the mail log using the following command:
tail -n 100 /var/log/exim_mainlog`
Look for the recipient's email address or the sender's IP address in the log.
Identify the specific error code or message provided by Exim.
Identify the cause of the rejection
Based on the logs, identify the specific reason for the failure:
If the log shows a "Greylisting" delay: The email is not rejected, but held for a period to verify the sender. This is a standard security feature.
If the log shows a "Spam Filter" or "RBL" rejection: The sender's IP address has been flagged as a source of spam or is on a blocklist.
If the log shows "Relay Access Denied": The sending server is attempting to route mail through your server for a domain it does not own.
If the log shows "Local Mailbox Full": The recipient's mailbox has exceeded its allocated disk quota.
Resolve the issue
Depending on the cause identified in the previous step, perform the following actions:
To bypass a Greylisting delay: If you have a frequent partner who is being delayed, you can disable Greylisting for that specific domain.
Navigate to Email > Mail Delivery Reports.
Identify the domain and adjust the settings in the Mail Delivery Manager or via the Exim Configuration Manager.
To resolve an RBL or Spam Filter rejection:
Identify the specific RBL that blocked the sender.
Navigate to Email > Mailer Configuration > Exim Configuration Manager.
Locate the Exim Configuration Manager section.
Add the sender's IP address to the Exim RBL Allowlist if the sender is a known, trusted source.
To resolve a "Mailbox Full" error:
Navigate to WHM > List Accounts.
Select the account and click Modify.
Increase the Disk Quota or contact the account owner to clear space.
Contact Hostek support
If you cannot identify the specific reason for the rejection in the exim_mainlog or if the email is being rejected despite being on the allowlist, contact Hostek support. Provide the following information:
The recipient's email address.
The sender's email address.
The specific timestamp of the failed delivery.
A copy of the full mail headers from the failed delivery.
