I've attached the message I'm playing with right now (as a zip because SourceForge rejected it the first time); here's the rule that's failing to trigger:
uri SPAM_SITE_11 /(domainsforpeople|pandabearperks)\.com/i describe SPAM_SITE_11 Body contains a spamserver site address score SPAM_SITE_11 2
I tested and couldn't reproduce the bug on 2.54
I was using following rules (one each of uri, body and rawbody)
uri SPAM_SITE_11 /(domainsforpeople|pandabearperks)\.com/i describe SPAM_SITE_11 Body contains a spamserver site address score SPAM_SITE_11 2
body SPAM_SITE_12 /(domainsforpeople|pandabearperks)\.com/i describe SPAM_SITE_12 Body contains a spamserver site address score SPAM_SITE_12 2
rawbody SPAM_SITE_13 /(domainsforpeople|pandabearperks)\.com/i describe SPAM_SITE_13 Body contains a spamserver site address score SPAM_SITE_13 2
and your test message got tagged by my copy of 2.54 with:
X-Spam-Status: Yes, hits=6.0 required=5.0
tests=SPAM_SITE_11,SPAM_SITE_12,SPAM_SITE_13
version=2.54
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
