Hide Forgot
There are some known issues with openchange 0.9 which cannot be fixed otherwise then in openchange (the other part using openchange is evolution-mapi). From the most significant I would name: a) unicode support is not finished in 0.9 resulting in (for example): - lost letters from strings - cannot send messages with unicode letters in subject b) support for particular property types is not done at all in 0.9 - PT_DOUBLE - no percent complete in tasks - PT_MV_BINARY - for distribution lists (address book) There are more which I cannot recall right now, but the point is that with these not working (especially from a)) customers would not use evolution-mapi properly. (Note that some changes are also needed on evolution-mapi side to have this working properly.)
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion.
I forgot to mention, these changes are including openchange API changes, but as evolution-mapi is the only package linking against it (I'm just about to file the bug and set it as depending on this one), then that shouldn't be a problem.
Patch committed to openchange-0.9-7.el6. It fixes unicode support and some property types. I do not have any exact steps for testing, because this is a library. It can be tested with evolution-mapi-0.28.3-5, which requires this package.
Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.