Re: exim's retry database acting up

On Mon, 6 Jan 1997, John Henders wrote:

jhenders >> I finally had enough of this nonsense and stopped exim and erased the
jhenders >> retry database. On startup exim delivered all messages to their
jhenders >> destination.
jhenders >
jhenders >In order to stop the new messages from being queued, you need to set the
jhenders >retry time lower. If you look at the retry rules in configure, there is
jhenders >(or should be) enough flexibility there that you could set local
jhenders >delivery retrys to every 30 seconds or so in order to prevent this
jhenders >problem in the future.

If an NFS volume becomes active again then delivery of all messages must
be triggered somehow. If the userforward director was failing and is now
working again then all pending messages because of that userforward
failure need to be delivered.

The situation for hosts is different. All messages for one host have one
retry cycle. In the same way: All messages depending on one userforward
directory need to have a common retrycycle and they are all to be
delivered if that director becomes working again.

--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
PGP Public Key = FB 9B 31 21 04 1E 3A 33 C7 62 2F C0 CD 81 CA B5