Gary,

> Considering I have seen a number of instances where those of us with
> low powered servers have had to increase $sa_timeout after upgrading
> to SpamAssassin 3.1 would you consider putting $sa_timeout back into
> amavisd.conf and amavisd.conf-sample?
> + $sa_timeout = 30;   # timeout in seconds for a call to SpamAssassin
> +     # (default is 30 seconds)

Let's unify and simplify things, and slowly phase out the $sa_timeout.
With 2.4.0 a timeout for external processess (decoders, command-line virus
scaners) is 2/3 or the remaining time from the initial $child_timeout,
but at leaset 10 seconds.

I'll do the same for SA check, but take $sa_timeout if that is bigger
than the calculated time. This will allow us to slowly forget about the 
existence of $sa_timeout.

  Mark


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to