EraHost – Free Domain, Cheap Hosting!

› Hosting & servers › "Retry Timeout Exceeded" in cPanel: What It Means and How to Fix It

"Retry Timeout Exceeded" in cPanel: What It Means and How to Fix It

4 min read

23.01.2026

Common Causes of the Error

Recipient Server Unavailable:
- The recipient's mail server is down or temporarily unreachable.
DNS Issues:
- Invalid or missing MX records for the recipient's domain.
Greylisting:
- The recipient's server temporarily rejects emails as part of its anti-spam measures.
Network Connectivity Problems:
- Connection issues between your server and the recipient's mail server.
Firewall or Port Blocking:
- Firewalls or network rules blocking outgoing SMTP connections.
Incorrect cPanel Server Configuration:
- Issues with the Exim mail server or DNS configuration on the cPanel server.
IP Blacklists:
- Your server's IP address is on a blacklist, preventing email delivery.

Troubleshooting and Resolution Steps

Verify DNS Records

Ensure the recipient's domain has valid and properly configured MX records.

cPanel Retry Timeout Exceeded — Retry timeout exceeded — Exim gave up after 7 days; verify why.

For closely related mail-queue / deliverability topics, see Domain Exceeded Max Defers and Failures (5), Domain Exceeded Max Defers and Failures (55), Exim Syntax Errors, and Email Rate Limited.

Check MX Records:

Use a tool like MXToolbox to verify the recipient's MX records.

Note: If the recipient's domain has no valid MX records, email delivery will fail.

Check Email Logs

cPanel email logs can provide detailed information about the error.

Access Logs:

Log into your server via SSH (if you have root access).
Check Exim logs for email delivery errors:
```
tail -f /var/log/exim_mainlog
```

Look for the recipient domain or email address in the logs to identify the specific issue.

Test Connectivity to Recipient Mail Server

Check if your server can connect to the recipient's mail server.

Steps:

Use the dig command to check the MX record:
```
dig mx recipientdomain.com
```
Test connectivity to the recipient's mail server using Telnet:
```
telnet mx1.recipientdomain.com 25
```
- Replace mx1.recipientdomain.com with the actual MX record.
- If the connection fails, the issue may be on the recipient's server side.

Whitelist Server IP Address

If the recipient's server uses greylisting, add your mail server's IP address to their whitelist.

Contact the recipient's email administrator and request whitelisting of your server's IP address.

Verify Your Server Configuration

Check Exim Configuration in WHM:

Log into WHM.
Navigate to Home > Service Configuration > Exim Configuration Manager.
Verify the following settings:
- Ensure Allow DKIM verification for incoming messages is enabled.
- Ensure proper routing for local and remote domains.

Restart Exim:

If you made any changes, restart the Exim service:

/scripts/restartsrv_exim

Check Your Server IP Reputation

Your IP address may be blacklisted, causing rejection by the recipient's server.

Check Blacklist Status:

Use tools like MXToolbox Blacklist Check.

If IP is Blacklisted:

Contact the blacklist provider to request removal.
Investigate and stop any spam activity on your server.

Increase Retry Timeout

If the recipient's server is temporarily unavailable, you can configure retry settings in Exim.

Edit Retry Configuration:

Edit the /etc/exim.conf file.
Find the retry configuration and increase the retry timeout. Example:
```
* * F,2h,30m; G,16h,1h,1.5; F,4d,6h
```
Restart Exim after making changes:
```
service exim restart
```

Contact Hosting Provider

If you cannot resolve the issue, contact your hosting provider or system administrator for assistance. They can:

Review server logs and network configurations.
Resolve server-specific issues.

Preventive Measures

Monitor Server Health:
- Regularly check email logs and server resource usage.
Set Up Proper DNS Records:
- Ensure SPF, DKIM, and DMARC records are properly configured.
Use Reliable SMTP Relay:
- For critical emails, use a reliable SMTP relay service like SendGrid, Mailgun, or Amazon SES.
Monitor Blacklist Status:
- Periodically check if your server's IP address is on any blacklists.

Frequently asked questions

Default retry timeout — and can I change it?

Exim default 7 days for normal mail, less for various error classes. Change in `/etc/exim.conf.local` (cPanel) under `retry` section: `* * F,2h,15m; F,12h,1h; F,7d,4h`. Modifies retry curve. Don't extend past 7 days — recipient assumes mail delivered eventually and won't expect explanation if delayed weeks.

Find the failed messages — exact command?

`exim -bp` lists all queued messages with age. `exim -bpr` summary by domain. Bounce messages from "retry timeout exceeded" have specific headers — `grep -l 'retry time' /var/spool/exim/msglog/*` finds them. For each, exim -Mvh shows full headers including reason.

Common underlying delivery failures?

(1) Recipient domain MX unreachable for days (their hosting dead). (2) Recipient mailbox over quota (Exim eventually gives up). (3) IP blacklisted at receiver. (4) DNS for recipient broken — Exim couldn't even attempt connect. The bounce message text reveals which.

Prevention — faster failure for known-bad recipients?

`callout=10s` in Exim config makes recipient validation happen at SMTP RCPT TO time — invalid mailboxes rejected immediately rather than queued for 7 days. Faster failure for senders, better queue cleanliness. Standard practice on modern Exim configs.

Error: "Domain has exceeded the max defers and failures per hour (5/5 (100%)) allowed. Message discarded."

Error: "Has exceeded the max defers and failures per hour (55 (100%)) allowed. Message discarded."

Using /usr/sbin/sendmail -bs for Email Notifications in Scripts

Hosting

Cloud Solutions

For You

VDS

Website Builders

Our services

Client Area

18+ Service. By continuing to use this website, you agree to the use of cookies. More detailed information can be found on the "What are cookies"page.