Oh. Silly me, I didn't respond to the original rule question. I made the same wrong assumption in my obfu rules generator. The problem with the original rule is the trailing word boundary marker:
\b matches the space between "\w\W" or "\W\w" the "]" character is \W, so for that rule to match, there must be a \w directly following the "]". The original rule works if you remove the trailing word boundary. HTH -- Chris Thielen Easily generate SpamAssassin rules to catch obfuscated spam phrases: http://www.sandgnat.com/cmos/ Chris Santerre said: > I don't even run them thru SA. I have procmail skip them out of the loop. > > You rule looks fine to me! > > -----Original Message----- > From: Marc Steuer [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 19, 2003 2:49 PM > To: [EMAIL PROTECTED] > Subject: [SAtalk] Negative score for SAtalk messages > > > > Hi list members, > > I want to score messages from [SAtalk] with a negative score so examples > posted to the list won't be tagged as spam. This is my first venture into > regex and I've tried: > > header MY_SATALK Subject =~ /\[SAtalk\]\b/ > describe MY_SATALK Message from [SAtalk] > score MY_SATALK -10 > > Messages with [SAtalk] in the subject aren't always matched by this rule. > > Two questions: > 1. Do I have the rule syntax correct? > 2. Is there an alternate way to ensure SAtalk messages won't be tagged as > spam? > > Thanks, > Marc ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
