On Sat, 2009-08-01 at 18:15 -0700, Stefan Malte Schumacher wrote: > > Evidence that it's not working? Show us some SA headers. In this case, a > > spam sample that triggered DCC, cause the Report header does show the > > rule's score.
Hmm, I wasn't clear enough. :) I meant an identified spam, where the Report header is added. It isn't with that sample. Anyway... > Here is an example with Razor2, but I guess the underlying problem is the > same. > > http://www.pagan.mynetcologne.de/example-email X-Spam-Status: No, score=2.2 required=5.0 tests=AWL,HTML_IMAGE_RATIO_04, HTML_MESSAGE,RAZOR2_CF_RANGE_51_100,RAZOR2_CF_RANGE_E4_51_100,RAZOR2_CHECK, UNPARSEABLE_RELAY autolearn=no version=3.2.5 > As you can see, the message only gets a score of 2.2. In the beginning I > believed that I made some embarrassing mistake with the rules concerning the > network checks, but if you say these are okay the problem most likely lies > somewhere else. AWL. Obviously, it counters the custom scores, based on the sender's history. And it seems, the sores have been really low in the past. spamassassin -t < sample What does that say at the bottom of the output, for this sample? -- 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; }}}
