The idea here is to provide an easier way to create rules for the users own email system (whether it be GroupWise/Outlook, etc.). Creating a rule to put a message in a folder for ** SPAM - 10.2 ** is much harder than ** SPAM - Likely **. It also lets me create that scale at my will (geometric/logarithmic/whatever). I would like to just add this as an option to the base code, with parameters in the local.cf file for the scale and words. Then you can decide as an administrator how to change the subject line.
The other benefit, is for my users to be more aware of false positives V.S. really obvious spam. If it is really close to the threshold, then it is more likely to be a false positive than if it is double the threshold. So, if it comes with a spamscore of < 1.2 (under 1.2 times the threshold - whatever that may be) then, it may be a false positive. Take a look at it to be sure. If it is 3.5, odds are it is spam. But, for the end user, they don't wish to see hits of 17.2, and the threshold, they want information, simple and sweet, against which to base a decision. If they want further information, they can look at the headers, it is all right there. But, again, it is harder to write rules for numbers, V.S. a known set of words (no we are not running perl at the email client). And, we are centralizing our SA rules (no per user rules). The only piece of code would be PerMsgStatus.pm and maybe the parameter load code (stuff that scans the local.cf file). And that, not even much. If it was contained with if statements, then if you opt out, it wouldn't take much processing power either. Steve >>> Chris Petersen <[EMAIL PROTECTED]> 12:02:40 PM 07/12/2002 >>> > The solution: Change the way it reports on the subject line, and let it > all through. That's how I handle most of my stuff... > In PerMsgStatus.pm (which is where the subject line is changed) I am > adding two additional variables: _SPLV_ and _SPLG_. > Spamlevel = hits/threshold (so hits of 15 with threshold of 10 = 1.5, > hits of 15 with threshold of 5 = 3, hits of 4, threshold of 5 = 0.8). > I then have a table (Using an if statement): > 1.2 <= Possible > 1.7 <= Likely > 1.7 > Definitely. So this is essentially creating additions to the current "score" variable, right? How hard would it be to get spamassassin to handle deletions, etc according to either score or spamlevel? Anyway, I personally think that at least the ranking (possible/likely/etc) is an awesome idea. Especially if those thresholds could be manually modified/renamed/added by each user in their personal prefs. My only concern would be that with higher score thresholds, a direct ratio probably wouldn't be the best way of handling things. A logarithmic scale of some sort would probably paint a more accurate picture, since it's much more likely that a spam would score 10 out of 5 than 50 out of 25, etc. -Chris --------------------------------------------------------------------------- For more information about Lewis and Roca LLP, please go to www.lewisandroca.com. Phoenix (602) 262-5311 Tucson (520) 622-2090 Las Vegas (702) 949-8200 NOTE: This message is intended only for the use of the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender of this E-Mail or by telephone. --------------------------------------------------------------------------- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
