SA RBL Failing

Brady A. Tucker batucker at ICNET.NET
Thu May 22 22:39:49 IST 2003

Dropped back to SA 2.55 with no help...

I think I may have found the issue with this, is
unresolvable,  therefore when spamcop ( is on the MailScanner
rbl list it fails, timeout doesn't seem to work since it doesn't resolve ?
Suspecting this is what's causing SA to fail is well, what do I put in
spam.assassin.prefs.conf or how do I disable this one RBL in spam assassin
to test this ?   All other RBL addresses are resolving fine,  so I'm not
sure what's up with that yet.

You can see from the dig... 0 answers...

[root at mailgw MailScanner]# dig

; <<>> DiG 9.2.1 <<>>
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20630
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;                        IN      A

;; Query time: 534 msec
;; WHEN: Thu May 22 16:28:47 2003
;; MSG SIZE  rcvd: 32

                                      Brady A. Tucker
                                      Internet Complete! inc.

-----Original Message-----
From: MailScanner mailing list [mailto:MAILSCANNER at JISCMAIL.AC.UK]On
Behalf Of Matt Kettler
Sent: Thursday, May 22, 2003 3:48 PM
Subject: Re: SA RBL Failing

At 02:58 PM 5/22/2003 -0500, Brady A. Tucker wrote:
>n spam.assassin.prefs.conf   If uncomment skip_rbl_checks in
>spamassassin...  it just sits there once MailScanner has it's 5 batches (I
>have it set to 25 messages per batch),  doesn't seem to ever time out..
>whether I set rbl_timout to 1 or 10 or 40.  I've messed with
>batches/messages  setting them both to one just as a debug measure with no

If you're doing production and want reliable performance you should NOT be
running the 2.60 CVS version of spamassassin.. that's a development
snapshot build and should be considered alpha-release quality at absolute

I know for fact that the 2.60 development is currently reworking the DNS
code, so the fact that RBLs aren't timing out isn't surprising.. that code
is being changed as we speak, so that feature might be broken.. heck, it
might actually have been fixed already..

I'd strongly suggest using the stable release (2.55) if "alpha release
bugs" aren't acceptable..

>   [root at mailgw log]# spamassassin -V
>   SpamAssassin version 2.60-cvs

More information about the MailScanner mailing list