On Thu, 2013-04-18 at 14:08 +0100, RW wrote: > On Wed, 17 Apr 2013 21:40:33 +0100 > John Horne wrote: > > > Hello, > > > > We are running SpamAssassin 3.3.2 on a CentOS 5.9 server. sa-update > > runs via a daily cron job, and we have modified that to run > > sa-compile as well. However, there are some questions: > > > > sa-compile is run without any options. So what I am unsure of is > > whether our local rules (in /etc/mail/spamassassin/local-spam.cf) are > > compiled as well or not? > > They are for me, but it's easy enough to test. Find a few *simple* > local body rules and grep for them under the "compiled" directory. > > > The man page for sa-compile says that the '--siteconfigpath' option > > defaults to /etc/mail/spamassassin which I assume implies that our > > local rules would be compiled? > > > > If they are, and we want to change our local rules, then I assume we > > would have to re-compile all the rules before restarting SpamAssassin? > > That's the received wisdom, but I've never seen a definitive reason > why. Compiled rules are intended to co-exit with non-compiled rules, > and from my limited testing, rules behave correctly when they are added, > removed or modified without recompiling. However I have seen one case > where a rule wasn't working properly and was apparently fixed by a > recompile, but I suspect that was a specific bug. > Thanks for the reply. I (now) gather that compilation actually only applies to 'body' rules. We don't have too many of those, so generally for non-body local rules a simple restart of SA works immediately. I suspect that for the body rules we never noticed that they only started to be hit the following day (recompiling of rules occurs each night). We would have simply assumed that the rule didn't have any hits until that time. It is, of course, something we will now bear in mind :-)
John. -- John Horne, Plymouth University, UK Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
