Hello Frank,
On 2013-03-23 14:27, Frank Ellebrecht wrote:
hmm, strictly speaking, yes, even though pilerget returned the email
as it was received. I'll fix this in the parser soon.
the fix is committed to bitbucket, please try it, and let's see whether
it
works for 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.
thanks, now I got it. I didn't want to hack the parser as I believe
that
this wierd encoding is rare, so instead I hacked the gui, and commited
a workround for the problem.
Thanks for the detailed problem description.
Janos
