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

How to Design a Website for Black Friday 2025 (Complete Guide)

Black Friday 2025 is here — the biggest shopping moment of the year, where customers expect unbeatable prices, fast performance,…

1 day ago

301 Redirects for WordPress: What, Why & How (SEO Best Practices)

When you move or delete a page on your WordPress website, visitors — and search engines — can easily hit…

4 days ago

Meet Perplexity: AI That Thinks Like a Researcher

Introduction Artificial Intelligence has made remarkable strides — from writing poetry to generating code. Yet, most AIs still act like…

2 weeks ago

Top 15 AI Text Writers in 2025 — Features, Uses, Pros & Cons Explained

Introduction Artificial Intelligence has revolutionized the way we create, refine, and scale written content — from blogs and marketing campaigns…

2 weeks ago

This Diwali, Give Your Website the Glow It Deserves — Host Smarter,Rank Higher

Every Diwali Brings New Light, New Beginnings, and New Opportunities In today’s digital world, your website is the Diya that…

1 month ago