https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6044
--- Comment #1 from Matt Kettler <[email protected]> 2009-01-15 04:03:05 PST --- If you're interested in performance, you should be using the spamc/spamd combination to scan mail, not the spamassassin script. Spamc automatically will skip passing emails over 250k to spamd for scanning, unless you tell it otherwise on the command line. The spamassassin script is only intended for very low-volume mail and/or manual testing, because it creates a new perl instance every time it's called. It is ungodly slow because of this, and should not be used for scanning mail streams with any decent volume of mail. That's not to say such a plugin can't be made, but it seems pointless. Using spamc causes this benefit automatically, and aborts substantially faster than any plugin ever could cause the spamassassin script to abort. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
