Jay Levitt wrote:
I discovered Net::DNS::Resolver::errorstring, and put some more logging
into SA, and the problem is really simple: my caching-only nameserver
times out when looking up NS records for a site that's not in the
cache. Not entirely surprising, with a 3-second timeout in SA. And
Since none of the devs have posted a followup on this, I think that perhaps
this is worth a bug in Bugzilla. If the analysis is valid it needs to be
fixed. If it isn't, one of the devs will probably explain why it should
work as it does.
Loren
I discovered
On Thu, Feb 24, 2005 at 07:17:16PM -0800, Loren Wilton wrote:
Since none of the devs have posted a followup on this, I think that perhaps
this is worth a bug in Bugzilla. If the analysis is valid it needs to be
fixed. If it isn't, one of the devs will probably explain why it should
work as
Actually a bug was already posted and a patch put into trunk.
The devs are silent and stealthy. ;)
Ah! Guess I should read dev before users rather than the other way around!
Loren
Jay Levitt wrote:
[SNIP]
I tried to create a test harness to see if I can replicate this outside
of SA, but for some reason, even though I double-checked the code I
copied from Dns.pm, I'm getting weird results - it's always giving me
the root nameservers, instead of the name servers for each
Jay Levitt wrote:
A quick test shows that indeed, an awful lot of domains are repeatedly
failing in lookup_ns, but that different domains fail at different
times - the domains that repeatedly fail right now were fine last
night in the SA logs.
So it looks like this is something (intermittment)
On Tue, 22 Feb 2005, Andy Jezierski wrote:
Kelson [EMAIL PROTECTED] wrote on 02/22/2005 11:30:46 AM:
Jay Levitt wrote:
I have SA 3.01 running under mimedefang 2.43 with sendmail 8.13.1. At
some point, SA seems to stop doing lookups on the DNSBLs; spam gets
through that is listed in
problem as the discussion in the Spammer
Anti-SURBL tactic thread?
Andy
Possibly, but I think the lots of URI spams are still somewhat
rare, so it should only be an occasional occurrence.
It sounds like this thread SA 3.01 eventually stops noticing
DNSBLs is more likely an installation
On Tuesday, February 22, 2005, 10:25:36 PM, Jay Levitt wrote:
Kelson wrote:
Jay Levitt wrote:
I have SA 3.01 running under mimedefang 2.43 with sendmail 8.13.1.
At some point, SA seems to stop doing lookups on the DNSBLs; spam
gets through that is listed in multiple BLs; if I check
Jeff Chan wrote (quoting Jay Levitt):
Nope, that's not it. I've been throwing debug code in bit by bit.
(More accurately, I've been re-copying the dbg statements as "warns",
because while there's plenty of useful output, there are just too many
un-categorized dbg statements to
On Wednesday, February 23, 2005, 8:38:31 AM, Jay Levitt wrote:
After it's been running for a few hours, the lookup_ns check (which does
a sanity check to make sure we can resolve the nameservers of a
well-known domain) seems to fail. Or, rather, it returns, but with 0
entries in the array.
Jeff Chan wrote:
On Wednesday, February 23, 2005, 8:38:31 AM, Jay Levitt wrote:
I tried to create a test harness to see if I can replicate this outside
of SA, but for some reason, even though I double-checked the code I
copied from Dns.pm, I'm getting weird results - it's
Jay Levitt wrote:
I have SA 3.01 running under mimedefang 2.43 with sendmail 8.13.1. At
some point, SA seems to stop doing lookups on the DNSBLs; spam gets
through that is listed in multiple BLs; if I check manually with
spamassassin -t, it detects the BL entry, even if I run it moments after
Kelson [EMAIL PROTECTED] wrote on 02/22/2005
11:30:46 AM:
Jay Levitt wrote:
I have SA 3.01 running under mimedefang 2.43 with sendmail 8.13.1.
At
some point, SA seems to stop doing lookups on the DNSBLs; spam
gets
through that is listed in multiple BLs; if I check manually with
On Saturday, February 19, 2005, 8:05:05 AM, Jay Levitt wrote:
Just checked.. there is only one resolv.conf on the system, in
/etc/resolv.conf, and it correctly points to my own machine, which runs
a caching named (actually caching for the world, authoritative for my
own domain).
Note that
I have SA 3.01 running under mimedefang 2.43 with sendmail 8.13.1. At
some point, SA seems to stop doing lookups on the DNSBLs; spam gets
through that is listed in multiple BLs; if I check manually with
spamassassin -t, it detects the BL entry, even if I run it moments after
the spam was
On Friday, February 18, 2005, 8:35:35 PM, Jay Levitt wrote:
I have SA 3.01 running under mimedefang 2.43 with sendmail 8.13.1. At
some point, SA seems to stop doing lookups on the DNSBLs; spam gets
through that is listed in multiple BLs; if I check manually with
spamassassin -t, it detects
17 matches
Mail list logo
