some problems with bopm doing blacklist lookups

Deedra Waters <[email protected]>
Newsgroups gmane.network.irc.bopm
Message-ID <Pine.LNX.4.58.0311131334410.25500@simba>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi!
I am a senior staff member for the freenode irc network, and lately have 
been managing the proxy scanner (bopm) I recently enabled the blacklist 
options again. It works fine for the most part, though there are some 
errors. I don't know what theese mean, and was hoping someone could give 
me some feedback as to what it means, and a suggestion how to correct it. 
One of the other staff seems to think this is a bug. I've pasted the 
errors below.

12:22 < ~proxyscan:#freenode-status> DNSBL -> Lookup error on
          144.161.136.144.opm.blitzed.org: Server failure
12:22 < ~proxyscan:#freenode-status> DNSBL -> Lookup error on
          158.133.217.12.opm.blitzed.org: Server failure
12:22 < ~proxyscan:#freenode-status> DNSBL -> Lookup error on
          176.159.214.212.opm.blitzed.org: Server failure
12:22 *** Quits: proxyscan [[email protected]] (Killed by
          OperServ ())


- -- 
Freenode staff member: [email protected] , http://www.freenode.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/s94PU5AGPOTGNc8RAgE2AKCM/wyDe5nQtvk/+z4K70iywwn+JQCfSZKm
ok/3ctrwQEz4g52RQ2Zd3eU=
=XHJg
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.