On Mon, 2014-05-12 at 11:33 +0100, Timothy Murphy wrote: > I'm not sure if SA is working properly on my CentOS-6.5 server.
> :0fw:spamassassin.lock > * < 256000 > | /usr/bin/spamc This adds some X-Spam headers to all messages less than 256 kByte in size, both spam and ham. The headers include details like SA version (primarily meant for debugging), as well as overall score and a list of SA rules hit, besides some more info. These headers should tell you if (and how) SA is working. If you need assistance interpreting them, feel free to paste a few sample headers. > :0: > * ^X-Spam-Status: Yes > /home/tim/Maildir/.Spam/new This delivery recipe works, if it is an existing directory, though the preferred way of specifying a maildir directory is to end the path with a "/" slash. Procmail will take care about using tmp/ and new/ itself. > I'm assuming that this is sufficient? Looks fine, yes. > But how can I check that SA is working properly? Your question is slightly confusing. Does spam get delivered to your dedicated spam maildir? If so, wouldn't that qualify for "working properly"? To differentiate various shades of "properly", the X-Spam headers will show some details. Those headers also can be used to verify SA being called without waiting for spam, since they are added to ham, too. > Any and all advice or suggestions gratefully received, > including pointers to helpful documentation. man procmailrc, last paragraph of section "Recipe action line" for the maildir delivery bit. ;) Official documentation, in particular the Conf document, as well as spamc and sa-learn docs in this specific case. http://spamassassin.apache.org/full/3.3.x/doc/ -- 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; }}}
