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

Will AI Replace Developers in the Future?

Artificial intelligence is changing the tech world at lightning speed. From automated chatbots to AI-generated applications, many people are now…

2 days ago

What is Bot Traffic? Easy Ways to Detect and Block It

Introduction to Bot Traffic Bot traffic refers to visits to a website that come from automated software programs rather than…

2 weeks ago

100+ Essential Windows Commands You Can’t Ignore

Windows may look like a point-and-click operating system, but under the hood, commands still do a lot of the heavy…

3 weeks ago

YouTube Shorts for Beginners: Step-by-Step Guide (2026)

YouTube Shorts are short-form vertical videos designed for quick consumption, typically lasting up to 60 seconds. In 2026, they’ve become…

3 weeks ago

YouTube SEO Secrets That Actually Work in 2026

YouTube SEO Secrets That Actually Work in 2026 YouTube SEO 2026 YouTube SEO Secrets That Actually Work in 2026 If…

4 weeks ago