On Fri, 2010-12-10 at 05:18 -0800, an anonymous Nabble user wrote: > Spam assassin last time worked on November, 15th. I saw the information in a > subject of the letter ***SPAM*** and properties of the letter:
So something changed that day. Whatever it was, that is almost certainly the cause. > Please check your spamassassin configuration in cpanel using the step by > step instructions given in this documentation : > If you want to stop spam to your account then only enabling spam assasin > will not work. You will also have to configure user level filtering from > your cpanel [...] OK, so you are using cPanel. There is nothing we can help you with, unless you got direct control over SpamAssassin and your mail processing chain. No debugging without that. > We dont find you have configured user level filters from your cpanel for > account aronis.ru please configure it [...] Asking the cPanel support would be a better guess. The following was not part of your original, invalid bug report against SA, and seems to be yet another mail to your hosting support. > I think you should configurate spamassassin at your end. You can ask for > help on the spamassassin users' list at > http://issues.apache.org/SpamAssassin/ No! For $diety's sake, no! This is EXACTLY what you've been told in the bug report. That link is NOT the place for support questions. It is a bug tracker. Do NOT ask for help there. -- 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; }}}
