--On Tuesday, October 22, 2013 8:56 AM -0400 "Kevin A. McGrail"
<[email protected]> wrote:
On 10/21/2013 4:59 PM, Quanah Gibson-Mount wrote:
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?
Definite opinions.
You need to have one dir that is designed for rules/config files you
create, modify and override. On my system this is:
/etc/mail/spamassassin.
Then you have your default rules location for sa-update which is
/var/lib/spamassassin/<version> dir by default. You really shouldn't
interact with the files in this dir so if you are intermingling them, it
could be very confusing to administer the system.
It sounds a bit like what you inherited predates the concept of sa-update
but I off the cuff, even something like setting LOCALSTATEDIR to
/opt/zimbra/conf/spamassassin/var/lib and DEFRULESDIR to /opt/zimbra/conf
might be better.
That should give you a couple of pre files and a local.cf in
/opt/zimbra/conf/spamassassin and then allow sa-update to run more
cleanly.
Thanks. I believe this configuration dates back to about 2005. ;)
--Quanah
--
Quanah Gibson-Mount
Architect - Server
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
