On 25/08/2011 10:01, Graeme Fowler wrote:
> Please try two things: Firstly, run "exim_tidydb /path/to/spool retry"
> and see what happens, if the problem continues then simply stop Exim
> and *remove* the retry DB file altogether (it's only a hints file so
> is safe to delete). It strikes me that there may be some stale data
> lying around. Alternatively it could be related to a very old bug in
> Exim's retry handling but that was wrinkled out a long time ago... Graeme
Thanks for the reply,
Shortly after my last email I actually used exim_dumpdb to check if
there were any entries in any of the databases that related to the
domains in question. The only entries were in the callout db andnone
seemed relevant to the error.
The only oddity I came across was that there was no misc.lockfile
present to dump that db though I could create one (removed after) and
the dump returned nothing.
I am running Exim version 4.69 so I wouldn't think there would be any
old bugs knocking around, the OS is Centos 5 so it is the latest out of
the packages.
Regards,
Colin.
