GNOME Bugzilla – Bug 200232
application/ms-tnef support
Last modified: 2013-09-13 00:51:52 UTC
Support Outlook TNEF attachments. URL link goes to MSDN docs. See also http://world.std.com/~damned/software.html
There is source code to do this at http://world.std.com/~damned/software.html, apparently.
Doh. And I knew I'd seen that URL somewhere... I even searched all the other bugs in the dependency tree for it. [grumbles, gets coffee]
Has this now been fixed? I can now read TNEF attachments from my Outlook using colleagues (I'm using 0.14). However, my other Evo using colleague (also using 0.14 - both SuSE 7.1 Red Carpetted versions) can't read them...
No, nothing has changed in Evolution regarding this. Did you install an external tnef-parsing program? Or are you and the other Evo users reading your mail from different servers or something like that?
Sorry in delay in responding, must have missed the update mail about this bug... We've both got the software from std.com installed, but did before it worked [for me] as well. It only started working for me when I upgraded to 0.14. Now using 0.99.2 (colleague is on 0.99.1 I think - pretty sure he's not gotten around to upgrading yet) and the same situation, I can view TNEF attachments & MAPI encoded stuff, and he can't. ooh, one thought that's just occured to me is that I have Codeweavers WINE installed (which includes MAPI support of some description), not sure if he has - will check and report back.
Confirmed, colleague doesn't have WINE installed. Oh, and he's using 0.99.0. Will get him to install it, and see if that makes a difference... :)
upping to critical for tracking/triage purposes.
Well, a fruitfull morning on this one... Here's what we did on my colleague's machine: * Installed Codeweavers WINE * User config of WINE with GNOME setup * Upgrade of Evo to 0.99.2 After each stage we restarted Evo, and after the final stage he was finally able to open an attachment another colleague sent that was TNEF/MAPI encoded. So it looks like it was when the Evo RPM was installed with WINE already installed that it worked.
*** bug 207295 has been marked as a duplicate of this bug. ***
Larry has it pretty much working already.
...without WINE?
yes without wine. I've got a preliminary release waiting for me to fix a couple os small things.
*** bug 219385 has been marked as a duplicate of this bug. ***
okay the gtnef module in gnome-cvs should cover this bug. I'll be making a release of it before the next major evolution release.
Fixed by gtnef, if there are problems with gtnef it should be a new bug
Where can one find a package for gtnef? I tried downloading the cvs version but it wants a newer gal than what ximian is currently distributing. Thanks
As gtnef seems to be in deep-sleep, shouldn't this bug be re-opened? (If there isn't any other application that can do the same thing as gtnef and integrated with evolution)
I vote 1+ that this is reopened. It is confusing that this item, which is probably a very common one, is not addressed.
I'd like to confirm that this bug exists in the 1.4 tree, due to gtnef never having been ported to GNOME2 (I suspect). I'd not noticed it till this morning, I switched from IMAP to POP3 for accessing my company's Exchange 5.5 server due to bug#234067 and in doing so I discovered that it clearly hadn't been Evolution decoding all the TNEF attachments I'd been getting sent, but Exchange. Can this bug be reopened please?
There are a variety of tools to decode TNEF attachments, so this shouldn't be too hard to integrate, I think. And I do think this is important-- We've got the transparency on DOC, XLS, and PPT, file formats, and this is something very similar. Marking 2.0.
is this really a 1.5.2 targeT?
Well it has to be 1.5.2 if its a feature we decide to add, however I don't see that we exactly have time this time around. I also think this can be handled externally.
No time. Can be external or next major release.
closing as discussed on irc with gerardo. please also see bug 252961.
a plugin for this is included in the unstable evolution release 2.11.5 and in the upcoming stable release 2.12. closing as fixed.
Let me just specify the plugin name "TNEF Attachment Decoder" For those who need it very urgently can just get it from latest head.