On Tue, Nov 12, 2002 at 01:05:43PM -0600, Patrick Bores wrote: > header MY_SUBJECT_TEST Subject=~/subject1/ > header MY_SUBJECT_TEST Subject=~/subject2/ > header MY_SUBJECT_TEST Subject=~/subject3/ > > and then have "score MY_SUBJECT_TEST -100" in a global file. This allows > > The way that spamassassin is written, this only works for the last > header rule defined, because it is not capable of recognizing that these > are distinct rules that use the same score line.
No, you are just defining the same rule 3 times. That's why the last one is the one that runs. > Of course it is not desirable to magically come up with a new rule name > and a new > Has anybody come up with a creative solution to this problem? Well, I've done something like this for some rules in the 2.50 (CVS) version. Basically, make a meta rule that looks for certain named rules, and checks to see if any of them triggered. It makes use of a short-hand method in 2.50 which I hope stays in, although there were some folks not happy with it ... ie: header __MY_SUBJECT_TEST_<UNIQUE> Subject=~/foo/ header __MY_SUBJECT_TEST_<UNIQUE> Subject=~/bar/ header __MY_SUBJECT_TEST_<UNIQUE> Subject=~/baz/ meta MY_SUBJECT_TEST (__MY_SUBJECT_TEST_.+ +) > 0 score MY_SUBJECT_TEST -100 Just make sure that <UNIQUE> is different per rule, and you're fine. (you also need to make sure that the rules get picked up via user_prefs, but that's another issue...) -- Randomly Generated Tagline: "Your next question is 'How does this gate work?' I don't know. I don't have to know, I'm not an Electrical Engineer, I'm a Computer Scientist." - Prof. Hamel ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd522.html _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
