We'd like to welcome and thank the addition of a new SURBL public name
server e1.surbl.org administered by:
spamchek.com
Without our public name servers and the help of their administrators,
SURBLs would not be possible.
Our thanks to all of them!
P.S. We could still use a few more public nameservers. More information is at:
http://www.surbl.org/public-dns.html
We'd like to welcome and thank the addition of a new public
SURBL name server h4.surbl.org administered by:
Mailshell
Without our public nameservers and the help of their
administrators, SURBLs would not be possible.
Our thanks to all of them!
We'd like to welcome and thank the addition of a new public
SURBL name server a4.surbl.org administered by:
Barracuda Networks
Without our public nameservers and the help of their
administrators, SURBLs would not be possible.
Our thanks to all of them!
We'd like to welcome and thank the addition of a new public
SURBL name server c2.surbl.org administered by:
University of Arizona
Without our public nameservers and the help of their
administrators, SURBLs would not be possible.
Our thanks to all of them!
We'd like to welcome and thank the addition of a new public
SURBL name server b3.surbl.org administered by:
NOC4 Solutions
Without our public nameservers and the help of their
administrators, SURBLs would not be possible.
Our thanks to all of them!
We'd like to welcome and thank the addition of a new public
SURBL name server e4.surbl.org administered by:
Georgia Institute of Technology
Without our public nameservers and the help of their
administrators, SURBLs would not be possible.
Our thanks to all of them!
[Note that this change was actually made about a year ago, around
November 1, 2005. I hope the delayed notification doesn't cause
any major issues.]
Previously, each SURBL zone file, including the bitmask-combined
list multi.surbl.org, had testpoints with A records resolving to
127.0.0.2. That was a design decision, and it was also convenient
to the way the zone files were generated before.
But Justin Mason or one of the other SpamAssassin developers
argued that multi should have testpoints corresponding to all
ones set for each bitmask position. So testpoints for
multi.surbl.org now have all the bits set for an A record value
of 127.0.0.126 instead of 127.0.0.2 .
(If a new list is added in future using the 128th bit, then the
new testpoint values in multi will be 127.0.0.254)
This may work better with applications that decode the bits
into individual list results, but it is a change from before and
it may break other applications' use of the testpoints.
The multi.surbl.org BIND zone file contains:
test.surbl.org 604800 IN A 127.0.0.126
604800 IN TXT "multi.surbl.org permanent test point"
test.multi.surbl.org 604800 IN A 127.0.0.126
604800 IN TXT "multi.surbl.org permanent test point"
surbl-org-permanent-test-point.com 604800 IN A 127.0.0.126
604800 IN TXT "multi.surbl.org permanent test point"
2.0.0.127 604800 IN A 127.0.0.126
604800 IN TXT "multi.surbl.org permanent test point"
The multi.surbl.org rbldnsd zone file contains:
test.surbl.org :126:multi.surbl.org permanent test point
test.multi.surbl.org :126:multi.surbl.org permanent test point
surbl-org-permanent-test-point.com :126:multi.surbl.org permanent test point
2.0.0.127 :126:multi.surbl.org permanent test point
Cheers,
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/
I'm pleased to announce that we are now including PhishTank
data:
http://www.phishtank.com/
in our phishing list:
http://www.surbl.org/lists.html#ph
Be sure to report your phishes to PhishTank through their web
site. This helps get the phishing sites get blacklisted.
Thanks to PhishTank for creating their system and making the data
available to the Internet community!
Cheers,
Jeff C.
--
Jeff Chan
mailto:jeffc@surbl.org
http://www.surbl.org/