SOLVED Spamassassin warning and missing rules?

EneTar

Well-Known Member
Dec 19, 2015
156
12
18
Greece
cPanel Access Level
Root Administrator
I have enabled in WHM -> Exim Configuration the rulesets

Code:
BAYES_POISON_DEFENSE Apache SpamAssassin™
Passive OS Fingerprinting for Apache SpamAssassin™
KAM Apache SpamAssassin™ ruleset
Apache SpamAssassin™ ruleset that cPanel uses on cpanel.net
Running
Code:
/usr/local/cpanel/3rdparty/bin/spamassassin -D --lint 2>&1 | grep -Ei '(failed|undefined dependency|score set for non-existent rule)'
I get
Code:
Feb 11 11:46:30.065 [28410] dbg: diag: [...] module not installed: Net::CIDR::Lite ('require' failed)
Feb 11 11:46:30.065 [28410] dbg: diag: [...] module not installed: Net::Patricia ('require' failed)
Feb 11 11:46:30.918 [28410] dbg: config: warning: score set for non-existent rule HEADER_HOST_IN_BLACKLIST
Feb 11 11:46:30.918 [28410] dbg: config: warning: score set for non-existent rule RCVD_IN_BRBL_LASTEXT
Feb 11 11:46:30.919 [28410] dbg: config: warning: score set for non-existent rule FILL_THIS_FORM_LOAN
Feb 11 11:46:30.919 [28410] dbg: config: warning: score set for non-existent rule FILL_THIS_FORM_FRAUD_PHISH
Feb 11 11:46:30.919 [28410] dbg: config: warning: score set for non-existent rule URIBL_AB_SURBL
Feb 11 11:46:30.920 [28410] dbg: config: warning: score set for non-existent rule RCVD_IN_CBL
Feb 11 11:46:30.920 [28410] dbg: config: warning: score set for non-existent rule DUP_SUSP_HDR
Feb 11 11:46:30.920 [28410] dbg: config: warning: score set for non-existent rule URIBL_JP_SURBL
Feb 11 11:46:30.920 [28410] dbg: config: warning: score set for non-existent rule HEADER_HOST_IN_WHITELIST
Feb 11 11:46:30.941 [28410] dbg: config: warning: no description set for KAM_RPTR_FAILED
Feb 11 11:46:31.498 [28410] dbg: rules: CBJ_GiveMeABreak merged duplicates: KAM_IFRAME KAM_RAPTOR KAM_RPTR_FAILED KAM_RPTR_PASSED KAM_RPTR_SUSPECT
Feb 11 11:46:32.082 [28410] dbg: rules: meta test KAM_GRABBAG9 has undefined dependency 'MALFORMED_FREEMAIL'
Feb 11 11:46:32.087 [28410] dbg: rules: meta test KAM_COLLEGE has undefined dependency '__KAM_URIBL_PCCC'
Feb 11 11:46:32.089 [28410] dbg: rules: meta test KAM_SALE has undefined dependency 'BODY_8BITS'
Feb 11 11:46:32.090 [28410] dbg: rules: meta test MULTI_FORGED has undefined dependency 'FORGED_GMAIL_RCVD'
Feb 11 11:46:32.091 [28410] dbg: rules: meta test KAM_CREDIT2 has undefined dependency '__KAM_URIBL_PCCC'
Feb 11 11:46:32.091 [28410] dbg: rules: meta test JMQ_CONGRAT has undefined dependency 'HK_SPAMMY_FILENAME'
Feb 11 11:46:32.093 [28410] dbg: rules: meta test KAM_PHISH2 has undefined dependency '__KAM_URIBL_PCCC'
Feb 11 11:46:32.099 [28410] dbg: rules: meta test KAM_BAD_DNSWL has undefined dependency 'IN_BRBL'
Feb 11 11:46:32.099 [28410] dbg: rules: meta test KAM_BAD_DNSWL has undefined dependency 'RCVD_IN_BRBL_RELAY'
Feb 11 11:46:32.099 [28410] dbg: rules: meta test KAM_BAD_DNSWL has undefined dependency '__KAM_URIBL_PCCC'
Feb 11 11:46:32.099 [28410] dbg: rules: meta test KAM_BAD_DNSWL has undefined dependency 'KAM_MESSAGE_EMAILBL_PCCC'
Feb 11 11:46:32.099 [28410] dbg: rules: meta test KAM_BAD_DNSWL has undefined dependency 'RCVD_IN_HOSTKARMA_W'
Feb 11 11:46:32.101 [28410] dbg: rules: meta test CONFIRMED_FORGED has undefined dependency 'FORGED_GMAIL_RCVD'
Feb 11 11:46:32.103 [28410] dbg: rules: meta test KAM_GOOGLE2 has undefined dependency 'HK_SPAMMY_FILENAME'
Feb 11 11:46:32.106 [28410] dbg: rules: meta test DIGEST_MULTIPLE has undefined dependency 'DCC_CHECK'
Feb 11 11:46:32.117 [28410] dbg: rules: meta test KAM_BADPDF2 has undefined dependency 'KAM_BADPDF'
Feb 11 11:46:32.117 [28410] dbg: rules: meta test KAM_BADPDF2 has undefined dependency 'KAM_BADPDF1'
Code:
/usr/local/cpanel/3rdparty/bin/spamassassin -V
SpamAssassin version 3.4.1
  running on Perl version 5.24.1
Am I missing any ruleset?
in /etc/mail/spamassassin there are the following:
Code:
BAYES_POISON_DEFENSE.cf
init.pre
local.cf.rpmsave
v312.pre
v320.pre.rpmsave
CPANEL.cf
KAM.cf
local.cf
P0f.cf
v310.pre
v320.pre
v330.pre
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,202
363
Hello,

I see the same debug output when running that command on a test system where SpamAssassin is working as intended. It's not an indication that your rules are not enabled. Are you experiencing a specific issue with SpamAssassin?

Thank you.
 

EneTar

Well-Known Member
Dec 19, 2015
156
12
18
Greece
cPanel Access Level
Root Administrator
Not anything in particular other than those warnings. Spamassassin works on my system. However I believe that all those rules and the rules that depend on those are not evaluated since they are missing.

I don't think that this particular debug output should be normal behavior. Perhaps you would like to have a look with your team.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,913
2,202
363
Hello,

This is noted in the output of the "/usr/local/cpanel/scripts/sa-update_wrapper" command:

Code:
[*] Please note that 'IO::Socket::IP' and 'Net::Patricia' are not needed by our implementation of SpamAssassin.
[*] The warnings related to them can be safely ignored.
Additionally, the output you noticed included a reference to Net::CIDR::Lite. You can also ignore that warning because Net::CIDR::Lite is only used with a SpamAssassin plugin that we don't enable.

As far as the rules/scores warning, here's part of a response from one of our Technical Analysts on a similar inquiry opened as a support ticket:

I have checked this for you, and it appears that the warnings are not something that should prevent SpamAssassin from operating. In fact, they appear to be only informational. For example, the "URI_OBFU_WWW" rule was downloaded automatically by SpamAssassin as part of its update, and there are definitions for how something triggering "URI_OBFU_WWW" should be marked. However, there are no rules provided in the update to say what is required for this to occur. There are also notices that certain rules do not have a description. This is not necessary for the rules to function, and is only used for helping to explain what the rule does. These descriptions are up to the rule maintainers to provide.
Thank you.