snowcrash+spamassassin writes: > some questions about sa-compile usage: > > (1) how do we verify that the compiled rules are working? is a > 'healthy' --lint sufficient?
Well, it's a bit tricky -- run a --lint, and look out for lines like this: [15144] dbg: rules: running one_line_body tests; score so far=0 [15144] dbg: zoom: run_body_fast_scan for body_0 start [15144] dbg: zoom: run_body_fast_scan for body_0 done note btw that you need to have this line uncommented in v320.pre: loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody > (2) how do/should we meaure the improved (hopefully) performance due > to the compiled rules? Compare the scan times for a collection of ham and spam mails. they should be faster ;) > (3) do compiled rules automatically take precedence over uncompiled > rules? or, must we remove the uncompiled rules from the rule path? > i'm guessing it's done auto-magically ... It's automatic. > (4) should (must?) we run sa-compile at every rule update? e.g., if > we're sa-update'ing once/hr, running sa-compile hourly is more than a > bit cpu intensive. > > (5) does sa-compile detect diffs/changes between runs and only compile > changes? or does it recompile ALL available rules each time? It'll always recompile fully. However sa-update will not exit with status "0" unless it downloads an update, so you can do: sudo sa-update && sudo sa-compile && sudo /etc/init.d/spamassassin reload --j.
