Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

DNSRBL config

2006-11-13 by BERTRAND Joël

Hello,

	I'm trying to configure dnsrbl in 3.0rc7 without any success. I have 
added in configure script a -lbind to build the package with 
--enable-dnsrbl (and of course thread-safe). I have started 
milter-greylist with verbose option and I obtain :

acl 243 greylist dnsrbl "SORBS-HTTP" [delay 3600]
acl 247 greylist dnsrbl "SORBS-SOCKS" [delay 3600]
acl 251 greylist dnsrbl "SORBS-MISC" [delay 3600]
acl 255 greylist dnsrbl "SORBS-SMTP" [delay 3600]
acl 259 greylist dnsrbl "SORBS-SPAM" [delay 3600]
acl 262 greylist dnsrbl "SORBS-WEB" [delay 3600]
acl 266 greylist dnsrbl "SORBS-BLOCK" [delay 3600]
acl 270 greylist dnsrbl "SORBS-ZOMBIE" [delay 3600]
acl 274 greylist dnsrbl "SORBS-DUL" [delay 3600]
acl 276 greylist [delay 600] default

	Good. But with tcpdump, I don't see any request to sorbs zone. Delay is 
always equal to 600 s. Thus, I have added a watchpoint in dnsrbl.c :

         anslen = res_nquery(&res, req, C_IN, qtype, ans, NS_MAXMSG + 1);
         mg_log(LOG_ERR, "DNSRBL: %d\n", anslen);
         if (anslen == -1)
                 goto end;

	In the log, I can see :

Nov 13 09:40:24 rayleigh milter-greylist: DNSRBL: -1
Nov 13 09:40:28 rayleigh milter-greylist: DNSRBL: -1
Nov 13 09:40:28 rayleigh milter-greylist: DNSRBL: -1
Nov 13 09:40:28 rayleigh milter-greylist: DNSRBL: -1
Nov 13 09:42:52 rayleigh milter-greylist: DNSRBL: -1
Nov 13 09:44:51 rayleigh milter-greylist: DNSRBL: -1
Nov 13 09:45:17 rayleigh milter-greylist: DNSRBL: -1
Nov 13 09:45:59 rayleigh milter-greylist: DNSRBL: -1
Nov 13 09:46:55 rayleigh milter-greylist: DNSRBL: -1
Nov 13 09:47:50 rayleigh milter-greylist: DNSRBL: -1
Nov 13 09:49:01 rayleigh milter-greylist: DNSRBL: -1

	All returned values are -1 (and no one request to sorbs...). Any idea ?

	Regards,

	JKB

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.