On 14/03/2006 16:37, Bradley Walker wrote:
<snip>
(1) × [EMAIL PROTECTED] F= R=spamcheck_director T=spamcheck: Child
process of spamcheck transport returned 2 from command: /usr/sbin/exim
(preceded by transport filter timeout while writing to pipe)
"transport filter timeout"... there's your clue.
http://www.exim.org/exim-html-4.60/doc/html/spec.html/ch24.html
transport_filter_timeout Use: transports Type: time Default: 5m
"When Exim is reading the output of a transport filter, it a applies a
timeout that can be set by this option. Exceeding the timeout is
normally treated as a temporary delivery failure. However, if a
transport filter is used with a pipe transport, a timeout in the
transport filter is treated in the same way as a timeout in the pipe
command itself. By default, a timeout is a hard error, but if the pipe
transport’s timeout_defer option is set true, it becomes a temporary error."
However, if your spam checks take longer than 5 minutes to complete then
you've got some serious problems outside of Exim, IMO.
Graeme
--
## List details at http://www.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://www.exim.org/eximwiki/
