Author: Todd Lyons Date: To: Chris Russell CC: exim-users@exim.org Subject: Re: [exim] exim 4.72 - No retry, immediate long failure timeout
On Wed, Jan 5, 2011 at 8:13 AM, Chris Russell
<Chris.Russell@???> wrote: > Hi Dave,
>
>> the root cause. I usually delete the retry db files
>> and restart exim which clears it up. Have not had reports
> This has to be something as you've said with the retry databases not updating or becoming corrupt, as your fix has solved the problem. Thanks again for the tip!
In the future you can db 'db_dump -d a /var/spool/exim/retry' and if
it complains about the structure of the file, then you know for sure
it's corrupted. (on CentOS 5.x it's in the db4-tools package, which
is not installed by default).
--
Regards... Todd
I seek the truth...it is only persistence in self-delusion and
ignorance that does harm. -- Marcus Aurealius
