So AXB pointed out some issues a while back that I wanted to give some
pointers to others if they want to expand on them while I'm building rc4:
First, Plugin/WLBLEval:
blacklist_uri_host example.net
blacklist_uri_host somehost.example.net
whitelist_uri_host example.org
whitelist_uri_host somehost.example.org
KAM: This appears to be already documented in Conf.pm in pod format so I
didn't add more.
Second, Additions
Disable lookups for a specific DNS list (instead of zeroing out rules)
dns_query_restriction deny someBL.example.org
KAM: This appears to be already documented in Conf.pm in pod format so
again, I didn't add more.
Third, if possible some minimal rule samples for:
"added the following sub-options to the tflags setting"
autolearn_force
maxhits=N
ips_only
domains_only
a
ns
A lot of features like these remain unused because they're either
very hidden or not loudly documented with sample rules.
KAM: I found these to be documented fairly well in Conf.pm and in
URIDNSBL.pm but I've taken a pass at cleaning up and adding an example
for maxhits/multiple.
I've also clarified autolearn_force by adding debug output. The output
will now tell you what rules were flagged autolearn_force as well as
telling you autolearn_force status yes/no if the auto-learn is yes.
Jan 10 18:01:57.661 [21198] dbg: learn: auto-learn: autolearn_force
flagged for a rule. Removing seperate body and head point threshold.
Body Only Points: 0 (-99 req'd) / Head Only Points: 13.626 (-99 req'd)
Jan 10 18:01:57.661 [21198] dbg: learn: auto-learn: autolearn_force
flagged because of rule(s): AUTOLEARNTEST_FROM_HEADER
Jan 10 18:01:57.661 [21198] dbg: learn: auto-learn? yes, spam (13.626 >
12) autolearn_force=yes
Additionally, should also now build things status lines like:
X-Spam-Status: Yes, score=6.0 required=5.0 tests=AUTOLEARNTEST_BODY,
RP_MATCHES_RCVD,T_FSL_HELO_NON_FQDN_2,T_HEADER_FROM_DIFFERENT_DOMAINS,
T_MSGID_NOFQDN2,T_NOT_A_PERSON autolearn=spam autolearn_force=yes
(AUTOLEARNTEST_BODY) version=3.4.0-rc3
This closed bug 5503. As that was a header change, I considered it a
blocker for 3.4.0.
Regards,
KAM
