On Wed, 19 Apr 2006, Ralf Ertzinger wrote:
> http://www.exim.org/mail-archives/exim-users/Week-of-Mon-20040830/msg00135.html
>
> The exim version is the default RHEL4 version, so it's a little oldish
> (based on 4.43).
>
> Has this bug been fixed in a more recent version? Looking through the
> changelogs showed nothing definite.
I cannot remember, it's too long ago, but it is the sort of thing that I
would eventually have picked up on. Ah yes, this looks like the relevant
ChangeLog entry:
14. Obscure bug fix: if a message error (e.g. 4xx to MAIL) happened within the
same clock tick as a message's arrival, so that its received time was the
same as the "first fail" time on the retry record, and that message
remained on the queue past the ultimate address timeout, every queue runner
would try a delivery (because it was past the ultimate address timeout) but
after another failure, the ultimate address timeout, which should have then
bounced the address, did not kick in. This was a "< instead of <=" error;
in most cases the first failure would have been in the next clock tick
after the received time, and all would be well.
But if you are using 4.43, it should be fixed...
--
Philip Hazel University of Cambridge Computing Service
Get the Exim 4 book: http://www.uit.co.uk/exim-book
