Hello Janos, Am Montag, den 25.03.2013, 14:48 +0100 schrieb Janos SUTO:
> it's the same. In the middle of the night I added a few more $-signs > then > required :-) > :-) > Please overwrite model/search/message.php with the attached file, and > let's > see whether it fixes the problem. > I've done that and now the message looks way better. Here is the interesting part, copied from the web UI: **************************************************************** Sure. MUA (Evolution 3.6.2): Content-Type: multipart/mixed; boundary="=-/ncrUDnazGcbiebe5OCW" Mime-Version: 1.0 --=-/ncrUDnazGcbiebe5OCW Content-Type: application/pdf; name*=ISO-8859-1''Kontenbl%E4tter% 202011.pdf Content-Disposition: attachment; filename*=ISO-8859-1''Kontenbl%E4tter% 202011.pdf Content-Transfer-Encoding: base64 Piler: Content-Type: multipart/mixed; boundary="=-/ncrUDnazGcbiebe5OCW" Mime-Version: 1.0 The file was sent from Evolution. But when I send a file with Umlauts from Thunderbird, it looks like that (should read äöüß.pdf): Content-Type: application/pdf; name="=?ISO-8859-15?Q?=E4=F6=FC=DF=2Epdf?=" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename*=ISO-8859-15''%E4%F6%FC%DF%2E% 70%64%66 **************************************************************** I think that's the expected output, isn't it? Frank
