В Сбт, 17/01/2009 в 18:43 +0300, Sergey Kovalev пишет: > Bogun Dmitriy пишет: > > I have upgraded to 3.59(was 3.56). But it not help... it still not > > converting body and not match my test rule. I have tried with utf8, > > koi8-r, cp1251... all not working. But when I have disabled > > normalize_charset, message in UTF8 hit into my rule... all > > other(koi8-r,cp1251 still not hit). I think this is because local.cf in > > utf8 too. > > > > Any suggestions how it fix? > > One russian SA user here on the list suggested adding line > use utf8; > to Mail/SpamAssassin/Plugin/Check.pm > and enabling normalize_charset in local.cf. > > After that my rules like > body CYR_PORN_BODY_8 /(?:\b|^)оральный(?:$|\b)/ > began hitting koi8-r spam that my postmaster@ receives a lot. > I use a perl script that generates one word rules from a list of "bad" > words. It also adds a summary big-score rule that is hitted if some > ammount of small-scored rules hit. > > I have not investigated if it hits html or cp1251-encoded messages > because have no time right now and haven't seen them often. > > But there is a side affect: SA starts complaining about some rules in > 20_advance_fee.cf which contains some non-ascii characters. Since there > are no usefull rules for me, I just renamed this file (I do not cron > sa-update).
I have made this ugly hack and it start working as wrote into documentation. I have googled same solution. As I understand this is old bug... Its working - it good, but this is not solution - it bad. Is here any developer who cat explain mainstream "politics" about utf8 support. Is it will be fixed or no one need it?
