Inline viewer for Microsoft proprietary mail formats (ms-tnef, etc.) ["winmail.dat"]
Categories
(MailNews Core :: MIME, enhancement)
Tracking
(Not tracked)
People
(Reporter: baffoni, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug, )
Details
(Keywords: parity-Outlook, Whiteboard: [workaround: comment 170,173][read comment 158 before replying])
Attachments
(2 files)
Comment 1•25 years ago
|
||
Updated•25 years ago
|
Comment 3•24 years ago
|
||
Comment 4•24 years ago
|
||
Comment 5•24 years ago
|
||
Updated•24 years ago
|
Comment 6•24 years ago
|
||
| Reporter | ||
Comment 8•23 years ago
|
||
Updated•23 years ago
|
Comment 9•23 years ago
|
||
Comment 10•23 years ago
|
||
Updated•22 years ago
|
Comment 11•22 years ago
|
||
Comment 12•22 years ago
|
||
Comment 13•22 years ago
|
||
Updated•22 years ago
|
Comment 14•22 years ago
|
||
Comment 15•22 years ago
|
||
Comment 16•22 years ago
|
||
Updated•21 years ago
|
Comment 17•21 years ago
|
||
Comment 18•21 years ago
|
||
Comment 19•21 years ago
|
||
Comment 20•21 years ago
|
||
Comment 21•21 years ago
|
||
Comment 22•21 years ago
|
||
Comment 23•21 years ago
|
||
Comment 24•21 years ago
|
||
Comment 25•21 years ago
|
||
Comment 26•21 years ago
|
||
Comment 27•21 years ago
|
||
Comment 28•21 years ago
|
||
Comment 29•21 years ago
|
||
Comment 30•20 years ago
|
||
Comment 31•20 years ago
|
||
Updated•20 years ago
|
Updated•20 years ago
|
Comment 32•20 years ago
|
||
Updated•20 years ago
|
Comment 33•20 years ago
|
||
Comment 34•20 years ago
|
||
Comment 35•20 years ago
|
||
Comment 36•20 years ago
|
||
Comment 37•20 years ago
|
||
Comment 38•20 years ago
|
||
Comment 39•20 years ago
|
||
Comment 40•20 years ago
|
||
Comment 41•20 years ago
|
||
Comment 42•20 years ago
|
||
Comment 43•20 years ago
|
||
Comment 44•19 years ago
|
||
Comment 45•19 years ago
|
||
Comment 46•19 years ago
|
||
Comment 47•19 years ago
|
||
Comment 48•19 years ago
|
||
Comment 49•19 years ago
|
||
Comment 50•19 years ago
|
||
Comment 51•19 years ago
|
||
Comment 52•19 years ago
|
||
Comment 53•19 years ago
|
||
Comment 54•19 years ago
|
||
Comment 55•19 years ago
|
||
Comment 56•19 years ago
|
||
Comment 57•19 years ago
|
||
Comment 58•19 years ago
|
||
Comment 59•19 years ago
|
||
Comment 60•19 years ago
|
||
Comment 61•19 years ago
|
||
Comment 62•19 years ago
|
||
Comment 63•19 years ago
|
||
Comment 64•19 years ago
|
||
Comment 65•19 years ago
|
||
Comment 66•19 years ago
|
||
Comment 67•19 years ago
|
||
Comment 68•19 years ago
|
||
Updated•18 years ago
|
Comment 70•18 years ago
|
||
Comment 71•18 years ago
|
||
Updated•18 years ago
|
Comment 72•18 years ago
|
||
Comment 73•18 years ago
|
||
Comment 74•18 years ago
|
||
Comment 75•18 years ago
|
||
Comment 77•18 years ago
|
||
Comment 78•18 years ago
|
||
Comment 79•18 years ago
|
||
Comment 80•18 years ago
|
||
Comment 81•18 years ago
|
||
Comment 82•18 years ago
|
||
| Assignee | ||
Updated•18 years ago
|
Comment 87•17 years ago
|
||
| Reporter | ||
Comment 88•17 years ago
|
||
Comment 89•17 years ago
|
||
Comment 90•17 years ago
|
||
Comment 91•17 years ago
|
||
| Reporter | ||
Comment 92•17 years ago
|
||
Comment 93•17 years ago
|
||
Comment 94•17 years ago
|
||
Comment 95•17 years ago
|
||
Comment 96•17 years ago
|
||
Comment 97•17 years ago
|
||
Comment 98•17 years ago
|
||
Comment 99•17 years ago
|
||
Updated•17 years ago
|
Comment 100•16 years ago
|
||
Comment 101•16 years ago
|
||
Comment 103•16 years ago
|
||
Comment 104•16 years ago
|
||
Comment 105•16 years ago
|
||
Comment 106•16 years ago
|
||
Comment 107•16 years ago
|
||
Comment 108•16 years ago
|
||
Comment 109•16 years ago
|
||
Comment 110•16 years ago
|
||
Comment 111•16 years ago
|
||
Comment 112•16 years ago
|
||
Comment 113•16 years ago
|
||
Comment 114•16 years ago
|
||
Comment 115•16 years ago
|
||
Comment 116•16 years ago
|
||
Comment 117•16 years ago
|
||
Comment 118•16 years ago
|
||
Comment 119•16 years ago
|
||
Comment 121•16 years ago
|
||
Comment 122•16 years ago
|
||
Comment 126•15 years ago
|
||
Comment 127•15 years ago
|
||
Comment 128•15 years ago
|
||
Comment 129•15 years ago
|
||
Comment 130•15 years ago
|
||
Comment 131•15 years ago
|
||
Comment 132•15 years ago
|
||
Comment 133•15 years ago
|
||
Comment 134•14 years ago
|
||
| Reporter | ||
Comment 135•14 years ago
|
||
Comment 136•14 years ago
|
||
Comment 138•14 years ago
|
||
Comment 139•14 years ago
|
||
Comment 140•14 years ago
|
||
Comment 141•13 years ago
|
||
Comment 142•13 years ago
|
||
Comment 143•13 years ago
|
||
Comment 144•13 years ago
|
||
Comment 145•13 years ago
|
||
Comment 146•13 years ago
|
||
Comment 147•13 years ago
|
||
Comment 148•13 years ago
|
||
Comment 149•13 years ago
|
||
Comment 150•13 years ago
|
||
Comment 151•13 years ago
|
||
Comment 152•13 years ago
|
||
Comment 153•13 years ago
|
||
Comment 155•13 years ago
|
||
Comment 156•13 years ago
|
||
Comment 157•13 years ago
|
||
Comment 158•13 years ago
|
||
Comment 159•13 years ago
|
||
Comment 160•13 years ago
|
||
Comment 161•13 years ago
|
||
Comment 162•13 years ago
|
||
Comment 163•13 years ago
|
||
Comment 164•12 years ago
|
||
Comment 165•12 years ago
|
||
Comment 166•12 years ago
|
||
Comment 169•11 years ago
|
||
Comment 170•11 years ago
|
||
Comment 171•10 years ago
|
||
Comment 172•10 years ago
|
||
Comment 173•10 years ago
|
||
Comment 174•10 years ago
|
||
Comment 175•10 years ago
|
||
Comment 177•9 years ago
|
||
Comment 178•9 years ago
|
||
Updated•9 years ago
|
Comment 179•9 years ago
|
||
Updated•9 years ago
|
Comment 180•9 years ago
|
||
Comment 184•6 years ago
|
||
What's the plan for this after the death of old TB addons? This is still a commonly used thing in corporate/government e-mail.
Comment 185•6 years ago
|
||
(In reply to khagaroth from comment #184)
What's the plan for this after the death of old TB addons? This is still a commonly used thing in corporate/government e-mail.
Office 365.
Comment 186•6 years ago
|
||
(In reply to khagaroth from comment #184)
What's the plan for this after the death of old TB addons? This is still a commonly used thing in corporate/government e-mail.
Ideally, the sender would be skilled enough not to send a proprietary formatted email out on the internet with a silly expectation that everyone uses Microsoft Outlook. But you are right, it would be silly to expect organisations with professional IT departments to actually know what they were doing. Better the open-source community adapt to professional sending malformed mail, and that is what is happening.
So for now https://addons.thunderbird.net/en-US/thunderbird/addon/lookout-fix-version
Then they are looking to the future https://github.com/TB-throwback/LookOut-fix-version/issues/53
But they may not have to as according to the Thunderbird road map, this bug for 78 perhaps. http://lists.thunderbird.net/pipermail/maildev_lists.thunderbird.net/2019-November/002024.html
Comment 187•6 years ago
|
||
Regarding the comment "Ideally, the sender would be skilled enough not to send a proprietary formatted email", I just have to ask: what world do you live in? This bug was opened 19 years ago. REPEAT 19 years ago! If a format has been active and alive for 19 years it has long since passed the threshold to being a defacto standard even if it's not an official one. To live in an ivory tower and ignore that fact means you are alienating a large group of potential users of your product.
Do you really believe the average e-mail user has any idea what TNEF is or that it is a proprietary format? All they know is they get e-mails from some of their friends and cannot see all of the contents and have no idea why.
I'm a developer and I tried to use TB about 10 years ago and this was a show stopper for me because I just want to read my e-mail and have it work for all formats. I tried lookout at the time and it did not work or did not work right, and there were posts stating (I think) that it was no longer being maintained.
Comment 188•6 years ago
|
||
(In reply to PK from comment #187)
I'm a developer
Are you offering to assist in the development of this feature?
Comment 189•6 years ago
|
||
No. The only reason I mentioned being a developer is that developers are usually more tolerant of software that might not just work out of the box. They are willing to fiddle with it if necessary. The average consumer is not, or has no idea how to.
If the comment I was responding to had been "we don't have any developers interested in working on this" or "the TNEF format is a closely guarded secret and reverse engineering TNEF formatted e-mails will only give partial solutions" or other comments of that nature I would have thought that was a reasonable response and not said anything.
The reason I responded was because the original comment seemed arrogant and attitudes like that will prevent more mainstream adoption (assuming that is one of the goals of the thunderbird project).
Like I said, I had tried to adopt TB about 10 years ago (plus or minus) and have since moved on. Ten years ago my answer might have been different, but not now. I've stayed subscribed to this thread since then more for idle curiosity then anything else.
Comment 190•6 years ago
|
||
(In reply to PK from comment #189)
No. The only reason I mentioned being a developer is that developers are usually more tolerant of software that might not just work out of the box. They are willing to fiddle with it if necessary. The average consumer is not, or has no idea how to.
If the comment I was responding to had been "we don't have any developers interested in working on this" or "the TNEF format is a closely guarded secret and reverse engineering TNEF formatted e-mails will only give partial solutions" or other comments of that nature I would have thought that was a reasonable response and not said anything.
The reason I responded was because the original comment seemed arrogant and attitudes like that will prevent more mainstream adoption (assuming that is one of the goals of the thunderbird project).
Like I said, I had tried to adopt TB about 10 years ago (plus or minus) and have since moved on. Ten years ago my answer might have been different, but not now. I've stayed subscribed to this thread since then more for idle curiosity then anything else.
Maybe.... maybe with the cloud e-mail (office 365) the old Exchange/Outlook users may be migrated to a new platform and we stop seeing this. Your comment is right, I can't assume anything but that the developers are linux people that only consumes and relates to other linux people and they do not work with/collaborate with private companies that employ Exhange/Outlook. I did all the time and it was a pain to unpack winmail.dat files, that fortunately, 19 years later are still coming but less and less or LookOut Fix is doing it's job.
Comment 191•6 years ago
|
||
Hello, I'm currently maintaining lookout (fix version). Development is slow as I don't have as much time to work on the breaking changes in TB.
Unfortunately I've seen tnef files from office 365 accounts. Also there has been an uptick in tnef emails (at least in my industry) due to several large organisations upgrading from old windows servers. With many people either using google apps or outlook, many systems administratior simply don't know they have not configured their servers correctly.
You know if you have recieved a modern tnef email as it has the body in the tnef as .html rather than .rtf
Several administrators have stated it's not their problem to fix, hence why I originally started maintaining the addon.
Thunderbird would benefit greatly if the client could decode the format natively, as lets face it the lookout addon is janky and not to mention it has been 19 years. It is time to accept tnef format emails are here to stay
Comment 192•6 years ago
|
||
(In reply to dugite-code from comment #191)
Hello, I'm currently maintaining lookout (fix version). Development is slow as I don't have as much time to work on the breaking changes in TB.
Unfortunately I've seen tnef files from office 365 accounts. Also there has been an uptick in tnef emails (at least in my industry) due to several large organisations upgrading from old windows servers. With many people either using google apps or outlook, many systems administratior simply don't know they have not configured their servers correctly.
You know if you have recieved a modern tnef email as it has the body in the tnef as .html rather than .rtf
Several administrators have stated it's not their problem to fix, hence why I originally started maintaining the addon.
Thunderbird would benefit greatly if the client could decode the format natively, as lets face it the lookout addon is janky and not to mention it has been 19 years. It is time to accept tnef format emails are here to stay
Can you start transitioning the addon into the Thunderbird code itself? Maybe break it into pieces, and start stripping the pieces out of the addon and into Thunderbird? Is there anyone on here who can and will help him to do this? Thanks so much.
Comment 193•6 years ago
|
||
The tnef parser is already split off from the rest of the addon, however I believe the java based jtenf would be a better reference as it's had more development, lookout is just getting maintenance patches
Comment 194•6 years ago
|
||
Can those just go right into Thunderbird instead?
Comment 195•6 years ago
|
||
When I first commented on this bug in 2006, my manager at the time was an extreme Microsoft zealot who thought everyone should use Windows and Outlook, and that any platform that couldn't handle Outlook's "standard" format was brain-damaged by definition, and that the only solution worth considering was to abandon broken toys like Thunderbird (and Linux!) and use Outlook.
That was years ago, thankfully, and that particular manager moved on, and I eventually stopped seeing TNEF-formatted e-mail entirely.
And I retired a couple of months ago, so I really don't need to worry about the issue anymore. :-)
But if people are still seeing TNEF in their incoming e-mail, and if it's not feasible for them to get the senders to stop doing this, then I hope the Lookout extension can continue to be available.
Comment 196•6 years ago
|
||
TNEF unfortunately is still very prevalent in small to large business who use exchange server. It seems as if this is one of those things that will not die in the past.
It looks like someone from the Thunderbird team would have to integrate the function from the add-on to Thunderbird itself, as the maintainer is not working on the webextension currently.
Because TNEF only shows an attachment in Thunderbird, I cannot fully recommend it to my peers, or install it for people I know because this is a huge incompatibility issue that breaks emails from certain senders. In all my years of using Thunderbird, this is the only issue I've run in to.
Comment 197•6 years ago
•
|
||
It would be beneficial to all users. This is indeed much needed and increase compatibility/interoperability of Thunderbird. Without it currently, it makes TB looks like having a "bug" and not working properly!
Especially considering a solution already exists, why not to convert the existing plugin into an experiment (shall be trivial for the dev team) and pre-load it in TB like lightning before? That would be the quickest way to do before slowly integrating it to Core later on.
This bug has quite a large vote number so obviously something people need/want!
Comment 198•6 years ago
|
||
(In reply to Rich Wales from comment #195)
When I first commented on this bug in 2006,
...
But if people are still seeing TNEF in their incoming e-mail, and if it's not feasible for them to get the senders to stop doing this, then I hope the Lookout extension can continue to be available.
The "Lookout" extension is no longer supported.
This has been working for a long LONG time with the Lookout extension. That is no longer a solution (no longer compatible), so this bug needs to get fixed ASAP.
Thank you.
| Comment hidden (metoo) |
Comment 200•6 years ago
|
||
(In reply to Worcester12345 from comment #199)
Just had a user complaint about this. Saying the sender claims we are the only ones having this problem. It turns out we are also one of the only recipients using Thunderbird. This is sealing the fate for Thunderbird to go away sooner rather than later. I'm sure this is the same for thousands or more users of this program. As of right now, there is no workaround for this user, other than Outlook (or Office365). Please help, time is critical.
If you go to the lookout Github page there is a beta release available: https://github.com/TB-throwback/LookOut-fix-version/releases/tag/v3.0.00b1 The reason I haven't released it is I'm missing the version checking for backwards compatibility and I am missing event invite sample for testing
Comment 201•6 years ago
|
||
(In reply to dugite-code from comment #200)
(In reply to Worcester12345 from comment #199)
Just had a user complaint about this. Saying the sender claims we are the only ones having this problem. It turns out we are also one of the only recipients using Thunderbird. This is sealing the fate for Thunderbird to go away sooner rather than later. I'm sure this is the same for thousands or more users of this program. As of right now, there is no workaround for this user, other than Outlook (or Office365). Please help, time is critical.
If you go to the lookout Github page there is a beta release available: https://github.com/TB-throwback/LookOut-fix-version/releases/tag/v3.0.00b1 The reason I haven't released it is I'm missing the version checking for backwards compatibility and I am missing event invite sample for testing
This is to go with the 78.3.2 64-bit version. Is it compatible with that?
Any chance you can help write a patch to put this code into Thunderbird itself?
Thanks.
Comment 202•6 years ago
|
||
(In reply to Worcester12345 from comment #201)
Any chance you can help write a patch to put this code into Thunderbird itself?
Thanks.
Even if it is just a couple little patches, to make it closer. Break them into separate bugs to accomplish each task. This will get us ALL closer to having a functioning email client.
Thanks so much.
Comment 203•6 years ago
|
||
Yes that is for TB 78.x.
Unfortunately I am only the current maintainer and have only been working on keeping the existing code running with the various Thunderbird changes, I'm not actually hugely familiar with the actual de-coding side of the addon. Also there has been more work done in other libraries such as jtenf that need to be considered by anyone doing work in this space. Someone more experienced with the Thunderbird code would be better suited to tackle this issue.
Comment 204•6 years ago
|
||
As I said, even small bugs to chip away at the edges of this would be helpful. That way, it is less for an addon to do, and less to keep up in the long run.
Comment 205•6 years ago
|
||
Hello,
I've been struggling with this problem too since the upgrade to TB 78.x.
After some googling I've found a nice solution to this problem for my employer (I'm a Linux network admin) > server side tnef (winmail.dat) extraction/decoding with mimedefang + libconvert-tnef-perl + libfile-libmagic-perl.
As my post is OT, I will not go into details here... but can share my solution if there is interest.
@dugite-code
Many thanks for your efforts. Your addon served me well since I send our Exchange 2013 server more than 2 years ago into hell.
@ TB devs
TB is missing a lot of important features, but it's still the BEST solution on earth if you migrate from Exchange server.
I do appreciate your changes/improvements even when they break things at the beginning.
TB is getting better and better with every major release... Many thanks to you.
Regards
Darius
Comment 206•6 years ago
|
||
(In reply to d.spitznagel from comment #205)
As my post is OT, I will not go into details here... but can share my solution if there is interest.
Darius, I think it would be great if you could share the solution.
Comment 207•6 years ago
|
||
(In reply to Saulius Gurklys from comment #206)
(In reply to d.spitznagel from comment #205)
As my post is OT, I will not go into details here... but can share my solution if there is interest.
Darius, I think it would be great if you could share the solution.
You can find my text-based howto here...
https://www.goodbytez.de/howtos/mimedefang
Comment 208•6 years ago
|
||
(In reply to d.spitznagel from comment #207)
..
You can find my text-based howto here...
https://www.goodbytez.de/howtos/mimedefang
Thank you!
Comment 209•5 years ago
|
||
Today I discovered, that a "special" email with a winmail.dat attachment crashed my defang (convert tnef to mine only) implementation!
Disabling defang on server side let the mail pass through.
With our webmail interface I was able to read the mail. It has its own inline tnef viewer and showed me 4 attachments with 0 bytes in size.
Please implement tnef inline viewer capabilities ASAP!
I realy don't understand why webclients can do that but TB not:(
Please fix that!
Kind regards
Darius
Comment 210•5 years ago
|
||
(In reply to d.spitznagel from comment #209)
With extensive help from John Bieling the Add-on Lookout (Fix Version) has been updated to work for TB78.
The Thunderbird devs are well aware that this issue needs investigating as can be seen on this roadmap for TB78+ in 2021
| Comment hidden (metoo) |
Comment 212•5 years ago
|
||
(In reply to Worcester12345 from comment #211)
(In reply to dugite-code from comment #210)
(In reply to d.spitznagel from comment #209)
...
The Thunderbird devs are well aware that this issue needs investigating as can be seen on this roadmap for TB78+ in 2021I hope someone can back this up by giving this a top priority. Right now is has NO priority!
Thanks.
Please read https://bugzilla.mozilla.org/page.cgi?id=etiquette.html Advocacy is not needed in this bug report - so comments are now limited.
Updated•5 years ago
|
Updated•4 years ago
|
Description
•