Hi Alec, The PidTagRtfCompress property is just passed through the API and there is no server-side support of the best body algorithm.
OpenChange supports the BestBody algorithm but for client-side applications (libmapi/cdo_mapi.c) only. At the server-side level, we only store client's preferences when it sets a synchronization context (SynchronizationFlag_BestBody in the synccontext object (mapiproxy/servers/default/emsmdb/oxcfxics.c). On 07/09/15 12:17, Aleksander Machniak wrote: > Does Openchange support Best Body Algorithm? Is PidTagRtfCompressed > property converted to html/text by the API or is it just passed through. > -- Julien Kerihuel j.kerih...@openchange.org OpenChange Project Founder Twitter: http://twitter.com/jkerihuel GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@lists.openchange.org http://mailman.openchange.org/listinfo/devel
