Thanks Helmut. I do pretty much the same thing.
While I use bayes training with SPAM/HAM folders, this isn't very
suitable for ISP type installations at this point, as it's server-wide
and the SPAM/HAM folders are shared with everyone. We can probably come
up with something better when we look at implementing DSPAM and dovecot
LDA. In a nutshell, I'd like to see global scanning on the front-end,
and user-controlled scanning on the delivery side. Again, long term. I'd
really like to nail the logging upgrade first.
Also FWIW, I've discontinued using graylisting. SamC (spamdyke author)
and I agree that its usefulness seems to have run its course.
Considering the negative impact it has on users (me included), for me
it's not worth using it. Besides which, it's usefulness is difficult to
measure (although iirc I may have modified the qtp-prune-graylist script
to give a little insight).
Thanks.
--
-Eric 'shubes'
On 03/12/2014 11:06 AM, Helmut Fritz wrote:
I use bayes with these scores in my local.cf for spamassassin:
score BAYES_00 0 0 -2.612 -2.899
score BAYES_05 0 0 -1.110 -1.110
score BAYES_20 0 0 -0.740 -0.740
score BAYES_40 0 0 -0.185 -0.185
score BAYES_50 0 0 0.001 0.001
score BAYES_60 0 0 1.5 1.5
score BAYES_80 0 0 3.0 3.0
score BAYES_95 0 0 4.0 4.0
score BAYES_99 0 0 5.1 5.1
I run the false positives through the Bayesian filter pretty much daily with
this script after putting the spams into aspam mailbox, I also have a ham
mailbox in case any real spam sneaks through. This works for server wide,
we all get the same stuff although I do have a couple users that are
technical and can dump stuff into the spam and ham mailboxes (via separate
imap accounts - copy into them):
#!/bin/bash
#Spam Assassin Bayes Training
DOMAIN=fritz.us.com
SPAM=is-spam
HAM=not-spam
# Learn spam!
cd /home/vpopmail/domains/$DOMAIN/$SPAM/Maildir/cur
sudo -u vpopmail -H sa-learn --spam --no-sync --progress ./*
rm -rf /home/vpopmail/domains/$DOMAIN/$SPAM/Maildir/cur/*
cd /home/vpopmail/domains/$DOMAIN/$SPAM/Maildir/new
sudo -u vpopmail -H sa-learn --spam --no-sync --progress ./*
rm -rf /home/vpopmail/domains/$DOMAIN/$SPAM/Maildir/new/*
# Learn ham!
cd /home/vpopmail/domains/$DOMAIN/$HAM/Maildir/cur
sudo -u vpopmail -H sa-learn --ham --no-sync --progress ./*
rm -rf /home/vpopmail/domains/$DOMAIN/$HAM/Maildir/cur/*
cd /home/vpopmail/domains/$DOMAIN/$HAM/Maildir/new
sudo -u vpopmail -H sa-learn --ham --no-sync --progress ./*
rm -rf /home/vpopmail/domains/$DOMAIN/$HAM/Maildir/new/*
sudo -u vpopmail -H sa-learn --sync --progress
I do not enable per user spamassassin control as most of my users are not
technical, the exception being a couple that I have help with ham and spam
per first paragraph.
I was still getting a significant amount of spam, so installed and turned on
spamdyke. I watched the logs for a couple days to gain confidence in it, it
is awesome and is probably the most significant spam blocker we can get,
especially with graylisting. you might want to set your graylist timeout
lower than default though - I ran into a couple issues where some mail
servers immediately retried sending the email after the initial graylist
reject (rr.com), mine is graylist-min-secs=90. I might even turn
spamassassin off.
This is what I do currently, if anyone sees flaws or suggestions let me
know. I can give more details as well.
Helmut
-----Original Message-----
From: Jim Shupert [mailto:[email protected]]
Sent: Wednesday, March 12, 2014 10:53 AM
To: [email protected]
Subject: [qmailtoaster] Battle SPAM--best practices
what might be some wisdom on SPAM
Best practices - gotchas - options - real world experiences That work
thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
