There is probably a stale entry in Exim's database in:
/var/spool/exim/db
in the 'retry' or 'callout' files.
This can occur under some circumstances if exim is stopped/restarted (or
crashes) or upgraded during a delivery. He,e you can end up with a
reference to an email in the database that no longer exists in the spool.
On our production systems (mail relays) handle 50,000-100,000 messages
per day we have the odd occurrence of this sort of symptom so once every
6 months or so when we install a security patch (eg. OpenSSL) or an Exim
upgrade we delete the contents of the database directory and let Exim
re-build it as necessary.
Mike
On 10/04/2016 05:58, Rob Gunther wrote:
> I keep getting a bunch of spool file not found errors, like this:
>
> 2016-04-09 00:34:13 1aogqr-0001Nl-MN Spool file 1amYf4-0008Hm-7j-D not found
> 2016-04-09 00:34:13 1aogqr-0001Nl-MN Spool file 1amYgz-0008Ke-Hp-D not found
> 2016-04-09 00:34:13 1aogqr-0001Nl-MN Spool file 1amYgz-0008KT-Dj-D not found
> 2016-04-09 00:34:13 1aogqr-0001Nl-MN Spool file 1amYf4-0008Hl-7i-D not found
> 2016-04-09 00:34:13 1aogqr-0001Nl-MN Spool file 1amYf4-0008Ha-1s-D not found
>
> The complete list is about 25 messages long and it repeats in the log
> often, but not at consistent times. I thought maybe every minute or
> something, but it might happen 2 times in a minute and it might not happen
> for 3 minutes.
>
> I checked the queue, and no such files even exist in the queue.
>
> What is Exim doing?
>
> I took one message, with id 1amYf4-0008Hm-7j and found the first instance
> in the logs. It first shows up on March 3, 2016.
>
> A message delivery was attempted, the remote server rejected it and an
> undelivered notice was created with the ID 1amYer-0008FE-VG.
>
> The undelivered notice with ID 1amYer-0008FE-VG was delivered successfully.
>
> 2016-04-03 04:45:57 1amYf4-0008Hm-7j Completed
>
> Every since then, exim keeps trying to deliver the message - even though it
> was delivered and does not exist on the disk anymore.
>
> I have stopped and started Exim but it continues to look for the same batch
> of messages that do not exist on the disk. How do I correct this and
> prevent it from happening?
>
>
> Robert G.
