On Fri, Feb 12, 2010 at 10:18:02AM -0500, Ken Murchison wrote:
> Bron Gondwana wrote:
> >On Mon, Feb 08, 2010 at 11:29:22AM -0500, Ken Murchison wrote:
> >>
> >>Bron Gondwana wrote:
> >>>On Mon, Feb 08, 2010 at 07:53:21AM +0100, Garry wrote:
> Hi,
>
> after wondering for a while why oc
Bron Gondwana wrote:
> On Mon, Feb 08, 2010 at 11:29:22AM -0500, Ken Murchison wrote:
>>
>> Bron Gondwana wrote:
>>> On Mon, Feb 08, 2010 at 07:53:21AM +0100, Garry wrote:
Hi,
after wondering for a while why occasionally my sieve script rules
wouldn't work, I just found the re
On Mon, Feb 08, 2010 at 11:29:22AM -0500, Ken Murchison wrote:
>
>
> Bron Gondwana wrote:
> >On Mon, Feb 08, 2010 at 07:53:21AM +0100, Garry wrote:
> >>Hi,
> >>
> >>after wondering for a while why occasionally my sieve script rules
> >>wouldn't work, I just found the reason (I guess) - Sieve does
Bron Gondwana wrote:
> On Mon, Feb 08, 2010 at 07:53:21AM +0100, Garry wrote:
>> Hi,
>>
>> after wondering for a while why occasionally my sieve script rules
>> wouldn't work, I just found the reason (I guess) - Sieve doesn't
>> (correctly?) decode utf encoded header lines which e.g. are in a for
On Mon, Feb 08, 2010 at 01:03:30PM +0100, Garry wrote:
> 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 f
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
On Mon, Feb 08, 2010 at 07:53:21AM +0100, Garry wrote:
> Hi,
>
> after wondering for a while why occasionally my sieve script rules
> wouldn't work, I just found the reason (I guess) - Sieve doesn't
> (correctly?) decode utf encoded header lines which e.g. are in a format
> like this:
>
> Subject
Hi,
after wondering for a while why occasionally my sieve script rules
wouldn't work, I just found the reason (I guess) - Sieve doesn't
(correctly?) decode utf encoded header lines which e.g. are in a format
like this:
Subject:
=?utf-8?B?W0xPR10gV2F0Y2hsaXN0OiBzbWVhZ29sIGZvdW5kIEdydcOfIGF1cyBkZX