On Wed, 2021-10-20 at 11:50 -0500, Jerry Malcolm wrote: > is working as it should. I'm pretty confident I've got the basic SA > function working. But along with the bayes issue from a couple of posts > back, I can't seem to make the KAM.cf file get involved. In previous > installations, I would see a lot of KAM rules showing up in the spam > reports on emails. I also have written some rules on my own and put I'm > not seeing any of my rules get hit. > Have you tried starting spamd with the debugging option ( -D or --debug ) set?
The output will be quite large, but it will at least show you which configuration files are being opened and, in the case of any that are not being opened, where its looking for them. > I created a rule that triggers if the subject or sender is my company > name. I sent an email from an outside email address and specifically > added this name to the subject (and it's also in my sender email > address). Nothing in the spam report. > That sounds like the .cf file containing your rule is not being read. Debugging output should tell you why. FWIW I found it helpful to have a secondary copy of SA installed on another system but using the same set of file names etc as the 'production' version. I run that by starting spamd and feeding it test messages by running something like "spamc <test*.txt" as part of a test script. This way I could get SA set up as I wanted it and can develop and test private rules etc. Then, because both SA instances have configuration files etc. stored in an identical set of directories, its easy to properly test new rules and configuration changes on the development system before copying the file set to the production system and restarting it to make the changes active. I also all keep all my test messages. This makes it easy to run regression tests on the development system after any major changes have been made. Another good idea is to keep everything in the development system under version control. I used to use CVS and now git for this. Of course my production SA system is backed up as part of regularly scheduled system backups. Some of this may sound like unnecessary work, but a fully customised and tuned SA installation is complex enough to make this approach worthwhile in the long run, particularly the ability to run regression tests on your current configuration and rule set. Martin
