RE: [cobalt-developers] Adding spam blacklists to sendmail on a Cobalt server

["E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>]

BG> Date: Sun, 20 Apr 2003 21:44:46 -0400
BG> From: Bob G


BG> Also, I specifically UN-recommend using Spamcop as a blacklist.
BG>
BG> (1) it's too aggressive
BG> (2) it's not always up, and when it's down your mail server could fail
BG> (3) spamcop themselves says not to use it in a production environemnt.
BG>
BG> But the rest of them, sure.

The rest are okay?  I disagree.  Don't use SPEWS.  There also are
many more I can neither vouch for nor against.

	http://moensted.dk/spam/

And, frankly, we've had much better results using Bayesian
filters than blacklists.  Consider combining with SpamAssassin if
you can stand Perl.

I'm not one of the kooks who thinks it's illegal to run
blacklists... but those who use bad blacklists deserve the mail
and customer loss that they get.

I also recommend blacklist users maintain a whitelist.


Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.