Phillip,
When we run exim -M with any old msg's it attempts a retry, fails and then
re enters it into the queue again, and it is never deleted. Is there
anything simple I can enter into the configure file to remove ANY messages
after they are older than 7 days regardless of there state (frozen)
Richard
----- Original Message -----
From: "Philip Hazel" <ph10@???>
To: "Richard Bible" <rbible@???>
Cc: <exim-users@???>
Sent: Tuesday, May 13, 2003 7:37 PM
Subject: Re: [Exim] Spool Maintenence
> On Tue, 13 May 2003, Richard Bible wrote:
>
> > We run a large exim installation, using double level hashing on the
spool,
> > msglog and input dirs.
>
> Which release of Exim?
>
> > We are finding messages stay in our queue past 7d in either a frozen
state
> > or just undeliverable.
>
> Detail? What happens if you use -M to force a delivery for such a
> message?
>
> > ignore_errmsg_errors_after = 1d
>
> Aha. That's an Exim 3 setting. Sorry, but Exim 3 is obsolete. Exim 4 has
> moved on a long way, and I think there have been changes in this area,
> but without trawling the change logs I can't be sure of the detail.
>
>
> --
> Philip Hazel University of Cambridge Computing Service,
> ph10@??? Cambridge, England. Phone: +44 1223 334714.
>
>
