it allows body rules to be written in UTF8, but still match text written in other charsets.
This is useful if you want to match the *text*, rather than the actual *bytes* that are being spammed. in my opinion though, spammer patterns can be matched as strings of bytes, since that's how the spammers send them, so I don't recommend it. it's probably more useful for people who want to make corporate policy rules (matching profanity etc.) --j. On Wed, Jul 8, 2009 at 04:39, Warren Togami<[email protected]> wrote: >> >> *************************************************************************** >> NOTE: the optional Encode::Detect module is not installed. >> >> If you plan to use the normalize_charset config setting to detect >> charsets and convert them into Unicode, you will need to install >> this module. > > What is the performance impact of using normalize_charset? > > Why is this not required by default? > > Is this necessary to filter mail for Asian languages? > > Warren Togami > [email protected] > >
