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 Science Behind Social Media Posting Times

In today's digital landscape, timing is everything. Whether you're a social media manager, business owner, or content creator, the success…

7 days ago

Mastering Google Search Console: Tips for New Users

Are you a website owner? Maintaining the website is the prime concern for any website owner. Yes, it’s equally important…

1 week ago

A Comprehensive Guide to Changing and Protecting the WordPress Login URL

If you’ve planned to launch a WordPress website, you might get a question, “How do I log in to WordPress?”…

2 weeks ago

The Ultimate Showdown: Linux vs Windows for VPS Hosting

As the demand for virtual private servers (VPS) continues to grow, businesses and individuals are faced with a crucial decision:…

1 month ago

Questions to Ask Your Web Hosting Support Team

Web hosting is a large industry, as many other factors help any web hosting provider to form a company. The…

1 month ago