Performance between SpamAssassin 3.2.1 and 3.2.2 and 3.2.3

Alex Broens ms-list at
Wed Aug 15 18:45:14 IST 2007

On 8/15/2007 7:08 PM, Gareth wrote:
>> -----Original Message-----
>> From: mailscanner-bounces at
>> [mailto:mailscanner-bounces at]On Behalf Of Greg
>> Matthews
>> Sent: 15 August 2007 17:56
>> To: MailScanner discussion
>> Subject: Re: Performance between SpamAssassin 3.2.1 and 3.2.2 and 3.2.3
>> given the relatively low traffic on this thread and my own inability to
>> spot the performance issue (even tho my upgrade to 3.2.2 happened pretty
>> recently) suggests that most people (myself included) have hidden the
>> problem behind a caching DNS server. Can anyone on this thread confirm
>> whether or not they are using a caching DNS?
> I am using a caching DNS server and upgraded from 3.1.8 to 3.2.3 today and
> it does seem slower but I cannot really tell since our mail volume is very
> low and most system maintenance does not even cause the queue to build up to
> 30 messages.
> I expect the majority of people are like me and have servers which are
> capable of processing far more email than they currently receive so each
> mailscanner run only handles a few messages so it is quick anyway.


look into all the RBL/DNSB tests wich are enabled by default and start 
disabling the ones you don't really need by setting the score to 0 in a file in /etc/mail/spamassassin.

I presume some of these lookups are happening on sites with few mirrors 
and/or low capacity/overlaoded servers and depending on what side of 
what pond you are, delay may be more or less noticeable.

Net lag can be deadly in processing speed, even with a local caching DNS.

Check thoroughly what each lookup does and evaluate



More information about the MailScanner mailing list