lidt googlen bragte flg.:
I too have variously been plagued with this winmail.dat affliction, and
as far as I can tell, the problem is that Microsoft Exchange servers use
the mysterious winmail.dat method of encoding attachments that are sent
from one Microsoft Outlook user to another through a Microsoft Exchange
server.
Of course, you clearly aren't using Microsoft Outlook for Windows (since
it would have magically decoded the attachment, leaving you none the
wiser), and are instead faced with trying to decode this mysterious
attachment...
Again, from what I've read, the real fix is for the sender to make a few
tweaks to their Microsoft Outlook to ensure that their copy of Microsoft
Exchange doesn't think it's sending to another Outlook user. It's easy:
they just have to indicate in their address book entry for you that you
cannot receive Rich Text Format (RTF) rather than the current setting
which assumes that you can and therefore must be running Outlook!
Getting your colleagues to change their address books so that you have
an easier time with their attachments might be, um, a bit tricky,
however.
Og "TNEF's enough" virker perfekt:
http://mac.softpedia.com/get/Utilities/TNEFs-Enough.shtml
--
MA @ 55.01.44N/11.50.39E -
www.ammentorp.org - fjern xyz fra mailadresse
-- and don't forget to boogie