At 09:56 AM (-0500) 2/12/2004 (Thursday), Matt Kettler wrote:
USER_IN_BLACKLIST results from a match of a blacklist_from stamtent in your local.cf or user_prefs. These MUST be placed there manualy.. SA does NOT add them automatically, or via any command-line.
So how is it getting triggered if I know for absolutely certainty that I have not manually defined any blacklist hosts? :-)
This is the extent of what is in my /etc/mail/spamassassin/local.cf:
rewrite_subject 1 subject_tag LIKELY SPAM: report_safe 0 use_razor2 0 use_bayes 1 bayes_auto_learn 1 bayes_auto_learn_threshold_nonspam -3.5 bayes_auto_learn_threshold_spam 12.0 skip_rbl_checks 1 use_dcc 0 use_pyzor 0 score X_OSIRU_OPEN_RELAY 0.001 score RCVD_IN_ORBS 0.001
The contents of /var/CommuniGate/Settings/SpamAssassin/.spamassassin/user_prefs is only the default file (all lines commented out).
The AWL doesn't work by automatcaly adding senders to a whitelist or a blacklist. It's VERY different than that. At the most basic level, the AWL is a score averaging system. I'd recomend some reading of the wiki for info on how the AWL works.
Cool thanks. Interesting stuff. Now I can tease my boss that AWL has him tagged with 7.3. LOL!
--JR
