Res wrote:
[]
> on our internal email servers (and on my personal one) I use
> milter-regex to stop all those pesky cable/dial/dsl users, its great
> because i can also use this rule in milter-regex.conf :
>
> reject "Access Denied ; Please use the English language when
> communicating with us"
> header /Subject/i
> /=[?](KOI8-[RU]|GB2312|GB2312_CHARSET|ISO-2022-JP|SHIFT[-_]JIS|BIG5|WINDOWS-125[156])[?][QB][?]/ie
>
> header /Subject/i
> /charset=(3D)?"?(KOI8-[RU]|GB2312|GB2312_CHARSET|ISO-2022-JP|SHIFT[-_]JIS|BIG5)/ie
>
> header /Subject/i /[-]{6}/e
> header /Content-Type/i ,text/(plain|html);
> *charset="?(KOI8-[RU]|GB2312(_CHARSET)?|ISO-2022-JP|SHIFT[-_]JIS|BIG5),ie
Too bad it does not work very well for legitimate email... You
don't know because you don't have correspondents in those countries,
which is why it works for you ;)
More and more email software uses UTF8 encoding nowadays, instead of
a single-byte encodings like KOI8, WINDOWS1251 and the like above.
And with UTF8, there's no simple way anymore to detect the language
actually used.
It's worse: for example, thunderbird running with russian as a default
language will put "charset=koi8-r" even for 100% ascii emails unless
explicitly told to use ascii charset. "Charset=koi8-r" and 100% ascii
inside does not contradict with each other since ascii is a subset of
koi8-r, but obviously does not help to filter those.
/mjt
