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.
> LOCALSTATEDIR=$(ZIMBRA_HOME)/data/spamassassin; \
>
> Although interestingly I never create or use /opt/zimbra/data/spamassassin.
> :P
So you are running sa-update always with --updatedir specified on the
command line?
That would explain the last pieces of the puzzle -- this directory not
existing, and the weird un-versioned path as per above. Without patching
the code, --updatedir is the only way to create that mess. Otherwise
sa-update would create LOCALSTATEDIR/3.xxx.yyy/.
--
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
