On Sun, 21 Apr 2013 19:47:49 +0100
John Horne wrote:
> > 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 modifie
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
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.
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/spam
