On Tue, 2014-07-01 at 20:53 -0500, Steve Bergman wrote: > On 07/01/2014 07:32 PM, Karsten Bräckelmann wrote: > > > That's pretty bad practice. Fundamentally, you are implementing a custom > > auto-learn flavor, overruling the SA configurable auto-learn behavior > > BTW, that reminds me of a question I had been meaning to ask on the > list. Autolearn. There's very little written about it, so far as I am
http://spamassassin.apache.org/doc/Mail_SpamAssassin_Conf.html http://spamassassin.apache.org/doc/Mail_SpamAssassin_Plugin_AutoLearnThreshold.html > aware. But from what I have gleaned, from old posts, is that it is > system-wide and in-memory. It depends on how you call SA (SMTP or MDA level). SA itself is a filter, called by your mail-processing chain. Thus, there is no SA default context of system-wide or per-user. It depends on how you call it. > Now, I have Spamass-milter set to run SA 3.3 > as the recipient user, using the filedb backend. So in 3.3, is autolearn > system wide and in memory, or per user and on disk? Milter usually means system-wide. (But since you just asked, it is.) Which, referring to my previous post, also means, a single sloppy user deleting your custom-auto-learned FN ham messages affects all your other users. Or a non-sloppy, but on-vacation-mode user. Moreover, there is no in-memory only, not on-disk mode. Unless you don't have to ask about it. > This makes a difference regarding what Karsten and I are discussing. I > don't suppose I would object to being wrong. But I have a feeling that > I'm right. Irrespective of your feeling -- cheers! /me having a beer -- 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; }}}
