-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello John,
Monday, September 22, 2003, 12:48:55 PM, you wrote: >> Something like >> > body RM_b_V-drug /V[Ii1\|[EMAIL PROTECTED]/i >> but for the subject, right? JP> Yes, this is along the lines of what I wanted since, at least my JP> version of SA, has only a rudimentary test in the body, which does JP> not of ourse address the Subject line at all or the various JP> mis-spellings commonly used. Head for http://www.exit0.us and http://www.merchantsoverseas.com/wwwroot/gorilla/sa_rules.htm -- you'll find plenty of rules there that will give you a good start at building your own rule base, including my own V-drug body test which can be easily converted into a subject header test (I've added a little to it since then -- compare the extract above against the sample you find, and you should be able to reconstruct the entire rule). >> What do you mean by "systems-wide use", and how much access do you >> have to your full system? JP> My virtual server is hosted by viaVerio and then I in turn host a JP> bunch of low-volume sites. I want to have the "new" rules apply to JP> all of them, so it would go in the /etc/mail/spamassassin/local.cf JP> file. I do have full access to that, so that's not an issue. I have JP> bumped up the Scores for the tests you mentioned. Good. So you can add rules to /etc/mail/spamassassin/local.cf for anything you want to apply to all of your domains. JP> Since making my post, I found over the weekend where SA actually JP> keeps it own Rules files ( i.e., /usr/local/share/spamassassin/ ), so JP> now I can see the syntax in use on some of the simpler ones and maybe JP> figure out a regex that will work. Good! Took me three months to find that resource! JP> Better yet, I am thinking that I should be able to update the whole JP> /usr/local/share/spamassassin/ with a more current set of Rules, such JP> as from the Version that I see has just been released. Unfortunately not. Rule sets tend to be version-specific. There's new functionality in 2.6 required by many of the 2.6 rules. Those rules simply won't work in 2.5x. And the scores in the 2.6 rule set have been adjusted with the assumption that all of the 2.6 rules are operational (as they are in 2.6). So trying to implement 2.6 rules in 2.55 may make things worse than what you have. What you can do is download the 2.6 rules, and see which ones do apply to 2.55 (all the simple regex rules, and possibly others). You can't rely on the 2.6 scores for these, but if you have a decent corpus of your own, you may be able to determine a suitable score for them on your system. Bob Menschel -----BEGIN PGP SIGNATURE----- Version: PGP 8.0 iQA/AwUBP2+gL5ebK8E4qh1HEQIxkACgmE5fkiHztluf92c4+vi9f7yOlNMAnjDi P0kVkvOiKIGWMeMh22o8IEiT =agHR -----END PGP SIGNATURE----- ------------------------------------------------------- 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
