If your emails are being rejected by a remote mail server, this article provides the steps to identify the cause and resolve the issue. This guide is intended for Server Administrators using WHM to manage the mail server environment.
Before you begin
You will need:
Root access to the WHM interface.
The specific email address, the recipient's email address, and the timestamp of the failed delivery.
Access to the Exim mail queue.
Check the Exim mail queue
To determine if an email is currently stuck or has been rejected, you must examine the mail queue.
Log in to WHM.
Navigate to Email > Mail Queue Manager.
Use the search filters to locate the specific message using the sender or recipient email address.
Review the status of the message. If the message is in the queue, the "Status" or "Log" section will often contain the specific error code from the remote server (e.g., "Relay Access Denied" or "550 Message rejected").
Identify the reason for rejection
If the mail is in the queue and shows a failure, the specific error message from the remote server will indicate the cause.
If the error is a "Greylisting" delay: The remote server is intentionally delaying the first delivery. If the message remains in the queue for more than 10 minutes, it may be blocked by a firewall or a local configuration.
If the error is a "DNS" or "SPF/DKIM" failure: The remote server is rejecting the mail because your domain's authentication records are missing or incorrect.
If the error is a "Blacklist" (RBL) block: The remote server has flagged your server's IP address as a source of spam.
Resolve common rejection issues
Depending on the error identified in the previous step, perform the following actions:
If the IP is on a blacklist
Identify the specific blacklist from the error message (e.g., Spamhaus, Barracuda).
Check if your IP is listed on that specific list.
If your IP is listed and you are not sending spam, request a delisting from the provider.
If the IP is frequently blacklisted, consider a dedicated IP or a mail relay service.
If SPF or DKIM records are failing
Log in to WHM.
Navigate to DNS Functions > DNS Zone Editor.
Select the domain and ensure the SPF record includes the server's IP or the authorized sending domain.
Verify that the DKIM keys are correctly generated and published in the DNS zone.
If the message is "Frozen"
A message may become "frozen" if it cannot be delivered and the system stops attempting to send it.
Navigate to Email > Mail Queue Manager.
Locate the frozen message.
Select the message and click Retry to attempt delivery again.
Retry delivery for a message
If you have corrected a configuration issue (such as updating a DNS record or resolving a temporary block), you can manually force the system to attempt delivery again.
Navigate to Email > Mail Queue Manager.
Locate the specific message in the queue.
Select the message and click Retry.
If the email is still not delivering
If the email remains in the queue after a retry or continues to be rejected with the same error, the issue may be with the recipient's mail server or a persistent block on your IP.
Collect the full "Log" output from the Mail Queue Manager.
Note the specific error code and the remote server's IP address.
Contact Hostek support and provide the specific message ID, the recipient's email, and the full error log to investigate further.
