Categories: Hostripples Featured

Retry time not reached for any host after a long failure period

If you are receiving the following error in exim_mainlog file then refer to the following solution.

===========================

Exim : retry time not reached for any host after a long failure period

===========================

The issue is because of the corrupted exim db files.

Go to /var/spool/exim/db and delete files: retry , retry.lockfile , wait-remote_smtp, wait-remote_smtp.lockfile

#cd /var/spool/exim/

#rm retry retry.lockfile wait-remote_smtp wait-remote_smtp.lockfile

After that restart the exim service.

#/etc/init.d/exim restart


HR-ADMIN

Recent Posts

The Ultimate Guide to WordPress Maintenance: Tips and Tricks

When you’re running a business that relies on website traffic and sales to succeed. Then you need to keep it…

6 days ago

Migrate In 2024: Our Comprehensive Website Migration Manual to the Next Level

Migration! Yes, this word is very big in the web hosting industry and it has its importance. Especially for businesses…

1 week ago

Unveiling the Importance of Server Maintenance Plans: A Comprehensive Guide

The server is the backbone of the web hosting industry and it acts like a HERO in the web hosting…

2 weeks ago

IP Address is Blocked? A handpicked list of Solutions to Fix it?

Imagine you are on holiday having a cup of tea and browsing your website or blog.Then, what next?You will get…

3 weeks ago

Explained: Difference between Nameservers Vs. DNS

The web hosting industry is growing every minute, day, and year. It has many terminologies that are important to understand…

1 month ago