On Mon, 25 Mar 2002, Dean Brooks wrote:
> My question, I guess, is whether or not routing failures adhere to
> ultimate message retry timeouts? If so, would a syntax routing error
> like this also be candidate?
Yes, and yes. I have put this on the list of things to investigate, to
check that it is working as it should (sounds as if it isn't).
> Also, when I would manually do a "exim -q", it would *always* attempt
> rerouting of the message, rather than saying "retry timeout not reached"
> like it does for most messages.
> Further, an exim_dumpdb on the retry
> database would never show ANY entry for the local-part/domain in question.
That may be part of the problem!
> Not sure if this is my problem or an Exim problem, but I would have
> thought that no message would have ever been allowed to be on the
> queue more than 4 hours based upon our retry rule config above.
You are quite right. It appears to be a bug. I'll investigate in due
course. Thanks for the report.
Philip
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
