On Wed, 2009-05-20 at 13:04 -0400, Charles Gregory wrote:
> On Wed, 20 May 2009, Karsten Bräckelmann wrote:
> > The ok_locales setting defaults to all, effectively disabling all
> > CHARSET_FARAWAY rules. It is intended to be set voluntarily to charsets
> > you cannot even decipher, let alone read.
>
> Now that I think about it, I would be much happier with a setting
> named "bad_locales", so that I could specifically trap/score certain
> over-abused locales without having to guess at every possible legitimate
Err, there are exactly 6 (six) different locales. How hard can that be?
Keep in mind this option is about character sets, not languages or
something.
So excluding a single one as with your inverted option is equivalent to
copying 5 locales, each 2 chars long. And yes, this logic inversion has
been discussed quite a few times in the past.
> locale that my users might be using. That, or rule/plugin that writes a
> header into the message that procmail could check. For example,
>
> Spam-Locale: {EN|FR|GR|RU|CN|...}
That's the TextCat plugin and it's ok_languages option. An entirely
different story.
> (And sorry, because of where and when SA is invoked it is always being
> run for *all* recipients of a message, defeating the use of per-user
> locale_ok setting. That would be easy! LOL)
That's your personal problem. ;) SA does support ok_locales with
per-user preferences.
guenther
--
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; }}}
