--On Saturday, October 26, 2013 2:01 AM +0200 Karsten Bräckelmann
<[email protected]> wrote:
OK, you have even more problems...
On Fri, 2013-10-25 at 09:43 -0700, Quanah Gibson-Mount wrote:
--On Wednesday, October 23, 2013 3:01 AM +0200 Karsten Bräckelmann
wrote:
>> > Well, what did you set $LOCAL_STATE_DIR to?
>
>> There's no versioned data anywhere. ;)
>>
>> There is only /opt/zimbra/conf/spamassassin
>>
>> (and after sa-update)
>>
>> /opt/zimbra/conf/spamassassin/updates_spamassassin_org/
>
> That... is rather strange. Without actually checking the code, I
> believe sa-update (and SA in general) adds the version number. Is
> there any custom patch to change that behavior?
No, we don't patch SA.
The build runs:
$(PERL) -I$(DEST_LIB_DIR) Makefile.PL
PREFIX=$(ZIMBRA_HOME)/zimbramon LIB=$(ZIMBRA_HOME)/zimbramon/lib
DATADIR=$(ZIMBRA_HOME)/conf/spamassassin
CONFDIR=/opt/zimbra/conf/spamassassin
DATADIR and CONFDIR are synonyms for DEFRULESDIR and LOCALRULESDIR
respectively.
Given previous statements, home too is /opt/zimbra, and both are using
the same directory. This is an issue, because according to the docs, the
files in DEFRULESDIR are removed when SA is installed. See the PACKAGING
docs.
No problem if used as intended, i.e. for stock rules (package). In your
case that also will flame any custom configuration or rules.
Well... Since we run SA via amavis, custom rules are stored in
/opt/zimbra/conf/sa, and Amavis loads them with:
$sa_siteconfigpath = '/opt/zimbra/conf/sa';
So custom rules are still supported. ;)
However, clearly this entire thing needs a redesign. Hopefully I can get
to it next week.
--Quanah
--
Quanah Gibson-Mount
Architect - Server
Zimbra, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
