Add support for winmail.dat / TNEF files?

[GoogleCodeExporter]

Hi!

Love Unarchiver!

Could you add supprt for TNEF winmail.dat files 
(http://en.wikipedia.org/wiki/Transport_Neutral_Encapsulation_Format), created 
by Outlook?

Original issue reported on code.google.com by tim.veri...@gmail.com on 1 Jun 2011 at 7:21

Attachments:

• winmail.dat

[GoogleCodeExporter]

It looks like it shouldn't be too hard to do, however, the question is how 
useful it would be in general. I'm not familiar with the format - under which 
circumstances would a user encounter it?

Original comment by paracel...@gmail.com on 1 Jun 2011 at 11:35

[GoogleCodeExporter]

I regularly receive these attachments from outlook users... I've tried to guide 
colleagues away from sending in this format, but it seems that there are 
several conditions which may trigger their generation (rather than attachments 
being sent transparently with the email).  Wikipedia mentions choosing RTF as 
the email format, and certain security conditions as triggers.

given that i trust theunarchiver to handle all my archives, it would mean a lot 
to me to have this annoying, recalcitrant format handled as part of my normal 
workflow.

there are a few apps out there which handle tnef files (i use TNEF's enough), 
but it requires launching, then opening the file, then selecting and saving the 
contents one-by-one!!

thanks so much for the quick reply, and thanks for an awesome app - its been 
invisibly taking care of business for years, now!

Regards, Tim, Melbourne

Original comment by tim.veri...@gmail.com on 1 Jun 2011 at 3:11

[GoogleCodeExporter]

If it helps, this commonly happens when receiving attachments from people who 
are using Outlook and have it set to produce "rich text" email messages rather 
than "HTML." It's not too much of a problem "in the wild," as most people don't 
use Outlook for their personal email, but it can be a problem when receiving 
email from companies where the issue of having Outlook misconfigured is 
company-wide.

The right course of action, of course, would be to email back saying that you 
can't open the attachment and ask the person to configure their client right or 
call their company's help desk to fix it for them, but that's not always an 
option...

Original comment by miguelpontes on 1 Jun 2011 at 3:49

[GoogleCodeExporter]

Forgot to link this, there's more info than you could possibly ever want about 
this subject in this Mozilla Mail/Thunderbird bug that is still open 10 years 
later: 
https://bugzilla.mozilla.org/show_bug.cgi?id=77811

Original comment by miguelpontes on 1 Jun 2011 at 3:53

[GoogleCodeExporter]

Well, I guess I will at least have a look to see how complicated it would be, 
and if it's worth it, when I get back to adding some more formats.

Original comment by paracel...@gmail.com on 1 Jun 2011 at 6:57

• Changed state: Accepted
• Added labels: Priority-Maybe, Type-Enhancement

[GoogleCodeExporter]

Wicked, thanks again

Original comment by tim.veri...@gmail.com on 2 Jun 2011 at 12:27

[GoogleCodeExporter]

Can I please Bump this feature. :)

Original comment by georg...@thoughtified.com on 25 Jul 2011 at 10:43

[GoogleCodeExporter]

My suggestion: Use the code from http://sourceforge.net/projects/tnef/

Original comment by Mento...@gmail.com on 8 Aug 2012 at 9:22

[GoogleCodeExporter]

Unfortunately, it is GPL, therefore unusable.

Original comment by paracel...@gmail.com on 8 Aug 2012 at 10:48

[GoogleCodeExporter]

The Unarchiver is also under GPL. What’s the problem?
When GPL is a really problem, you can add the tnef binary and call it from your 
code.

Original comment by Mento...@gmail.com on 10 Aug 2012 at 4:10

[GoogleCodeExporter]

The Unarchiver is LGPL, not GPL. And due to the design of XADMaster and the 
fact that it runs on many operating systems under various configurations, 
external binaries are really not an option.

Original comment by paracel...@gmail.com on 10 Aug 2012 at 4:29