On Thu, 15 Apr 2004, Thomas Fini Hansen wrote:
> > > This release fixes a serious recipient callout caching bug that was introduced
> > > in 4.31. Also, I have reversed the change in 4.31 that caused Exim to use the
> > > real sender when doing recipient callouts (which is where the bug was). The
> > > default behaviour is now what it was in 4.30. However, there is a new option
> > > to request the altered behaviour.
>
> What kind of problems showed up?
The problem was a huge increase in the number of callouts, particularly
for incoming spam, where the sender address tends to be different every
time. If you know that the receiving host does not make any use of the
sender while verifying, then it makes sense to use <> as the sender, so
that the cache reduces the number of callouts when you get lots of
messages for the same recipient.
> (Thought: If Exim could keep that callout open, and actually try the
> delivery as soon as it's accepted the message right after, that would
> be insanely cool. But I know, it's just gonna stay a wet dream.)
Correct. Sorry.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
