Hi Martin, It is a bug we have already identified in OpenChange some months ago, but it is tricky to address a long term fix right now.
The root cause of the issue lies in the statically and implicit
encoding/decoding of strings from/to utf8 while Outlook expects a
different codepage to be used. One way to work around this problem can
be the usage of raw8string which prevent iconv from doing any
conversion, but it may have some side effects. Outlook also specifies
the encoding in which it expects to receive strings, but this happens at
a higher layer which is not propagated down the the lowest one.
Furthermore, there may also be additional roots of this problem in SOGo
which fails to save the encoding properly when receiving external emails.
Next steps:
1. can you send me a wireshark capture (non-encrypted) so I can
inspect the data flow involving this problem?
2. if I provide you a patch, do you have the environment to apply it
and give me feedback (eventually additional captures on request?)
I suggest we continue this discussion on the openchange devel
mailing-list [1], so each list keeps the focus and information is
dispatched properly.
Br,
Julien.
[1] http://mailman.openchange.org/listinfo/devel
On 19/05/14 09:53, Martin Šinský wrote:
> Hi,
> if I have mails in ISO8859-2, webmail or imap shows it ok, but Outlook
> connected through openchange it shows bad. Mails in UTF8 shows Outlook
> ok.
> How to fix it, please?
>
> Regards,
> Martin
>
--
Julien Kerihuel
[email protected]
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 [email protected] http://mailman.openchange.org/listinfo/devel
