does the munge8bit config option work in new kolab releases?

[Bernhard Reiter]

On Wednesday 11 October 2006 19:32, Uwe Greßhake wrote:
> in old kolab2 beta server releases , I never had any problems with
> wrongly coded subject lines, when I set reject8bit and munge8bit options
> in the imap.conf file both to "no".
> Wrongly coded letters passed through unchanged and my email client
> displayed most of the HAM emails correctly. Thats just what I wanted and
> needed.
>
> Now, I am using kolab 2.0.3 release and all wrongly coded subject
> letters get 'X'-ed by cyrus.
> It does not matter, if I set the 'munge8bit' option to 'yes' or 'no'.
> For me it seems, that this option has no effect in this kolab release.
> Is that right?
> I read somewhere, that cyrus has to be patched for this option to work.
> Does it mean, that newer kolab releases do not include this patch any
> longer?

I do not think we changed anything like this from the Kolab Server side
packaging, we just used a newer Cyrus version as far as I can remember.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20061013/c2883b50/attachment.sig>