[SLL] collaborate on a dnsbl?

[Paul A. Franz]

You can manually add offending IP's to your own block list in sendmail. I
block big ranges of IP's from Brazil and all Korean IP's. This made a huge
dent in spam. This might not work for you if you have any need to
communicate with Brazil or Korea. I don't so this works well.

Another large source of spam that there isn't much that I know you can do
about is hijacked end-user computers. There are so many Comcast computers
spewing spam that a number of their mail servers are listed in Spews.

My mail server blocks from a low of 600 or so to over 8000 spams a day yet I
still get a handful everyday on my own accounts. I run a Bayesian filter at
the mail clients that puts spams in their own folder. Works pretty well
however quite a number of mails from this mail list end up there which is a
bit puzzling to me.

Paul Franz
Blackdog Motor Freight
Office/Home 425.641.8202
Cell 425.241.1618
FAX 425.641.1773 

> -----Original Message-----
> From: linux-list-bounces at ssc.com [mailto:linux-list-bounces at ssc.com] On
> Behalf Of Jeremy C. Reed
> Sent: Thursday, May 12, 2005 10:19 AM
> To: linux-list at ssc.com
> Subject: [SLL] collaborate on a dnsbl?
> 
> I continue to get virus and spams sent to my systems that aren't listed on
> the RBLs that I use. I also sometimes check a set of other RBLs and not
> listed.
> 
> What do you all use for easily submitting IPs to blacklists?
> 
> (I am scared to automate because I don't want to submit IPs from good mail
> servers that relay spam to me, such as my NetBSD, FreeBSD, SeaBUG admin
> and other accounts.)
> 
> Or would anyone be interested in starting another DNS-based realtime
> black list?
> 
> Today I want to block these new IPs:
> 
> 216.173.42.231
> 216.173.42.231
> 216.32.65.170
> 201.9.139.17
> 205.152.59.68
> 200.223.105.63
> 201.26.42.65
> 220.70.47.191
> 216.55.167.24
> 209.152.168.19
> 84.94.109.202
> 65.54.187.58 -- spam via hotmail, so probably shouldn't block this
> 213.228.0.62
> 194.85.123.64
> 194.85.123.64
> 222.145.82.226
> 59.32.250.179
> 217.12.10.182
> 196.47.2.58
> 84.129.188.159
> 218.208.229.196
> 81.101.65.25
> 222.104.247.124
> 201.14.44.5
> 
> I guess some of these could be in some DNSBLs by now.
> 
>  Jeremy C. Reed
> 
>  	  	 	 BSD News, BSD tutorials, BSD links
> 	  	 	 http://www.bsdnewsletter.com/