administrivia: blocked IP addresses and the proposed KBL

[Richard Welty <rwelty@xxxxxxxxxxxxxxxxxxxxxx>]

i'm soliciting input on a project i'm considering.

as many of you are aware, the krusty server that hosts digest.net mailing
lists subscribes to certain "blocking lists" for spam control purposes.

we used to subscribe to MAPS, but the MAPS stuff
(http://www.mail-abuse.org/) has gone through some changes, so right now
we're using two sublists of SPEWS (http://www.spews.org/). i tried using
the full SPEWS blocking list, but while it really nailed the spam, it also
cut out too much legit traffic alongside the spam.

additionally, i maintain my own set of manually blocked email sources,
which may be viewed at

http://www.krusty-motorsports.com/blocked.html

(many of you will not follow the rest of this posting, which is ok)

i am considering publishing these in an additional format, the same sort of
DNS format which MAPS, SPEWS, and other blocking services use. there are a
couple of reasons. one is the instructional value -- i'd like to learn how
to set one up (it doesn't look too hard.) another is a maintenence issue --
i can convert the krusty email system to use this service itself, so the
amount of work involved in maintaining such a system is only slightly more
than what i'm doing now.

for those of you who administer Mail Transports out there (you know who you
are), would having the KBL (krusty blocking list) available be of interest
to you? your answers probably won't affect whether i do the project; i'm
pretty much going to. i'd just like to find out if anyone else cares.

there is a third reason to do this -- by naming it the KBL, there is an
opportunity to tell kibble jokes.

of course, i could host the list on a domain name that i'm not currently
using for anything (howitzerworld.com, i guess it would then be the HBL).

thanks,
   richard

- -------- End of message -------

------------------------------