On 07/02/2014 03:05 AM, Dave Funk wrote:
Unless you've explicitly disabled them, the network based rules (razor,
pyzor, dcc, DNS based rules, RBLs, URIBLs, etc) constitute an external
'reputation' system to pass judgment on messages.
Actually, DCC is not included in the default due to arbitrary
restrictions on request volume for the public servers. 100,000 per day
or something. And neither is Pyzor, presumably for similar reasons?
Razor2 is in by default.
I use all these, but have reservations about them. DCC Pyzor and Razor2
are lists of bulk email. Not specifically of *unsolicited* bulk email.
Many of my users are on lists of various sorts.
The DNSBL's are problematic because so many ISP's mail servers are on
them. We get quite a few emails from employees at companies who's ISP's
are on Spamhaus lists, or whatever, due to nothing that has anything to
do with them.
It's not uncommon to take a low-scoring spam and find that it gets a
higher score on retest as it has been added to various bad-boy lists.
Except that the "bad-boy" lists flag more ham then spam.
This is also one way that gray-listing helps.
Review the thread. You don't want to talk to me about greylisting. ;-)
But for all the discussion today, we never really had a good talk about
postscreen, which is something I'd like to hear someone expound a bit upon.
I've used site-wide Bayes with auto-learning at a site with ~3000 users
and have had to flush & restart our Bayes database twice in 10 years.
I'll add you to the list of people telling me that jumping out of an
airplane at 20,000 feet with nothing but a parachute and a pair of
underwear is fun.
-Steve
