On Fri, 2009-10-09 at 12:48 -0400, Jason Bertoch wrote:
> Karsten Bräckelmann wrote:
> >
> > Probably because you are not short-circuiting on the whitelist. ;)
>
> Is there a reason whitelist entries aren't short-circuited by default?
They are, in 60_shortcircuit.cf.
IFF you enable the optional Shortcircuit plugin. I guess it is disabled
by default, because it results in quite some different behavior.
> > If you *know* a given message is not spam, you can just as well spare
> > the cycles calling SA on it -- and have your glue avoid SA for those.
>
> Because of things like user_prefs and such. I don't want to give users
> access to glue configuration. Besides, if editing glue was _always_ the
> appropriate tactic, SA wouldn't need the ability to whitelist.
I did not say "always", neither did I imply it. However, with stuff like
mailing lists, it is a good choice and frequently advised on this list.
As per the documentation, the whitelist options in SA are "Used to
whitelist [...] mail that is often tagged (incorrectly) as spam." Which
is not the same as a mailing list.
--
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; }}}
