Harry Putnam wrote: > Matt Kettler <[EMAIL PROTECTED]> writes: > > >> Well, that particular subject looks to only contain ordinary ascii. >> Can't hit any CHARSET rules when there's no charachter set to hit. >> > > I hadn't understood it was based on a charset being stipulated. > Yes, check the manpage again.. In fact, the HTML version on the website has *character sets in bold text.
http://spamassassin.apache.org/full/3.1.x/dist/doc/Mail_SpamAssassin_Conf.html#language_options * > >> Are you using ok_languages as well? >> > > My Mail::SpamAssassin::Conf page doesn't mention this at all. The > only thing beginning `ok_' in it is `ok_locales'. What man page talks > about ok_languages? > Apparently in SA 3.1.0 this was moved to a plugin. You need a loadplugin statement in your v310.pre that loads the TextCat plugin. There's one in there in the default file, but it's commented out. Once you load TextCat you can use the options in it's manpage, including ok_languages: http://spamassassin.apache.org/full/3.1.x/dist/doc/Mail_SpamAssassin_Plugin_TextCat.html > Judging from yours and other posts on this thread, I'm looking for > something that is able to tell with some certainty when a subject line > is not in english. Something that gets to a message before SA is > called. Like maybe a nifty procmail recipe. > > If you're looking to save CPU, that's the way to go. However, I'm not sure how to do that with anything simple..
