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. -- ## 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/
