On Tue, 29 Jul 2003, Dean Brooks wrote:
> As a feature request, would it be possible to add a configurable
> transport option of "transport_filter_timeout"?
>
> Currently, Exim 4.20 appears to have a hardcoded timeout of 300 seconds.
Do you want to reduce this or increase it?
There are actually two timeouts involved. The 300 seconds applies when
Exim is waiting for output from the filter process; a 30-second timeout
is applied when it is waiting for the process to finish (after reading
"end of file").
Both of these timeouts were of the "paranoia" variety, because when
transport filters were conceived, they were thought of as something that
could make small changes to messages "on the fly" as they were
delivered. Therefore, everything should be very quick.
The idea of using SpamAssassin as a transport filter came later; it is
of course a Cunning Plan, but it rather changes things because it can
take a substantial time.
> For now, I can just manually change the value in the source code of Exim,
> but a configurable option would be great.
WishListed.
--
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
