"score $TESTNAME 0"
into your local.cf to disable the test. Though that one test is fairly low scoring, it would barely be enough to bring it under your threshold. You might want to check why messages are getting caught by the RBL's, it seems almost as if it is checking for localhost, but I wouldn't think that SA wouldn't query for 127.0.0.1 since that will hit a few rbl zones that include it for some reason (when they should be including 127.0.0.2 or something).
Ryan Moore ---------- Perigee.net Corporation 704-849-8355 (sales) 704-849-8017 (tech) www.perigee.net
John wrote:
I am running Amavis-New, Postfix, SpamAssassin 2.60 4....
I have a webmail system running from the same box. Scanning the messages sent from the webmail system is
alright but I just found a false positive......
X-Spam-Status: Yes, hits=6.9 tag1=3.0 tag2=6.3 kill=6.3 tests=HTML_30_40, HTML_MESSAGE, HTML_MIME_NO_HTML_TAG, MAILTO_TO_SPAM_ADDR, MIME_HTML_ONLY, RCVD_IN_DYNABLOCK, RCVD_IN_NJABL, RCVD_IN_NJABL_DIALUP, RCVD_IN_SORBS X-Spam-Level: ******
I don't really care about people emailing to known spam addresses (at least that is what I am assuming with the test MAILTO_TO_SPAM_ADDR). 1) Does anyone know any negative drawback to disabling that test? 2) To disable the test, just edit the /etc/mail/spamassassin/local.cf file and insert "MAILTO_TO_SPAM_ADDR 0"?
Thank you.
------------------------------------------------------- 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
