On Tue, 2013-10-22 at 17:03 -0700, Quanah Gibson-Mount wrote:
> --On Wednesday, October 23, 2013 1:53 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?
> with /opt/zimbra/conf/updates_spamassassin_org.cf added for loading the
> rules.
(Missed a "spamassassin/" here. Did you really, repeatedly type in that
string manually?)
With a layout like that, having an un-versioned SA update channel inside
your site-specific $LOCAL_RULES_DIR, you are indeed lucky enough to have
it just work. Because alphabet.
> They are definitely not equal values:
>
> ./Mail/SpamAssassin.pm: $self->{LOCAL_STATE_DIR} ||=
> '/opt/zimbra/data/spamassassin';
> ./Mail/SpamAssassin.pm: $self->{LOCAL_RULES_DIR} ||=
> '/opt/zimbra/conf/spamassassin';
>
> but /opt/zimbra/data/spamassassin doesn't even exist. :P
>
> I'll definitely spend some time on getting this mess sorted out.
Good. As should be clear by now, these really should be 3 distinct
directories with different precedence.
--
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; }}}
