On Fri, 2011-02-25 at 16:06 -0500, Mauricio Tavares wrote:
> On Fri, Feb 25, 2011 at 4:04 PM, Bowie Bailey <[email protected]> wrote:
> > > ok_languages en
> > >
> > > and textcat enabled (loadplugin) but it is not, say, scoring Spanish spam.
TextCat might just not identify the language with sufficient confidence.
See the TextCat plugin docs. The _LANGUAGES_ template tag might help
debugging this.
> > > Now, is it ok to have both the loadplugin and the ok_languages
> > > statements in local.cf?
> >
> > Loadplugin statements should be in the *.pre files so that they get
> > loaded before the rules.
Exactly, should, for the very reason you stated. :)
However, since that is the reason, using pre files actually is not
mandatory. With a custom plugin Foo, it is perfectly fine to exclusively
use a foo.cf, that contains both, the loadplugin line and rules using
it. The loadplugin of curse MUST be given before using it in rules.
> > TextCat should be enabled by uncommenting the loadplugin statement in
> > v310.pre.
>
> Aha. I thought you want to only make changes on local.cf because
> in an upgrade you could not guarantee changes to a .pre file would not
> be overwritten.
They should not be overwritten, since it's site configuration.
If you prefer not to mess with the stock pre files, you always can
create e.g. your own local.pre, or even a dedicated pre file for each
plugin to load.
--
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; }}}
