Kmail has stopped reading winmail.dat attachments. Specifically, the winmail.dat attachments are meeting invites. Moreover, the email describes the winmail.dat as "winmail.dat <empty>" and if I save it and try to read it using tnef I get no output. This problem did not occur a few weeks ago. Thus, I do not know whether the problem is due to a change on my system or the sender's. However, if I forward the email to Gmail, the attachment is interpreted correctly. Finally I see, in Synaptics, that ktnef is not installed. However, if I mark it for installation then Synaptics warns me that kmail will be removed, which is a risk I am not keen to take. In all other respects, thank you for a wonderful desktop and collection of applications. Regards Reproducible: Always Steps to Reproduce: 1. Receive email from Outlook user 2. Read email Actual Results: Winmail.dat attachments that I know to be meeting invites are shown as "winmail.dat <empty>". Saving the attachment and attempting to read it using tnef gives no output. If I forward the email to Gmail, the attachment is interpreted correctly. Expected Results: The meeting invite should have been displayed in kmail. I see that ktnef is not installed. However, if in the Synaptics Package Manager I mark ktnef for installation, it warns that kmail will be removed.
I need an test email to test it. Could you provide one ?. Thanks
I've seen this before and I believe it was due to some changed setting on the Windows mail server side. Not that I have any idea what that change is. It is interesting that Gmail can show it still so that probably means GMail has a better tnef library than we do. Our tnef library is quite old and may not support everything needed.
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.