How to use non-ascii charsets with sieve?
ken at oceana.com
Mon Dec 9 16:42:44 EST 2002
Lawrence Greenfield wrote:
> You bring up good questions.
> First, our Sieve implementation currently doesn't deal with RFC 2047
> encoded headers---or rather, it just compares the undecoded headers
> against the UTF-8 string. This is obviously a bug which sadly isn't in
> Ken and I talked (a long time ago) about this. The main issue is that
> Cyrus's character comparison routines remove whitespace and always
> perform casemapping, and this is probably inappropriate for Sieve's
> use. Fixing this is probably not difficult, but I'd prefer not to have
> multiple different canonicalization tables.
I _think_ I still have the code around which implements the Sieve
charset tables and does the rfc2047 decoding. I don't recall why we had
to have the separate tables however.
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
More information about the Info-cyrus