On Tue, 2009-06-09 at 01:18 +0200, Mark Martinec wrote:
> >
> > X-SpamScore: 0
> > tests= SIZE_LIMIT_EXCEEDED
> Some sw components to be ruled out:
> - this isn't amavisd-new doing it, at least none of the official versions;
Sorry, Mark. :) I was entirely going by the OPs outgoing headers, which
clearly shows an amavisd-new header in the chain. Though at a second
look, I realize that's about a hop after SA processing...
> - this isn't Maia Mailguard;
> - this isn't old versions of amavis;
> - this isn't SpamAssassin (neither spamc/spamd, nor the library).
>
> Although the most recent version of amavisd-new (2.6.3) does provide
> ability to pass partial message to SpamAssassin and to insert rule hits
> into the final result, this isn't the case here, and there is no
> SIZE_LIMIT_EXCEEDED message generated anywhere.
>
> Look for another culprit in your mail path, such as a webmail component
> or a content filter at some ISP. My guess at pointing fingers is Nemesis.
Right, that's definitely something else adding the headers, as has been
pointed out before. Not SA. Anything, even a trivial filter foo calling
formail easily can inject such a header (though the order in the chain
may vary, which is not obvious from the OP).
--
char *t="\10pse\0r\0dtu...@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; }}}
