I didn't ignore your first message, in fact I read it, have it archived in a
folder here to continue to try and discern helpful information from. Being
I'm working 14-17 hours a day as a business owner, replies sometimes can't
always come in due time.
Anyway I am currently running Jeff Lasman's spamblocker which blocks spam
before it has a chance to be processed by SpamAssassin. That is probably
blocking a good 75% of the spam that is being sent to the server. However
for the remaining 25% of spam, I need SpamAssassin to filter it and tag it
appropriately. However the system itself is not under a stressful load at
this point. Load averages throughout the day sometimes can even be
0.0/0.0/0.0 while email is continually being processed.
Several people on the SpamAssassin list have commented that the spamc child
process has been terminated created the error that I orginially posted.
Their thought was that it's the orginating program (exim in this case) that
is terminating the spamassassin child process causing it to bounce the
message back to the sender.
-----Original Message-----
From: Jakob Hirsch [
mailto:jh@plonk.de]
Sent: Tuesday, March 14, 2006 12:22 PM
To: bawalker@???
Cc: exim-users@???
Subject: Re: [exim] Exim timeout?
Bradley Walker wrote:
> 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.
transport_filter_timeout, default is 5 minutes.
But this will not help you. Just think how many messages you can process per
day if scanning a single one takes more than 5 minutes.
Some advice were already given to you, without any feedback, so I guessed
you just ignored it. The problem may be your exim config (rather than exim
itself, else this would mean there is a flaw in Exim which has to be fixed),
but the source is SA itself. SA is slow and puts a lot of load on your
system. So you should stop as much garbage as possible before it hits SA.
There were a bunch of discussion on the list about that and there are some
hints in the Wiki.
