Am Donnerstag, den 21.03.2013, 20:59 +0100 schrieb Janos SUTO: > Hello Frank, > > On 2013-03-21 14:43, Frank Ellebrecht wrote: > > > > During my tests (build 776) I archived an email with an attached text > > file (log file). In the web UI the message size is shown correctly, > > but > > neither the paper clip icon nor a link to the attachment is shown. The > > message body doesn't show the attachment's text either. There is no > > way > > to view or open the attachment. > > > > 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. > > > > 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.) > > 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. Frank
