David Zinder wrote:
Thank you for the response and suggestions.
Yes - lists.surbl.org - I was using the link Contacts->mailing lists
from www.surbl.org
If I understand the request for more info... It seems to get caught by
all the lists. Here is an example from an email this morning. I'm not
sure how to munge, but I think this is what you requested.
Content analysis details: (5.2 points, 5.0 required)
pts rule name description
---- ----------------------
--------------------------------------------------
1.5 URIBL_WS_SURBL Contains an URL listed in the WS SURBL
blocklist
[URIs: techweb.com]
<snip, every surbl and uribl listed>
Well, that's really odd. It's *VERY* unusual for a domain to be in every
surbl and uribl list.
Checking using uribl.com's multi-checker, they've got techweb
whitelisted. They also show surbl as not listing the domain (but they
can't see surbl's whitelists).
However, locally I get some *VERY* strange results:
$dig techweb.com.multi.surbl.org
<snip>
;; ANSWER SECTION:
techweb.com.multi.surbl.org. 0 IN A 63.251.179.13
techweb.com.multi.surbl.org. 0 IN A 66.150.2.134
techweb.com.multi.surbl.org. 0 IN A 8.15.7.117
techweb.com.multi.surbl.org. 0 IN A 66.150.2.134
None of which are appropriate answers for multi.surbl.org.
I get the same results for URIBL.com:
These were sent via the built-in DNS in my verizon fios router.. but
that's really odd.. Perhaps Verizon is screwing up their DNS?
Ahh, yes they are:
http://www.freedom-to-tinker.com/?p=1227
Connecting to those IP's, they're redirects to
"verizonsearch.infospace.com", so Verizon is actively engaging in
hijacking failed DNS lookups..
When I use the local named on my Linux box, which doesn't forward to the
fios router but does the full recursive lookup all on its own, I get a
correct no-answer.
You might want to try running that dig and see what answers you get
back. If you're not running your own DNS, you might want to yell at your
isp..
