On Thu, 23 May 2002, j.linn wrote:
> I have been trying to catch the error condition "pipe delivery process
> timed out" to prevent it generating an error message but, my preference,
> put it back in the spool area for a later re-try or freezing the message.
There is no way to do this. My thinking was that, if it timed out once,
what's the point of trying again?
> I think it is an internal bsmtp timeout (error message in mainlog)
>
> SMTP data timeout (message abandoned) on connection from local process
>
> and do not see any way of getting round this. There is no
> "bsmtp_receive_timeout", only smtp.
You are running exim->pipe->exim so you have control at both ends,
though it can be confusing.
The "pipe delivery process timed out" message is from the delivery
process. This is controlled by the "timeout" option on the pipe
transport (default 1h). It should be possible to see from the logs
whether it really did take an hour to timeout.
> The Bsmtp timeout setting must be set at something like 240s as I can see
> values for scanning greater than that from spamd log about the same time.
The SMTP incoming timeout, set by smtp_receive_timeout, applies to
BSMTP. The default is 5 minutes. The value can be overridden by the -os
option. Oh, hang on, that's Exim 4. Let me look at the Exim 3 manual...
In Exim 3, it's smtp_accept_timeout, and there's no command line
override, I'm afraid.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
