I installed both patches and still get errors in some of the dnsbl
tests.  Here is a possibly relevant section of t/log/d.dns/1 from a
system where the test succeeded:

 

[27718] dbg: check: running tests for priority: 500

[27718] dbg: async: select found 1 socks ready

[27718] dbg: uridnsbl: query for uribl-example-b.com took 4 seconds to
look up (multi.surbl.org.:uribl-example-b.com)

[27718] dbg: uridnsbl: query for uribl-example-a.com took 4 seconds to
look up (multi.uribl.com.:uribl-example-a.com)

...

[27718] dbg: uridnsbl: query for uribl-example-a.com took 4 seconds to
look up (bl.open-whois.org.:uribl-example-a.com)

[27718] dbg: async: queries completed: 73 started: 0

[27718] dbg: async: queries active: at Fri Jun 15 11:42:27 2007

[27718] dbg: dns: success for 0 of 73 queries

[27718] dbg: rules: running head tests; score so far=18.85

 

And here is the corresponding log where the tests failed:

 

[10362] dbg: check: running tests for priority: 500

[10362] dbg: async: select found no socks ready

[10362] dbg: uridnsbl: query for uribl-example-b.com took 2 seconds to
look up (multi.surbl.org.:uribl-example-b.com)

[10362] dbg: uridnsbl: query for uribl-example-a.com took 2 seconds to
look up (multi.uribl.com.:uribl-example-a.com)

...

[10362] dbg: uridnsbl: query for uribl-example-a.com took 2 seconds to
look up (bl.open-whois.org.:uribl-example-a.com)

[10362] dbg: async: queries completed: 44 started: 0

[10362] dbg: async: queries active: DNSBL-A=10 DNSBL-TXT=19 at Fri Jun
15 11:59:06 2007

[10362] dbg: async: select found no socks ready

[10362] dbg: async: queries completed: 0 started: 0

[10362] dbg: async: queries active: DNSBL-A=10 DNSBL-TXT=19 at Fri Jun
15 11:59:07 2007

[10362] dbg: async: select found no socks ready

...

[10362] dbg: async: queries completed: 0 started: 0

[10362] dbg: async: queries active: DNSBL-A=10 DNSBL-TXT=19 at Fri Jun
15 11:59:27 2007

[10362] dbg: async: escaping: must have lost requests

[10362] dbg: async: aborting remaining lookups

[10362] dbg: dns: success for 44 of 73 queries

[10362] dbg: rules: running head tests; score so far=14.85

 

So what is going on, and why aren't my socks ready? (Sounds like a
laundry problem...)

 

BTW, looking up "134.88.73.210.sb.dnsbltest.spamassassin.org" (one of
the failed lookups) from the command line returns a successful answer
immediately.

 

 

From: Randal, Phil [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 14, 2007 3:41 AM
To: users@spamassassin.apache.org
Subject: RE: "make test" dnsbl tests sporadically fail

 

Possibly related to

 

  http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5511

 

as discussed in the "DNS tests getting aborted" thread?

 

Cheers,

 

Phil

--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK 

 

         

        
________________________________


        From: Rosenbaum, Larry M. [mailto:[EMAIL PROTECTED] 
        Sent: 13 June 2007 22:01
        To: users@spamassassin.apache.org
        Subject: "make test" dnsbl tests sporadically fail

        When I run "make test" for v3.2.1, why do some of the dnsbl
tests sporadically fail?  For instance:

         

        t/dnsbl.....................    Not found: P_2 =
<dns:134.88.73.210.dnsbltest.spamassassin.org> [127.0.0.4]

        # Failed test 1 in t/SATest.pm at line 635

                Not found: P_7 =
<dns:134.88.73.210.sb.dnsbltest.spamassassin.org?type=TXT>

        # Failed test 2 in t/SATest.pm at line 635 fail #2

                Not found: P_4 =
<dns:14.35.17.212.dnsbltest.spamassassin.org> [127.0.0.1]

        t/dnsbl.....................NOK 1# Failed test 3 in t/SATest.pm
at line 635 fail #3

                Not found: P_3 =
<dns:18.13.119.61.dnsbltest.spamassassin.org> [127.0.0.12]

        # Failed test 4 in t/SATest.pm at line 635 fail #4

                Not found: P_5 =
<dns:226.149.120.193.dnsbltest.spamassassin.org> [127.0.0.1]

        # Failed test 5 in t/SATest.pm at line 635 fail #5

        t/dnsbl.....................NOK 2       Not found: P_1 =
<dns:98.3.137.144.dnsbltest.spamassassin.org> [127.0.0.2]

        # Failed test 6 in t/SATest.pm at line 635 fail #6

                Not found: P_6 =
<dns:example.com.dnsbltest.spamassassin.org> [127.0.0.2]

        # Failed test 7 in t/SATest.pm at line 635 fail #7

                Not found: P_15 =  DNSBL_RHS

        t/dnsbl.....................NOK 3# Failed test 8 in t/SATest.pm
at line 635 fail #8

                Not found: P_17 =  DNSBL_SB_FLOAT

        t/dnsbl.....................NOK 4# Failed test 9 in t/SATest.pm
at line 635 fail #9

                Not found: P_18 =  DNSBL_SB_STR

        # Failed test 10 in t/SATest.pm at line 635 fail #10

                Not found: P_16 =  DNSBL_SB_TIME

        # Failed test 11 in t/SATest.pm at line 635 fail #11

        t/dnsbl.....................NOK 5       Not found: P_10 =
DNSBL_TEST_DYNAMIC

        # Failed test 12 in t/SATest.pm at line 635 fail #12

                Not found: P_12 =  DNSBL_TEST_RELAY

        # Failed test 13 in t/SATest.pm at line 635 fail #13

        t/dnsbl.....................NOK 6       Not found: P_11 =
DNSBL_TEST_SPAM

        # Failed test 14 in t/SATest.pm at line 635 fail #14

                Not found: P_8 =  DNSBL_TEST_TOP

        # Failed test 15 in t/SATest.pm at line 635 fail #15

                Not found: P_9 =  DNSBL_TEST_WHITELIST

        t/dnsbl.....................NOK 7# Failed test 16 in t/SATest.pm
at line 635 fail #16

                Not found: P_14 =  DNSBL_TXT_RE

        # Failed test 17 in t/SATest.pm at line 635 fail #17

                Not found: P_13 =  DNSBL_TXT_TOP

        t/dnsbl.....................NOK 8# Failed test 18 in t/SATest.pm
at line 635 fail #18

        t/dnsbl.....................NOK 9Output can be examined in:
log/d.dns/1

        t/dnsbl.....................FAILED tests 1-18

                Failed 18/23 tests, 21.74% okay

         

        If I run t/dnsbl.t later, a smaller number of the subtests fail.
If I repeat it later, a different set of dnsbl subtests fail.

         

        There is nothing obviously wrong with the DNS server.  What
causes this problem?

Reply via email to