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 Get More Customer Reviews That Build Trust and Sales?

Customer reviews have become one of the most influential factors in modern buying decisions. Before choosing a product, service, or…

3 days ago

Why Micro-Influencers Matter: How Small Creators Drive Higher Engagement and ROI

In today’s digital landscape, consumers trust people more than brands. Traditional ads are often ignored, celebrity endorsements feel scripted, and…

1 week ago

2026 SEO Roadmap: Skills Every Digital Marketer Must Have

Introduction: SEO in 2026 Is No Longer Optional—It’s Strategic Search Engine Optimization in 2026 has evolved far beyond keywords and…

2 weeks ago

Website Affirmations for 2026: Build, Grow, and Succeed Online

With 2026 just days away, it’s time to reimagine your website’s future. Hostripples encourages businesses, creators, and entrepreneurs to begin…

1 month ago

Cron Jobs: Automate Everything While You Sleep

Cron Jobs – The Unsung Heroes Think of cron jobs as the unsung heroes of your server — capes optional,…

1 month ago