Hello Janos, Am Samstag, den 23.03.2013, 12:27 +0100 schrieb Janos SUTO: > >>> > >>> --=-P1LXwtUztRVaN97ccNZu > >>> Content-Disposition: attachment; filename="mail.log" > >>> Content-Type: text/x-log; name="mail.log"; charset="UTF-8" > >>> Content-Transfer-Encoding: 7bit > >>> > >>> I'm afraid that's a bug. > > hmm, strictly speaking, yes, even though pilerget returned the email > as it was received. I'll fix this in the parser soon. > Okay, thank you.
> I'm confused: is it shown properly in the piler gui or not? Where is > the > bug actually? Can you show me a screenshot spotting the problem? > Sorry, it wasn't my intention to confuse you. Piler displays the file name as »ISO-8859-1''Kontenbl%E4tter%202011.pdf« when I send an attachment »Kontenblätter 2011.pdf« with Evolution 3.6.2. Evolution writes the following headers: > > 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 > I attached a screenshot (evolution-3.6.2-wrong.png). This is the problem I described in my first mail. But as you wrote, the issue might very well be with the MUA, Evolution. I'll see if I find anything useful to Mime encoding with Evolution. To find the cause of that issue, I did another test with Thunderbird 17.0.4 as MUA and sent the file »äöüß.pdf«. The mime headers are slightly different when created by Thunderbird: > > 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 > Here piler displays the file name right as »äöüß.pdf« (see screenshot »thunderbird-17.0.4-ok.png«). Thunderbird adds the encoding type as »?Q?«. What might have confused you was probably this: > > Although both > > Evolution > > and Thunderbird show the file name right in both cases. > I wanted to point out that both Thunderbird and Evolution know how to handle both (Evolution's and Thunderbird's) kinds of headers and show in their GUI the right filename, while piler only knows how to handle Thunderbird's header and fails with Evolution's way of writing the header. But as you said, the problem might very well be with Evolution, not with piler. I hope I made myself a bit clearer now? Thanks, Frank PS: Just saw that in Evolution's screenshot I used another filename (äöüß.pdf) than mentioned above. It's headers: --=-IunKz+uAOBfx0xew4ICt Content-Type: application/pdf; name*=ISO-8859-1''%E4%F6%FC%DF.pdf Content-Disposition: attachment; filename*=ISO-8859-1''%E4%F6%FC%DF.pdf Content-Transfer-Encoding: base64
<<attachment: evolution-3.6.2-wrong.png>>
<<attachment: thunderbird-17.0.4-ok.png>>
