Am 28.01.2015 um 20:46 schrieb srach:
28. Jan 2015 19:28 by li...@rhsoft.net <mailto:li...@rhsoft.net>:
maybe you need some numbers why the below config is good and
greylisting not needed
peak day 2015/01
* postscreen rejects: 90000
* spamassassin: 120
* clamav: 15
* delivered mail: 850
that are numbers for a single day
Okay that is very good! Numbers are good to see. And they make a clear
story. Wow that is really good percents.
see attached mailgraph
So I think I leave alone the greylisting idea and the deep protocol tests.
For the later steps of both Spamassassin & CLamav, to keep them less
expensive too what recomends are there? Still the policyd or the
spamc? I am starting to read the documents for these now with new eyes,
not wanting the greylisting integrated or not.
* spamass-milter with spamd
* clamav-milter
both are acting before-queue what's no problem given only a small amount
of mail make it there and the benefits are that you can tag from let
say 5.0 to 7.9 points and reject >= 8.0
http://www.postfix.org/MILTER_README.html
having that setup since august 2014 for 1200 users replacing the
previous Barracuda Networks appliance and the results are great, the
server load is zero, it's running stable and no complaints
well, there are HELO/PTR-filters and python-spf-policyd in front of the
milters too - if would have imagined how well that all works at the end
(after a lot of hours for tuning and config) i would own that setup for
years now instead a few months
I am arriving to a good solution with these ideas. Asking with getting
good answers here changes it for the better.
I am seeing the documents are like a fat Oxford Dictionary. Many many
words with official particular definitions. They are like a book for
childs too, that it tells some very simple stories. But to write stories
richly someday like Mr. Shakespeare we must have advise from old authors
writing some bad books already in the past! :-)
