> OK -- I've addressed guenther's issue, and cleaned up that conditional code in
> a more consistent way with the existing code. Also, the reason the rule was
> now not hitting was because I used the wrong rule type in the first place for
> URIBL_DBL! doh. using "urirhssub" now seems to be working with a test msg
> here.
+ # set to 1 if _any_ URIBL supports non-domains_only lookups
+ my $dnsbl_lookup_ips;
Not initialized. ;) Anyway, as I just said in a previous post, do we
need that? The comment now is correct. However, it guards the
+ if ($dnsbl_lookup_ips) {
+ $self->lookup_dnsbl_for_ip($scanner, $obj, $dom);
call exactly then. Called, if *any* URIBL supports IPs. Not called only
in the corner case, if all URIBLs are unhappy with IPs. Is it worth the
loop, to prevent that function call? lookup_dnsbl_for_ip() has the
tflags check now itself.
Also, in sub lookup_dnsbl_for_ip():
+ next if ($tflags->{$rulename} =~ /\b(?:ips_only|domains_only)\b/);
No IP lookup, with tflags ips_only?
One of us needs more coffee. ;) I know I do...
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
