On Mar 23, 2006, at 06:15 , Justin Mason wrote:
I agree -- that should be removed. Could you open a new bugzilla
bug about this?
Submitted bug ID 4842. Attached a proposed patch to the bug.
Thank you.
- Jason Parsons
Jason Parsons writes:
>
> >> urirhssub SAFF_EXAMPLE rbl.example.com. A 127.0.0.8
> >
> > urihssub expects just 8, not 127.0.0.8
>
> Sorry for the delay in responding. Your description, while it seems
> to match the current code, doesn't match the documentation:
>
> > subtest is the s
urirhssub SAFF_EXAMPLE rbl.example.com. A 127.0.0.8
urihssub expects just 8, not 127.0.0.8
Sorry for the delay in responding. Your description, while it seems
to match the current code, doesn't match the documentation:
subtest is the sub-test to run against the returned data. Th
Jason Parsons wrote:
>
> I'm using an internal URIBL, configured like so:
>
> urirhssub SAFF_EXAMPLE rbl.example.com. A 127.0.0.8
> body SAFF_EXAMPLE eval:check_uridnsbl('SAFF_EXAMPLE')
> describe SAFF_EXAMPLE Example RBL hit 8
>
> Running with the above configuration causes spamd
I'm using an internal URIBL, configured like so:
urirhssub SAFF_EXAMPLE rbl.example.com. A 127.0.0.8
body SAFF_EXAMPLE eval:check_uridnsbl('SAFF_EXAMPLE')
describe SAFF_EXAMPLE Example RBL hit 8
Running with the above configuration causes spamd to log:
warn: Argument "127.0.0
