| Summary: | TNEF attachments not properly represented in UI | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Soenke Dibbern <s_dibbern> |
| Component: | UI | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | montel |
| Priority: | NOR | ||
| Version: | 5.3.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/kdepim-addons/648a48afbb50187c18d9452433549ae660f12b08 | Version Fixed In: | 5.5.2 |
could you provide some testcase (in private if you want)? Well, the email causing this problem is confidential. I see there's a PGP key for your name and email: F8971E06FD551F2C. I could use that to send you the mbox if you vow not to disclose the contained information and if you have no better proposal. If you send me as private I will trash this email after that. I just need to investigate your bug :) Git commit 648a48afbb50187c18d9452433549ae660f12b08 by Montel Laurent. Committed on 19/05/2017 at 14:29. Pushed by mlaurent into branch 'Applications/17.04'. Fix Bug 379988 - TNEF attachments not properly represented in UI FIXED-IN: 5.5.2 M +1 -1 plugins/messageviewer/bodypartformatter/ms-tnef/application_ms-tnef.cpp https://commits.kde.org/kdepim-addons/648a48afbb50187c18d9452433549ae660f12b08 |
I have got a TNEF attachment ("winmail.dat")containig two PDFs. These seem to get automagically extracted to two folders in /tmp/, /tmp/messageviewer_Bh3061.index.ktnef-0 and /tmp/messageviewer_zg3061.index.ktnef-1. Within these two folders, the contained PDFS got stored. In the KMail representation of the e-mail the PDFs are represented by two links into the file system. But apparantly the creation of these links fails somehow. Instead of a link to "file:///tmp/messageviewer_Bh3061.index.ktnef-0/Some Long File Name Containig Spaces.pdf" I get something like "file:///%2Ftmp%2Fmessageviewer_Bh3061.index.ktnef-0%2FSome~1.PDF". This is on a ext4 filesystem. I don't get winmail.dats regularly these days any more, so I can't tell whether this is a general problem or whether only few winmail.dats are affected.