Hello Frank,
On 2013-03-21 23:53, Frank Ellebrecht wrote:
The relevant headers shown by piler:
Content-Type: multipart/mixed; boundary="=-P1LXwtUztRVaN97ccNZu"
Mime-Version: 1.0
The headers in my MUA (Evolution 3.6.2):
--=-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.
do you get the original message properly if you retrieve the message
with pilerget?
Yes, pilerget retrieves the whole message properly (only some
X-Header-lines removed).
What do you have in the metadata table for this message? I'm
interested
in
the attachments column.
mysql> select attachments from metadata where id='18';
+-------------+
| attachments |
+-------------+
| 0 |
+-------------+
1 row in set (0.00 sec)
Another problem is that attachments with file names containing
Umlauts
(äöü) are not shown correctly in the web UI, e.g. the file
»Kontenblätter 2011.pdf« becomes
»ISO-8859-1''Kontenbl%E4tter%202011.pdf«.
Is this an intended behaviour? (The angle quotes are not in the file
name,
but here to show what belongs to the name.)
well, I believe that if you specify the character set (eg. iso-8859-1),
and use "extended" characters (above 127) then you should also encode
it
(as it is done), however you should also specify the encoding type,
too.
(eg. ?Q? or ?B?), so it should look as
=?ISO-8859-1?Q?Kontenbl%E4tter%202011.pdf?=
so I think it might be a bug on the MUA side.
can you show me its MIME headers like above for the mail.log?
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
and it is correctly shown in the web ui as äöüß.pdf. So it seems to be
more a problem with evolution than with piler. Although both
Evolution
and Thunderbird show the file name right in both cases.
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?
Janos
