Re: Help with KAM rule set setup

[email protected] Mon, 16 Mar 2026 12:24:34 +0100
Newsgroups gmane.mail.spam.spamassassin.general
Message-ID <[email protected]>
On 3/13/26 5:54 PM, Jared Hall via users wrote:
> A blast from the past.  AFAIK, HashBL came out with 3.4.2.
> 
> Think you're going to have to contact KAM directly for resolution.
> 
`P@yp@l` escape issue is now fixed in latest KAM.cf version.
HashBL came out with 3.4.2, those rules have `ifplugin` guards and won't load if HashBL is not loaded.
SpamAssassin 3.4.0 also has security issues, it would be better to update to a supported version.
  Cheers
   Giovanni

> 
> TTFN,
> 
> -- Jared Hall
> [email protected]
> Available for hire.
> 
> 
> On 3/13/2026 12:07 PM, Scott Techlist wrote:
>>
>> Redhat/Centos 8
>>
>> Spamassassin 3.4.0 running on Perl version 5.16.3
>>
>> Normally used via amavisd
>>
>> Trying unsuccessfully to implement/install the KAM rule set.
>>
>> Novice spamassassin user.    I have used it for years but haven’t had to configure much except a few custom rule sets and scores.  I’m now trying to use the KAM rule set.
>>
>> When I run the last step:
>>
>> sa-update --gpgkey 24C063D8 --channel kam.sa-channels.mcgrail.com
>>
>> That results in:
>>
>> rules: failed to run SNB_HASHBL_FREEMAIL test, skipping:
>>
>>         (Can't locate object method "check_hashbl_emails" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 1571) line 45.
>>
>> )
>>
>> Possible unintended interpolation of @L in string at /tmp/.spamassassin1602K8J4hetmp/KAM.cf, rule __KAM_PHISH_INVOICE2_1, line 1.
>>
>> rules: failed to compile Mail::SpamAssassin::Plugin::Check::_body_tests_0_8, skipping:
>>
>>         (Global symbol "@L" requires explicit package name at /tmp/.spamassassin1602K8J4hetmp/KAM.cf, rule __KAM_PHISH_INVOICE2_1, line 1.)
>>
>> channel: lint check of update failed, channel failed
>>
>> I also added this .conf file:
>>
>> cat /etc/mail/spamassassin/channel.d/KAM_channel.conf
>>
>> CHANNELURL=kam.sa-channels.mcgrail.com
>>
>> KEYID=24C063D8
>>
>> # Ignore everything below.
>>
>> return 0
>>
>> <snipped KEY BLOCK>
>>
>> Any easy fix to this?
>>
>> Thanks, Scott
>>
>
OpenPGP_signature.asc (application/pgp-signature, 840 B)
-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEEqg3TnG6R3qYMxl94+r7qCYlyWOUFAmm36HMFAwAAAAAACgkQ+r7qCYlyWOVv
WRAAteBAExQ0SU29Y5NrPsKMM5V7f79hIwC3+Yk55MIR79y9YBeltB5znnIf7WBC+76SP8Ym6iQz
53vYBMoOBzmQEFP15nIgj2G205vnP3/1BWX4Os2KL/Vyckn65djSekG9nTDRxizX/67vusfGjkjz
74Y0rxMa2ELgeqOvPRA/1WypnjgkAbZrQqKdljBbTc5zhn3RSe7IWCDCh8WWOCpVfRsqhffpg4ol
d+ESc7RB3Nr1YgXVW5EePIeB9kUrmnLEV0umuw4AUfUGNUE8q+arMBwHT1YsVQcJtJkbYUv28k77
nL1+vS9OYWtfo9FKMS/4ePF1h68tQmmR+DTWGHcHFasxCssd1BTg9TB4CTBSaHIuYXw7vooKI99B
h8m7261sJNki5RjF3HgXEgHSwmYc9RiAeuOl9RdwIUZlxmSrDrtoW+1Xv2VJN7iBnlqOxAlwp3sc
FCT1sXjH3xDydkZcsZQVPbRpFMerquS7zEBVRf9I0kAWp7bYyM78middgkcrAu0gH4qg0FBaGE7M
U3dZXXz+l8rkC8ccFCTayLL1+0kTwFaD+yKhDhRt5CbEank3q1We/xpB0G32IlgDKZBGblCmm5k6
Hslg8GMJy/D0CtDakDLkG9anne3RFv5AxaJ2sfdsMf9hscd+vnrz4Z9aH4f+YPHgHMw++i4g9EkS
3jM=
=/FLM
-----END PGP SIGNATURE-----