Charles Gregory wrote:
> Well, yes, that's the whole point. The message *looked* like 'ordinary
> text', but failed to match. SA triggered fine on a URI rule in the
> same message, and there were no 'mime parts' to confuse it. My best
> guess is that one of the characters is somehow not really alphabetic,
> but is like a 'high bit' version of the letter? Or maybe '*' is not
> part of the \W class?
Post the message to this group or upload it and post a link. That way, we
can look to see if something is odd / wrong with that message.
If you would rather figure this out yourself, add this rule to your local.cf
file:
body PRINTBODY /(^.*$)(?{ print "Body:\n$^N\nEnd Body\n" })/i
Then run the same message through SpamAssassin using -D for debug and watch
the output, it'll show you what SA sees as the body text and output exactly
what the rules would see when they run. Remember to always remove this rule
when done with it, it'll always score 1 point if not!
This has saved me troubles many times, for example, I was writing a rule to
catch multiple spaces between specific words and I found that "body" tests
was removing all unnessary spaces and causing my tests to break. For the
life of me, it was a simple regex looking for 3 or more spaces and I
couldn't get it to work. After using this test rule, it showed me how the
extra spaces were removed before the rule ran, and that's why my rules
weren't firing.
HTH
Frederic Tarasevicius
Internet Information Services, Inc.
http://www.i-is.com/
810-794-4400
mailto:[EMAIL PROTECTED]
