Hi:
We have also experienced slowness by SA where it takes 20 to 30 seconds to process a message. This might be OK for a stand alone Linux box but it is unacceptable for a production mailserver handling several thousand email accounts.
In our experience we have traced the problem to the large number of RBL's, DNSBL's, and other network tests (SPF, SURL, SORB) that seem to be multiplying in SA. Not counting DCC and RAZOR there must be over a dozen that are now consulted for every email. If you consider the hundreds of thousands of boxes now using SA and the billions of emails processed by SA these RBL's are just getting overloaded.
Has anybody thought about that? And is anybody considering response time and load capacity of an RBL before adding it to SA? No wonder we're getting time-outs on some of these tests and our servers are overloading with SA processes sitting around waiting for RBL results.
I think before any other network tests are added we need some logging added to SA that would show the response speed of each network test. Then we'd be able to quickly turn off those that are timing-out instead of the trial and error method we use now.
Just my two cents.
Best Regards,
Jeff Koch
