On 11/01/2013 01:38 PM, Tim Whitaker wrote:
"Are you running Spamdyke?"

No I don't believe so, but I can look into installing it.

"SpamAssassin logs to /var/log/qmail/spamd."

Yeah I know about that log, but that only shows you that it's running, has
pids and children, etc.  It doesn't actually give me any type of "I blocked
this email because of X" kind of logging.

I just checked out /etc/mail/spamassassin/local.cf and it is already set to
these settings:

ok_locales all
skip_rbl_checks 1

required_score 5
report_safe 0
rewrite_header Subject ***SPAM***

use_pyzor 1

use_auto_whitelist 1

use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1



Hmm,

Check in logs in /var/log/qmail/smtp for simscan entries, like this:

simscan:[14918]:CLEAN (-1.40/12.00):10.4742s:message subject here:192.168.7.33:[email protected]:[email protected]


CLEAN means SpamAssassin scored the message less than the reject threshold. In this case, the message scored -1.40 and the reject threshold is 12.00

The reject threshold comes from the spam_hits=12 entry in your /var/qmail/control/simcontrol file.


In my logs in /var/log/qmail/spamd I see entries like this when SpamAssassin analyzes a message:

[2139] info: spamd: clean message (-1.4/5.0) for clamav:89 in 6.8 seconds, 16674 bytes. [2139] info: spamd: result: . -1 - BAYES_00,DATE_IN_PAST_12_24,DKIM_ADSP_CUSTOM_MED,DKIM_SIGNED,DKIM_VALID,FORGED_SENDER,FORGED_SENDER_SOFT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE scantime=6.8,size=16674,user=clamav,uid=89,required_score=5.0,rhost=qmt01.example.com,raddr=127.0.0.1,rport=58763,mid=<[email protected]>,bayes=0.000000,autolearn=no


And I totally agree with what Angus wrote about Spamdyke. If you look at the numbers I posted earlier, over 96% of our unwanted messages for the month of October were blocked by Spamdyke, and we don't even use graylisting. Less than 3% were blocked by SpamAssassin.


Regards,

Brent Gardner



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to