-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is anyone who is using the TQMCUBE RBL with their email server seeing any significant decreases to the effectiveness of the list?
The TQMCUBE DNSBL is the first RBL we check -- it had been dropping about 60% of our incoming email connections. Four days ago, that percentage dropped to around 30%. We have not added any whitelists entries on our server that would be causing email to bypass this. Other DNSBLs that we check as well are showing an increase in the percentage of our email blocked as a result but nowhere near the total delta now getting past TQMCUBE. As a result, our SpamAssassin server has been getting slammed, maxing out our concurrent child connections and eventually timing out and letting email pass unfiltered. We switched to a new server this morning that has 4GB of RAM (twice prior) and we've been stepping up our max connections in chunks of 10 -- currently at 60. Grepping the maillog for 'prefork: child state' I can see the ebb and flow of concurrent connections. I realize email is bursty so spikes are expected. However, we continue to run into sustained periods of time were all the child processes are forked and busy. Server is running SA 3.1.8 with SARE rulesets, DCC, Pyzor, Razor, Botnet, iXhash, KAM and FuzzyOCR. CPU load is negligible. I did remove the SARE header and obfu rulesets (> 100K) per the FasterPerformance wiki page and am in the process of setting up a caching nameserver on the box. Any other ideas for performance improvements? This is also an indication of future performance issues if we stop using RBLs on the SMTP front door completely and only use them for scoring in SA. This is a consideration so we wouldn't completely reject valid emails; they would be in our quarantine area and could be retrieved for X days. Thanks, David Goldsmith -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3rc2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF40sy417vU8/9QfkRAvMtAJ0aeWlttkG/rfs3lmt92ohvjBmu9ACgoFWN f8MQvXpdz+k7wck0diroo68= =nPpf -----END PGP SIGNATURE-----
