Marc MERLIN wrote:
> Ok, so SA 2.21 sorts the rules by score in an attempt to stop scanning the
> message if the user specified a scan threshold
> Unfortunately, this completely breaks rule dependencies. Granted, those are mostly
>(only?) RBL rules for now, but rule dependency is needed somewhere.
>
> Let me quote 20_head_tests.cf:
>
> # X prefix is so that these are run after RCVD_IN_*. tests are run in
> # alphanumerically-sorted order. (These used to be Osirusoft.com-specific, but
> # now, other DNSBLs are using the same convention.)
> header X_OSIRU_SPAM_SRC eval:check_rbl_results_for('relay', '127.0.0.4')
> describe X_OSIRU_SPAM_SRC DNSBL: sender is Confirmed Spam Source
>
>
> I just so happens that I spent the last week overhauling DNS RBL checks so
> that they are done properly wrt DUL checks and checks across multiple RBLs
> (see my proposed patch in the next message).
> Of course, the new sort code not only breaks the current behavior, but also
> breaks my patch completely
See what I did for the YELLING rules. It's just a simple cache system,
so that the depending rule calls the dependant rule, and the cache
ensures it only gets called once (sort of like memoizing the function).
Matt.
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
