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 Future of App Development: No-Code, Low-Code, and Traditional Coding

The app development industry is evolving at an incredible pace. A decade ago, creating an application required extensive programming knowledge,…

2 weeks ago

Why You Should Move Your Website to Cloud Hosting?

Introduction to Cloud Hosting In today's digital world, website performance can make or break an online business. Whether you run…

1 month ago

What is a Call to Action in Marketing? Definition + Examples

In the world of digital marketing, getting attention is only half the battle. The real goal is to convince people…

2 months ago

Website Bandwidth: What it is and Why it Matters?

Introduction In today's digital world, understanding website bandwidth is essential for anyone running a website. Whether you own a blog,…

2 months ago

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