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

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…

2 weeks 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,…

2 weeks ago

Designing a Christmas Website: Creative Ideas & Best Practices

With vibrant colors, cheerful graphics, and a sprinkle of festive magic, your website can instantly create an emotional connection and…

3 weeks ago

Meet Sora: The Game-Changing AI Video Model from ChatGPT

The world of artificial intelligence is evolving faster than ever — and one of the biggest breakthroughs is here. Sora,…

1 month ago

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 month ago