https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6020
--- Comment #1 from Justin Mason <[EMAIL PROTECTED]> 2008-11-24 07:36:08 PST --- Created an attachment (id=4395) --> (https://issues.apache.org/SpamAssassin/attachment.cgi?id=4395) implementation for 3.3.0 AXB made me do it. Here's the implementation of that... =item urinsrhsbl NAME_OF_RULE rhsbl_zone lookuptype Perform a RHSBL-style domain lookup against the contents of the NS records for each URI. In other words, a URI using the domain C<foo.com> will cause an NS lookup to take place; assuming that domain has an NS of C<ns0.bar.com>, that will cause a lookup of C<bar.com.uriblzone.net>. Note that hostnames are stripped from both the domain used in the URI, and the domain in the lookup. C<NAME_OF_RULE> is the name of the rule to be used, C<rhsbl_zone> is the zone to look up domain names in, and C<lookuptype> is the type of lookup (B<TXT> or B<A>). Note that, as with C<urirhsbl>, you must also define a body-eval rule calling C<check_uridnsbl()> to use this. =item urinsrhssub NAME_OF_RULE rhsbl_zone lookuptype subtest Specify a RHSBL-style domain-NS lookup, as above, with a sub-test. C<NAME_OF_RULE> is the name of the rule to be used, C<rhsbl_zone> is the zone to look up domain names in, and C<lookuptype> is the type of lookup (B<TXT> or B<A>). C<subtest> is the sub-test to run against the returned data; see <urirhssub>. Note that, as with C<urirhsbl>, you must also define a body-eval rule calling C<check_uridnsbl()> to use this. Checked into 3.3.0 trunk: : 96...; svn commit -m "bug 6020: add 'urinsrhsbl' and 'urinsrhssub' rule types to URIDNSBL plugin, allowing listing of NS record strings in URIBL blocklists" Sending lib/Mail/SpamAssassin/Plugin/URIDNSBL.pm Sending t/data/spam/dnsbl.eml Sending t/uribl.t Transmitting file data ... Committed revision 720211 ( https://svn.apache.org/viewcvs.cgi?view=rev&rev=720211 ). -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
