http://bugzilla.spamassassin.org/show_bug.cgi?id=4013





------- Additional Comments From [EMAIL PROTECTED]  2004-12-03 19:00 -------
For that matter, please make a test that does not do NS and A lookups for SURBL
checks (if it currentlyy is).  NS resolution is broken in some proxies, and
SURBL lookups would be much more efficient without any NS or A checks.

Here are Dallas Engelken's comments about the broken resolver:

"Well, the platform is not really the issue here I don't believe... The
surrounding platform is.  Their SA is running on redhat 7.3, perl 5.6.1.
They have this Symantec Raptor software firewall running on an NT box,
and for some reason, it doesn't resolve NS resource record queries.
Been on the phone with them (symantec) about it, they say they have
never supported it in the DNS proxy, but in their new version, support
for it is experimental.  I was like WTF, its just like any other DNS
lookup.

So anyways, if you run a  'host -tNS domain.com', you get no answers.
Not even a NXDOMAIN.   This causes SA to think DNS is not available and
not run any network tests unless you hard code it.   Even then SURBL
does not work because it does a NS lookup before pulling the A records.
Dunno why, that's why I'm asking for feedback here.

I guess it is possible that even when NS records are properly working on
a good setup, that NS's are still being pulled for the URI domains that
are being compared against SURBL.  Whether this is creating false
positives or not is another thing.  I'm still trying to figure out
how/if the NS lookups are being used in SA as it pertains to SURBL.  I
realize the NS's are resolved and compared against SBL, and maybe this
is why NS's are pulled for all URIs, but its just a DNS lookup that is
not needed IMHO... And with lots of URIs to lookup, this could cause it
to take twice as long on the surbl lookups."

Perhaps this should be a separate ticket, but the issues may be related.
Adding Dallas to ticket notification.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to