Hi,
using Roundcube 0.5.1 I experience a strange behaviour:
I start a new conversation using a simple text containing "Umlaute", lets say:
äöüÄÖÜß
My partner answers me using Outlook 2007 (English version). The message I received is messed up when using Umlaut or other special characters. The message reads like this (my partner answered with 'äöüÄÖÜß' too, for demonstration):

äöüÄÖÜß
If I answer this message again and get another reply, everything is back to normal. So, msg #1, #2 are corrupt, msg #3, #4, ... are okay.
If I check the corrupt text using Thunderbird, all is okay and readable. When I check the source of the mail, I see that the answer of my partner (who's using Outlook) is base64 encoded. So I tried die decode using different web-tools. The "äöüÄÖÜß" I should receive is encoded to
77u/DQrDpMO2w7zDhMOWw5zDnw0K
Decoding "77u/DQrDpMO2w7zDhMOWw5zDnw0K" using
PHP-Einfach.de - Base64 kodieren/dekodieren (php based) comes out with crap. Using the javascript-based decoder at
Kodierung und Dekodierung mit base64 gives the same messed up result.
But if I use the asp-decoder at
Safe Base 64 Decoder, it gives the correct result. The same if I use a windows executable program for decoding.
Countercheck: if i use a web-tool to encode "äöüÄÖÜß" I get
5Pb8xNbc3w==
which should be the right base64 encoded result.
What I can say from comparing some mail sources is that the starting "77u/" seems to cause the trouble. It doesnt matter what text is encoded, if it starts with "77u/" it will decoded incorrect.
So what is the solution? And remember, the 3rd, 4th... reply of the message-thread is correctly showing umlaut and special chars.
Cheers & thnx in advance
Thomas Schröder