Hello all, I've started looking at SA with an eye towards implementing it as an opt-in spam filter for our mail systems here at the University of Wisconsin - Madison. I began using it personally about three weeks ago and I have been impressed by it. I really like the way SpamAssassin works with the scoring of email, such that things like ORBS and the RBL only contribute to the score, and don't cause outright rejection. However, SA is really slow, and I need to deal with 150-200 email messages per second for 85,000 accounts without a room full of hardware.
I've been reading the threads about porting SA to C, and am incredibly interested in that in conjunction with spamproxyd. I was also planning on disabling some of the checks, like Razor, for extra speed. I did have a few questions, that I was hoping someone could answer: 1) Why does SA continue the checks when the mail has already exceeded the required_hits value? Would it be worth it to add a flag to stop the checks? I can see the informational value in knowing that your mail has a score of 32.82, but if you're like me and just trying to move as much mail as possible... 2) Was the C version of SA going to end up somewhere public? :-) A'rpi? 3) Was there already an effort to reorder/reevaluate the rules for speed? I did catch the discussion about the slower rules, but if people here at the UW are going to futz with things in SA I'd like them to futz with things people aren't already working on. :-) 4) How do you guys want patches? Thanks, all. Have a good day. ...Bob ...................................................................... Bob Plankers [EMAIL PROTECTED] University of Wisconsin - Madison +1.608.262.7783 Division of Information Technology http://bob.plankers.com _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
