Hi all,
I just noticed that we have had auto_whitelisting turned off since 2005 (!). I just turned it back on (first deleting the auto_whitelist file in /home/exim/.spamassassin (we run a site-wide installation) and ensuring that file was re-created after restarting spamd). It seems to be working. So now when I peruse the logs, I see the new tag AWL being added for the first time. But then I saw this fly by: Apr 6 10:54:12 mx1-server spamd[12713]: spamd: result: Y 18 - AWL,BAYES_99,DRUGS_ERECTILE,FB_CIALIS_LEO3,FORGED_OUTLOOK_HTML,FORGED_OU TLOOK_TAGS, FORGED_YAHOO_RCVD,HTML_MESSAGE,HTML_MIME_NO_HTML_TAG, MIME_HTML_ONLY,MSGID_OUTLOOK_INVALID,SPF_HELO_PASS,SUBJECT_DRUG_GAP_C, UNPARSEABLE_RELAY,URIBL_BLACK,URIBL_JP_SURBL,URIBL_SC_SURBL,URIBL_WS_SUR BL,URIBL_ZEN scantime=6.5,size=1206,user=nobody,uid=108,required_score=5.0,rhost=loca lhost.localdomain, raddr=127.0.0.1,rport=45215,mid=<007401c4dc05$2105c210$7c07c...@gew>,bay es=0.999996,autolearn=spam It looks like it did everything correctly, giving the message a high score (18) and autolearning it in Bayes, but I was surprised to see the AWL tag get slapped onto this one. Is that normal behaviour? We are running SpamAssassin 3.25. - jim - -
