Massive queue buildup

Brent Addis brent.addis at
Tue Nov 14 00:12:37 GMT 2006

3 seconds?
Not bad!
However, are you sure that includes the mailscanner config? (It might be in /etc/spamassassin or /etc/mail/spamassassin)
if not, include the config file in your lint (I think its either -C or -P /path/to/spam.assassin.conf)


From: mailscanner-bounces at on behalf of Chandler, Jay
Sent: Tue 11/14/2006 1:09 PM
To: MailScanner discussion
Subject: RE: Massive queue buildup

Time spamassassin -D --lint takes three point seven seconds-- I don't
think that's where the holdup is occuring.

Our DNS server is local and on the same netblock as the mailserver in

We have a few RBLs at connecttime, but they seem to be holding up well.

It's a bit of a stumper...

Jay Chandler
Network Administrator, Chapman University
714.628.7249 / chandler at
Today's Excuse: your keyboard's space bar is generating spurious

-----Original Message-----
From: mailscanner-bounces at
[mailto:mailscanner-bounces at] On Behalf Of Brent
Sent: Monday, November 13, 2006 3:48 PM
To: MailScanner discussion
Subject: RE: Massive queue buildup

if you want to only check spamassassin (generally the slowest part with
lots of rules) "time spamassassin -D --lint" is a good start. as long as
your is in a reasonable place it should pick it up. If
you keep an eye on where it seems to take a while, it should help you
track down the problem.

Or, there is an option within mailscanner to turn on batch process time.
I forget the name however its in the last quarter of the config

are you running bayes? If you are, and its standard db files on the
server, I would recommend migrating these to an sql server somewhere.
This helped scan times a fair bit too. Another upside is this also means
you can have multiple servers using the same db.

With RBL's, don't forget spamassassin also does RBL checking so make
sure your not doing twice the lookups you need to.

100k a day should be fine on the hardware you have.


From: mailscanner-bounces at on behalf of Jay
Sent: Tue 11/14/2006 12:39 PM
To: MailScanner discussion
Subject: Re: Massive queue buildup

On Nov 13, 2006, at 2:42 PM, Brent Addis wrote:

        Check your not running one of those massive blacklists from

        I was running one for a while while testing and a similar thing
happened. removing it dropped my average scan time from ~2 1/2 minutes
to 11 seconds per message.

Where does one determine how long the average scan time is?

        Other ideas:

        - Check your dns servers are capable of standing up to the
amount of dns requests you are making. Running something like nscd
locally is a good idea.

I suspect they are, but I'll verify this.

        - Are you running very many RBL's within mailscanner? Try
disabling these and see if it helps.

Three or four-- nothing insane.

        - Are you running any type of recipient verification? (as in,
checking that the person being sent the mail actually exists). If not,
try turning it on. I am unsure what it is called within postfix as I
don't use it.

We are.  Messages to undefined users fault to a 5xx error.

        - Check out
which has a few others as well.


        How much mail are you handling a day? I have a couple of single
cpu 3.0 ghz machines comfortably handling many thousands of messages a

Right now, about 100K a day.

Thanks for the help!

Jay Chandler
Network Administrator, Chapman University
714-628-7249 / chandler at
"Bother," said Pooh as he struggled with /etc/, "it never
does quite what I want.  I wish Christopher Robin was here." -- Peter Da
Silva in a.s.r.

MailScanner mailing list
mailscanner at

Before posting, read

Support MailScanner development - buy the book off the website!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 7654 bytes
Desc: not available
Url :

More information about the MailScanner mailing list