John Hardin wrote:
>
>
> It would also be useful if (before changing your config) you provided the
> results of DNSBL lookups at your site for some large known-clean domains
> like google.com, microsoft.com, etc. If they are all FPing, then the
> problem is as I stated above and the fix is straightforward. If not, then
> more investigation is warranted.
>
>
Thank you John!
Not sure if I'm fulfilling your request or not, but here is my best attempt
so far:
$ host google.com.multi.uribl.com
;; connection timed out; no servers could be reached
$ host google.com.multi.surbl.org
Host google.com.multi.surbl.org not found: 3(NXDOMAIN)
$ host microsoft.com.multi.surbl.org
Host microsoft.com.multi.surbl.org not found: 3(NXDOMAIN)
$ host microsoft.com.multi.surbl.org
Host microsoft.com.multi.surbl.org not found: 3(NXDOMAIN)
$ host websiterepairguy.com.multi.uribl.com
;; connection timed out; no servers could be reached
$ host websiterepairguy.com.multi.surbl.org
websiterepairguy.com.multi.surbl.org has address 184.106.15.239
websiterepairguy.com.multi.surbl.org has address 69.16.143.110
Host websiterepairguy.com.multi.surbl.org not found: 3(NXDOMAIN)
It looks like google.com and websiterepairguy.com have something in
common. It looks like uribl.org is ignoring requests for both of these
domains and letting them time out. Is this a correct assumption?
Ed Abbott
--
View this message in context:
http://old.nabble.com/False-Positive-on-Domain-Name-tp33975030p33977290.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
