Just released SpamCopURI 0.17. This is basically a bugfix release.
Upgrade if you see something you need:
0.17 Mon May 24 18:23:55 PDT 2004
- added code to handle hex encoded and base 10 encoded
IP addresses
- added backslash handling in urls (http:/\www.google.com)
- handling case when host of a URL is a '.'
- calling env_proxy on LWP::UserAgent to support proxied
users (thanks to bluebanana )
http://sourceforge.net/projects/spamcopuri/
--eric
Eric Kolve has released SpamCopURI version 0.16 which fixes the
handling of the few URIs which use numeric IP addresses.
http://sourceforge.net/projects/spamcopuri
If you're using SpamCopURI, please upgrade to this new version.
Thanks all,
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/
I have just released SpamCopURI 0.15. I have fixed a few bugs
that were reported and also added some url extraction so open_redirect
resolution isn't need any longer for urls that redirect through
google.com, msn.com, yahoo.com or any site that redirects based
on a url being passed in the query or path portion.
The install *should* be smoother. The Makefile.PL now attempts
to detect where SpamAssassin was installed and place itself in
that directory. See the Changes file for a complete list.
https://sourceforge.net/projects/spamcopuri/
--eric
We are now removing any subdomains (third or greater level
domains or host names) from generic TLDs:
http://www.icann.org/tlds/
using a "new"-style regular expression:
s/^([^\.]*\.)+([^\.]*)\.(com|net|org|edu|mil|biz|info|int|arpa|name|museum|coop|aero|pro)$/\2.\3/
It seems to do the right thing, both on test cases and the actual
data, so it's now live on all the SURBL lists. If anyone sees any
problems with this regex, please let me know.
Bill's domains from sa-blacklist are already in the correct form :-)
and have no subdomains on these gTLD domains going into
ws.surbl.org. I added it also to sc.surbl.org and be.surbl.org
which did get rid of a few errant records. Subdomains are now
properly removed in be and sc, as they should have been.
This may result in slightly better matching on both be and sc
since the clients are supposed to be doing similar things with
domains found in message URIs.
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/
1. We'd like to welcome and thank our two new public name
server administrators and hosts:
Dave Burke and esat.net
Bjorn Jensen and info-connect.dk
Without the help of all of our public nameservers, SURBLs
would not be possible. Thanks Dave, Bjorn and all the
administrators and networks of our nameservers!
2. We've added some documents about using rbldnsd, rsync, dnscache
and BIND to locally cache SURBL (and any other RBL) zone files.
Bob Cottrell describes setting up rbldnsd and rsync on top
of an existing BIND server:
http://www.surbl.org/rbldnsd-howto.html
Rick Macdougall writes up how he set up rbldnsd to run on
the same name server as dnscache from djbdns:
http://www.surbl.org/dnscache-rbldnsd.html
I've written up how to use rsync with BIND to cache RBL
zone files, though rbldnsd is a better solution for many
reasons.
http://www.surbl.org/bind-rsync.html
In addition, NJABL has some helpful tips on setting up
rbldnsd and rsync to serve RBL zone files locally:
http://njabl.org/rsync.html
Kind thanks to Bob Cottrell and Rick Macdougall for preparing
and sharing their notes for everyone's benefit! Please let me
know if you have any comments on these. Any errors are probably
due to my transcriptions.
*****************************************************************
Anyone running a high-volume mail system (i.e., more than 250,000
inbound messages per day) is strongly encouraged to set up local
caching of their RBL zone files including SURBLs. The benefits
are improved mail performance, reduced network traffic, and
offloading of the public nameservers. rbldnsd and rsync is the
preferred way to do it, but BIND will also work (slower ;-).
Also if you are using a version of SpamCopURI prior to the
current 0.14, please upgrade it. Some earlier versions do not
support DNS caching, which can result in excessive DNS traffic.
http://sourceforge.net/projects/spamcopuri/
*****************************************************************
3. We have lowered the refresh times on ws.surbl.org and
be.surbl.org zone files to 20 minutes. This change should not
affect most SURBL users. Refresh times of 10 minutes remain
unchanged on sc.surbl.org. Retry times are programatically half
of the refresh times (i.e. 10 and 5 minutes respectively).
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/
http://www.surbl.org/news.html
Ask Bjørn Hansen of develooper.com is using SURBL data to block
spammer domains in the Metamark Shorten Service URI shortening
and redirection service. This is the first use of SURBL data to
prevent abuse of a redirection site that we've heard of! Great
going!
Ask explains his motivation as: "I mostly did it to make it less
likely that I'll have to deal with abusers of the service
manually. Hopefully the other redirection services will realize
that benefit soon as well."
To anyone who knows how to contact the other redirection sites:
please feel free to write them with this news and possibly the
open letter to redirectors:
http://www.surbl.org/redirect.html
Cheers,
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/
The SURBL community, including developers, users, fans and all
would like to thank the people and networks who have volunteered
to carry our SURBL zones on their public name servers. In no
particular order, they are:
Kelsey Cummings and sonic.net
Raymond Dijkxhoorn and tudelft.nl
Bill Stearns and pa.net
Erik O'Connor and littleredbat.net/supranet.net
Dave Funk and icaen.uiowa.edu
Doc Schneider and maddoc.com
Mark Reynolds and telstra.net
David Coulson and davidcoulson.net
Richard Zuidhof and zonnet.nl
Daryl Jones and smrn.com
Vincent Schonau and xs4all.nl
Left off this list are some specific network and facilities
providers where some of the name servers are located, so
we'll leave it to our friends to forward our thanks to them.
This project would not be possible without our great public
DNS servers thus far, so our hearty thanks go out to everyone
helping to get the SURBL data out.
We also encourage anyone else with DS3 or faster network
connections to consider helping us provide DNS for these zones.
Interest in using SURBLs is ramping up from many different projects
and people, but when SpamAssassin 3.0 comes out in a few months
with its built-in support for SURBLs, the DNS traffic will
probably jump significantly. So we could probably still use some
more help with DNS. Please let us know if you can help.
Expect DNS traffic to max out around 1 or 2 Megabits per second
if things really take off. Also the more servers we have the
less traffic each one does, so a larger community helps to share
the load!
*************************************************************
We also want to strongly encourage any high-volume users of
SURBLs to set up local caching name servers for the zones
in order to offload the public name servers. Probably the
best way to do this is with rbldnsd and rsync, though BIND
versions of the zone files are also available via rsync.
Please contact Raymond at rsync at surbl dot org with your
name server's IP address in order to get rsync access. This
will help keep the load on the public name servers reasonable,
and it's also good engineering practice since it will get you
the best performance for using SURBLs. To re-iterate, if
you're running a high volume mail server, please do your
SURBL queries from your local name server by pulling the
zones using rsync and not from the public servers. Thanks!
*************************************************************
Also, we'd like to remind all SURBL users that the name of the
SURBL list derived from Bill Stearns' sa-blacklist has changed
from sa.surbl.org to ws.surbl.org. If you are using the old name
please change your configs to use the new name. After checking
that DNS traffic for the old name is minimal, we are ceasing DNS
service on the old name now, so use ws.surbl.org now! The
different SURBL lists are described at our site:
http://www.surbl.org/
Please forward this message to any interested parties. It
seems to be getting more difficult to keep in contact with
everyone using SURBLs, so a little help getting the word out
could be useful.
Thanks everyone!
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/
4/24/04: In order to prevent future confusion, we are changing
the names of the rbldnsd zone files from .rbldns to .rbldnsd . If
you are using rbldnsd, please update your rsync and cron configs
to use the slightly revised .rbldnsd names. For now both old and
new names are being served, but we may want to stop serving the
deprecated names at some point in future. If you're using the old
names, please update to the new ones. We expect the new names to
be stable. The changes to the rbldnsd zone file names are:
sc.surbl.org.rbldns --> sc.surbl.org.rbldnsd
ws.surbl.org.rbldns --> ws.surbl.org.rbldnsd
be.surbl.org.rbldns --> be.surbl.org.rbldnsd
(For background, there are two RBL name server programs with
similar names but different functionality: rbldnsd and rbldns.
Zone files for the two programs do not share the same syntax. But
they are similar enough to cause potential confusion.)
4/24/04: Zone files now only update when the underlying spam
URI domains have changed.
The latter change means there are fewer unnecessary zone
transfers, but could potentially affect anyone who was looking at
the zone file serial numbers or file times as a status flag or
heartbeat.
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/
[Linked from the surbl site also... -- Jeff C.]
From: Dallas L. Engelken
To: spamassassin-users, spamassassin-dev
Date: Thursday, April 22, 2004, 3:13:23 PM
Subject: ANNOUNCE: The SARE SURBL+ Checker v0.4
http://www.rulesemporium.com/cgi-bin/uribl.cgi
- domain and ip lookups for sc/ws/be.surbl.org
- ip lookups for standard txt based rbls found in SA
For folks processing more than a a few hundred thousand messages
per day, please set set up a local caching name server for any of
the RBLs you are using, including SURBLs. This is considered a
standard, good practice since it offloads the public name servers.
A very popular and fast name server specifically meant for
serving up RBLs is rbldnsd:
http://www.corpit.ru/mjt/rbldnsd.html
SURBL zone files are available in rbldnsd format.
Then arrange with the RBLs to get rsync access to their zone
files. Since rsync only transmits differences, the zone files
are kept updated in a very efficient manner. For example to get
rsync access to SURBL zone files, please contact Raymond at
rsync at surbl dot org.
Other RBLs have similar procedures for gaining rsync access.
Then configure your mail servers using RBLs to query your local
forwarding RBL name server.
Thanks,
Jeff C.
P.S. Please don't grab zone files from our web site for
production or even hobbyist mail servers, as I see some people
apparently doing right now. I want to say that's really lame,
but that would be rude. ;-)
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/