On Wed, 2008-10-15 at 17:55 -0400, Kris Deugau wrote:
> Matt Kettler wrote:
> > You can always do a relative score adjust.. SA supports that you know:
> >
> > score URIBL_BLACK (1.5)
> >
> > Will take whatever the existing score is and add 1.5 to it.
>
> ... but this doesn't work in rule channels pulled in by sa-update. :(
>
> (You *can* have "score RULE newvalue" entries in a channel ruleset, but
> you can't use the score adjustment mechanism as above in a channel ruleset.)
Why would that be? The configuration order looks exactly as expected.
Site pre files, sys pre files, default rules (sa-update), site rules
(including your local adjustments), user prefs. See the debugging output
below.
guenther
dbg: config: using "/etc/mail/spamassassin" for site rules pre files
dbg: config: read file /etc/mail/spamassassin/init.pre
dbg: config: read file /etc/mail/spamassassin/v310.pre
dbg: config: read file /etc/mail/spamassassin/v312.pre
dbg: config: read file /etc/mail/spamassassin/v320.pre
dbg: config: using "/var/lib/spamassassin/3.002005" for sys rules pre files
dbg: config: using "/var/lib/spamassassin/3.002005" for default rules dir
dbg: config: read file
/var/lib/spamassassin/3.002005/updates_spamassassin_org.cf
dbg: config: using "/etc/mail/spamassassin" for site rules dir
dbg: config: read file /etc/mail/spamassassin/foo.cf
[...]
dbg: config: read file /etc/mail/spamassassin/local.cf
[...]
dbg: config: using "/home/guenther/.spamassassin" for user state dir
dbg: config: using "/home/guenther/.spamassassin/user_prefs" for user prefs file
dbg: config: read file /home/guenther/.spamassassin/user_prefs
--
char *t="[EMAIL PROTECTED]";
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; }}}
