Does anyone know if Exim has some sort of built in timeout feature that can
be changed somewhere?? The reason I ask is that yesterday after spending
time on the SpamAssassin mailing list, they suggested I check to see if Exim
had a timeout feature.
All of this goes back to the continuous problems I'm having with running
Exim 4.60 and SpamAssassin 3.1.1 together. Anyway after upgrading to SA
3.1.1 I went back through and flushed all of the log files out so I can get
an accurate picture of what Exim was doing. I started running this setup at
11:00pm last night and had to stop it at 11:00am this morning after once
AGAIN customers were on the phone and IM coming at me that their email
wasn't work. The exim logs showed that out of 453 received emails that Exim
processed in that 12 hours, there were 59 errors. Almost EACH error was
identical to the one listed below:
(1) × mleatherland@??? 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)
I posted this to the SpamAssassin mailing list and they suggested that it
would be an Exim problem, due to SpamAssassin child process possibly taking
a few minutes to run various spamtests on it, but Exim times out waiting for
the message to come back, kills the SA child process and goes forward from
there.
All I know is that something is going on and it's a combined problem of Exim
and SA. I'm just not sure where to look next. I can't afford to keep
experimenting because it's eventually going to drive customers away, either
from lack of spam filtering or the spam filtering causing customers to not
get/reply to emails.
