On Sat, 5 Sep 2020, Rajesh M wrote:
dear friends,
had a few questions
1) what is the sequence based on which the rules are processed ?
is there any documentation on this ?
how is the rule number example 20_dnsbl_tests.cf or 25_uribl.cf related to the
sequence of rule processing ?
Are you asking about rule sequencing or configuration file sequencing?
"20_dnsbl_tests.cf" is a configuration file which contains zero or more rules.
During startup spamassassin reads all configuration files that are found in a
list of specific directories (which are distro dependent). The directories are
searched in list order for configuration files (name.cf), the files are read in
lexical order.
So if you have a rule (EG: "MY_RULE_2") in file 20_my_rules.cf and another
instance of "MY_RULE_2" in 99_my_rules.cf (in the same directory) the "99" file
will be read after the "20" file and the latter definition of "MY_RULE_2" will
over-ride (replace) the one from "20".
Also the system provided rules directories are processed before the user
supplied directories (intentionally) so a user can over-ride a system rule if
they don't like how that particular rule works.
See:
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/WhereDoLocalSettingsGo
Once all the rules are read and parsed spamassassin has an internal order to how
specific rules get run.
--
Dave Funk University of Iowa
<dbfunk (at) engineering.uiowa.edu> College of Engineering
319/335-5751 FAX: 319/384-0549 1256 Seamans Center, 103 S Capitol St.
Sys_admin/Postmaster/cell_admin Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
