Author: Tamas TEVESZ Date: To: Chris CC: exim-users Subject: Re: [Exim] Expensive Queue Flushes & Retry
On Wed, 26 Sep 2001, Chris wrote:
> Is there any way to have the queue runner process examine the message
> *before* forking a process to deliver it?
if no other way, turn off automatic queue runs, arrange a <insert your
fave scripting language here> tool to 1) get a queue list, 2) get
corresponding retry hint entries from the hints db, 3) produce an
msgid list that needs to be tried now, 4) do the run for these only
(and this can be maybe even 1/50th of the messages you want to try as
exim accepts multiple msgids for "-M". it'll pose less load on the
machine, although naturally slightly slower as the level of
paralellization is smaller than one-exim-for-every-message. get ideas
from the xargs manpage :)
> I also wouldn't mind turning off updating the msglog for "retry time not
> reached", if that's possible.
