--On Tuesday, October 22, 2013 12:18 AM +0200 Karsten Bräckelmann
<[email protected]> wrote:
By setting $DEF_RULES_DIR to the same value as $LOCAL_RULES_DIR, placing
stock rules in what's supposed to be strictly for site-specific conf,
you override the fresh rules pulled by sa-update.
I'm not positive that is correct -- When sa-update runs, it pulls down the
rules and adds a cf file to include them, with the name
updates_spamassassin_cf. Given load order seems to be alphabetically
dependent, it should still override, I'm hoping. ;)
I'm wondering if there's a better layout strategy than this. I.e., keep
the .pre files in a specific location (/opt/zimbra/conf/spamassassin)
and keep the rule files + updates in /opt/zimbra/data/spamassassin (our
generalized data location for app specific data).
Any opinions on that?
Yes, definitely.
Ok, added to my to-do list. ;)
--Quanah
--
Quanah Gibson-Mount
Architect - Server
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration