On Tuesday, July 16, 2002, at 12:53 AM, Rick Eames wrote:
I am getting overwhelmed with SPAM. What is the best way to cut that down
for the server? One by one basis, or globally?
There are two ways to "stop" spam on a server basis, blocking and
filtering, which boil down into three routes of action.
1. Using sendmail's access.db,
2. Using DNS Blocklists,
and 3. Using a procmail-based filter like SpamAssassin or SpamBouncer.
Every time someone asks the list about this, I am reminded that I
need to spend some time on the instructions I was putting together
on this. See <http://bluebird.sinauer.com/~morse/cobalt/> for my
preliminary stages, which mostly include instructions for
implementing DNSBL's (following Charlie Summers' instructions posted
about a year ago.)
For more on the access.db, see a discussion from the beginning of
this month, where Tim Dunn <http://list.cobalt.com/pipermail/cobalt-
users/2002-June/072714.html> and Charlie <http://list.cobalt.com/pipermail/
cobalt-users/2002-July/073395.html> explain its use against spammers.
Also, Steve Bassi posted his (extensive) notes on installing
Spamassassin last Thursday; they are in the archives at
<http://list.cobalt.com/pipermail/cobalt-users/2002-July/074325.html>.
Steve, may I incorporate these into my pages?
Are there any prebuilt packages for this?
Not that I'm aware of, though I'd love to hear that I'm wrong.
However, aside from SpamAssassin or SpamBouncer, no outside software
should be needed; most Cobalts have the required bits already
installed and running.
They just need some configuration.
pjm
_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users