Sieve and encoded Headers

Garry gkg at
Mon Feb 8 07:03:30 EST 2010

On 08.02.2010 08:28, Bron Gondwana wrote:
> I've CC'd Ken on this - I wonder if it's worth going back and doing a
> "minimal still compatible" set of patches that fixes charset encoding in
> sieve without actually changing the on disk format of the cyrus.cache
> (which is what requires reconstructs to make things work again)

I've not looked into the sources, so please be kind if I'm totally off
the path here, but in general I wouldn't expect the comparison to
require changing the on-disk format of the stored information - just
ensure that upon reading (and thus comparing) something, add a function
that creates a decoded copy of the header string (e.g. by going to UTF8
on everything, including the sieve rule information), then compare that ...

> But - I can tell you that we're not going to be backporting this sort of
> thing to the 2.2 series, so you'll certainly need to upgrade!

I was just stating the facts, no problem here if it needs to be updated
... I just dropped in the current APT packages for ease of
administration ...

Thanks for the feedback,


More information about the Info-cyrus mailing list