Re: sieve and utf-8 MIME/base64 content

Thanks for making this more clear to me :)

On Fri, Feb 16, 2018, at 11:07, Vladislav Kurz wrote:
> The problem is that headers with non-ascii chars are encoded in form
> like this:
> Subject: =?UTF-8?B?UmU6I.....gVG9v?=
> And also the body is sometimes completely in base64, even though it is
> just plaintext or HTML in UTF-8. Depends on sender's mail client.

AFAIK the Sieve implementation in Cyrus 2.5 fully implements RFC 5228, including the string comparison requirements of section 2.7 [1]. That is, it implements the ascii-casemap and octet collations. It decodes MIME headers to UTF-8 before matching (e.g. see [2] and [3]). The RFC 5173 Sieve body extension is also supported [4].

Eugene, does that work for you?

Cheers,
Robert

[1] https://tools.ietf.org/html/rfc5228#section-2.7
[2] https://github.com/cyrusimap/cyrus-imapd/blob/cyrus-imapd-2.5/sieve/script.c#L261
[3] https://github.com/cyrusimap/cyrus-imapd/blob/cyrus-imapd-2.5/sieve/bc_eval.c#L809
[4] https://cyrusimap.org/imap/rfc-support.html
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus