On Fri, 30 Jul 2010, Adam Moskowitz wrote:
I want to use spamassassin's per-user whitelisting as part of some mail processing I'm doing. I'm dealing with a lot of messages (potentially over 100,000), but doing it one-at-a-time (and I can't easily change that). spamassassin takes a long time to load and run (1.5 - 2 seconds per message), and it's performing over 50 tests per message even though for this purpose I need only 1 or 2 of those tests.
How about: run a spamd on a non-default port configured with your rules subset, and score your corpa using spamc against that spamd? You'll get much better performance than using a foreground spamassassin, and potentially you could multithread it.
Using straight spamassassin is a bad idea for performance reasons, as you've noticed.
-- John Hardin KA7OHZ http://www.impsec.org/~jhardin/ jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 ----------------------------------------------------------------------- ...much of our country's counterterrorism security spending is not designed to protect us from the terrorists, but instead to protect our public officials from criticism when another attack occurs. -- Bruce Schneier ----------------------------------------------------------------------- 6 days until the 275th anniversary of John Peter Zenger's acquittal
