
adamlists at plexicomm
Aug 21, 2012, 1:00 PM
Post #3 of 8
(427 views)
Permalink
|
Awesome, thanks for the tip. Any guess how this affects messages with mixed character sets? One of our users definitely emails with Chinese vendors. I'm sure they correspond in English, but I'm guessing the Chinese folks might have Chinese characters in their signature line or some such. Thanks. > SpamAssassin has an ok_locales thing that allows you to specify basically > languages you want to accept. But it has problems: > https://issues.apache.org/SpamAssassin/show_bug.cgi?id=4078 > > I don't believe anybody has created rules to match these kinds of spams. > A big part of the problem is lacking examples of non-English non-spam > to verify the rules don't hit them. > > So, you should probably try using ok_locales, and if it doesn't work, > create your own rules to match these spams, if you can find good common > patterns that don't seem likely to match non-spams (or match all Chinese > email if that's what you want). And please share what works. > > ok_locales is defined in the Mail::SpamAssassin::Conf main page which can > also be found here: > http://spamassassin.apache.org/full/3.3.x/doc/Mail_SpamAssassin_Conf.html > > Hmm, ok_locales may actually work on Chinese, I don't see examples of > problems with that language. > > On 08/21, Adam Moffett wrote: >> I have a user who seems to get 4-5 messages per day with Chinese >> characters for the subject and body. They come from a variety of >> domains and IP's so I guess she somehow got onto a list used to spam >> Chinese speaking people. >> >> If I paste them into Google Translate they seem to be roughly the >> same kind of junk as our English spam: "work from home", "buy our >> drugs", etc. The handful that I looked at closely had scores of >> 2.0-3.0. >> >> Are there existing SpamAssassin rules that work on non english >> characters? Is there maybe something extra I should enable or >> install that would score these higher? >> >> I'm sorry if it's an ignorant question, but the issue hasn't really >> come up here before. >> >> Thanks. >>
|