On Sun, 2014-05-11 at 15:26 -0400, James B. Byrne wrote:
> We use Spamassassin through Amavisd-new with Postfix. Our Postfix /
> Amavisd-new / Spamassassin setup has worked reliably for the past 18 months or
> so. Recently we made changes to Postfix to enable SPF policy checking and to
> have DKIM sign outgoing messages. Since then we have noticed a considerable
> decline in spam but we have also noticed that incoming mail no longer has any
> SPAM headers applied by Spamassassin at all.
Since you are using SA via Amavis, the X-Spam headers are not added by
SA, but Amavis. Thus, you would need to check back with Amavis rather
than SA. However...
If the observed lack of X-Spam headers really coincides with a change to
Postfix configuration, Amavis isn't a likely candidate either. You want
to review your Postfix config changes.
It also might be possible that the recent Postfix config changes are
causing Amavis to bypass SA checks or prevent adding SA result headers.
In that case, it might be an Amavis feature (and configuration option)
now triggered by the Postfix changes.
In any case, it is at least one level up of SA in your mail processing
chain.
--
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; }}}
