mikea writes:
>A-*Ha*! And then each header is checked against the DNSbl named
>'zone', I take it, with IP addresses of the form a.b.c.d being
>reversed to d.c.b.a first, so that the lookup is done against
>d.c.b.a.zone.
>
>TYVM. My search for doc on this apparently sidestepped something
>
On Tue, Jul 22, 2003 at 11:44:38AM -0700, Justin Mason wrote:
> It works like:
> header CHECK_DNSBL_NAMErbleval:check_rbl('setname', 'zone')
> describe CHECK_DNSBL_NAME Insert CHECK_DNSBL_NAME description here
> tflags CHECK_DNSBL_NAMEnet
> header CHECK_RESULTS rbleval:check_r
mikea writes:
>I _think_ that the rules are constructed like this in the general
>case, but would really appreciate guidance:
>
>#==
>header CHECK_DNSBL_NAMErbleval:check_rbl('RESULT_NAME', 'DNSBL_SERVER_NAME')
>describe CHECK_DNSBL_NAME Inser
I'm looking at adding a local DNSBL, served out of one of the
nameservers here.
Let's say that I want to look up an IP address, a.b.c.d, on
my server bl.odot.org, and want to add 5 points for entries
that map to 127.0.0.4.
Here:
#==
header ODOT_RCVD_B
