How do I open winmail.dat attachments

When receiving a winmail.dat attachment I am unable to open it.

You could try the LookOut! add-on.
https://addons.mozilla.org/en-US/thunderbird/addon/lookout/
It appears not to have been updated recently, but there are recent comments suggesting it is still functional.
There are some standalone tools for converting these files, e.g.
http://www.winmail-dat.com/
and I think you will be able to find some on-line converters too.
You might also want to tell your correspondents that their attachments are of no use to you, and direct them to this article:
http://support.microsoft.com/kb/278061

Similar Messages

  • How do i open winmail.dat attachments in mail

    How do i open winmail.dat attachments in mail ?

    Having problems with Winmail.dat attachments?  This is really Windows problem but their hubris will not allow them to admit it. 
    Windows does have a global fix for this problem but it is not a general patch - in their KB there is a fix for Exchange servers which cause the winmail.dat problem but most users don't know about it or have it implemented. 
    http://support.microsoft.com/kb/138053http://
    Here is a solution that Apple users can get for $30.  An Austrian program and APP called Letter Opener http://www.creativeinaustria.com/http:// is the solution to seamlessly opening Winmail.dat files. 

  • How do I open Winmail.dat?

    How do I open Winmail.dat?

    ajlayne wrote:
    In Outlook, I changed the setting for how the mail sent to each typoe to resolve the issue. I created one email per setting and addressed to both people on their corporate exchange account (same server for both) and their gmail accounts. This is where the confusion arose since one phone receives fine and the other doesn't. I used Gmail as an alternate mail client with the same result.
    So basically I used two different clients each time sending to four addresses two are located on each phone. Phone A always receives a winmail.dat file no matter which client or email address is used. Phone B always receives the attachment in it's correct format.
    I took it a step further and used the phones to test sending. Even if I use Phone A to send to the other account on Phone A, winmail.dat is received. If done from Phone B to Phone A, Phone A winmail.dat persists. Phone A to Phone B correct format is received. I'm thinking there is a setting somewhere on Phone A I'm not aware of that was somehow changed since it is not mail client dependant nor recipient mail server dependant based on the testing results.
    This is a Microsoft Windows setting with Microsoft Outlook or within the Exchange Server gateway in general.   These winmail.dat files have been arriving on Linux, BSD, OS X, Tru64 Unix, ULTRIX, Solaris and many other servers for many years, too — unfortunately, everybody that's using non-Microsoft clients and tools encounters these files from time to time.  The winmail.dat is a Windows Mail data file, after all.
    If the mail client or if the mail server gateway sends a mail message to an iOS device — or many other "foreign" mail clients — that involves a winmail.dat file generated by the sending client or generated by the originating mail server gateway, then iOS will show the winmail.dat file.  Like many other mail clients, the iOS mail client does not decode, process nor create these winmail.dat files.  (Most clients simply treat these winmail.dat files as an arbitrary attachment on the message.)
    Send the same messages to the same email addresses and read those messages via another mail client — one that doesn't have winmail.dat support — and you'll see the exact same behavior; a wad of attached winmail.dat data.
    From Microsoft: How to Prevent the Winmail.dat File from Being Sent to Internet Users.  In short, either the Outlook client settings or the Exchange Server (IMC) settings will need to be changed here.

  • How to open winmail.dat attachments???

    Hi, this is my first use of this discussion forum, so here goes: Can anyone tell me how to open attachments I am sent on a regular basis that are winmail.dat attachments???

    Search Google for "winmail.dat mac" and you'll find many solutions
    Also note that this forum is for troubleshooting Apple Software Update for Windows, a software package for Windows designed to update Apple products that run on Windows, and not related to your issue, so you should really post search/post your question in the Mac OS X forums

  • How can I get Mac mail to open winmail.dat attachments on lion 10.7.3

    How can I get Mac mail to open letter attachments winmail.dat??   (Lion 10.7.3) Any help appreciated...

    Sorry peterskine,
    it's true in part. There's more then one article on the subject "Recipients receive a winmail.dat attachment":
    http://office.microsoft.com/en-gb/outlook-help/recipients-receive-a-winmail-dat- attachment-HA010153018.aspx?CTT=1
    The odd thing is that my colleague and me use the same release mountain lion and we received the same email from someone on Outlook2007. He received the mail with the attachment, whilst I saw a "Winmail.dat". It already happened to me on snow-leopard, some month ago. Up til today I don't know what the difference between our machines is.
    But it is interesting: the same OS, the same mail-clients (Apple Mail) and still different results.
    Note: on my machine it used to work properly. It just suddenly happened that I started to receive winmail.dat files in stead of proper attachments.
    When I have more time on hand, I cant try to find out why this happens.

  • How can i open WINMAIL.DAT attached to e-mails ???

    Hi,
    anybody knows how to open attached WINMAIL.DAT in e-mails (Yosemite 10.10.3)
    Thanks.

    See the suggestion by thomas_r.
    Get a copy of TNEF
    HOW TO OPEN WINDAT FILES

  • Opening  winmail.dat files

    How can I open winmail.dat files on a mac osx 10.4.4?
    Thank you Ron

    The Apple Mail Plug-in OMiC process this Microsoft Outlook winmail.dat files.

  • I recently purchased an Iphone 6plus and I am receiving pdf attachments that are shown as winmail.dat attachments on the phone. When I check e-mail via  my macbook pro the attachment is a pdf and I can open it. Why is this happening?

    I recently purchased an Iphone 6plus and I am receiving pdf attachments that are shown as winmail.dat attachments on the iphone. When I check the same e-mail on my macbook pro the attachment is a pdf and I can open it. Why is this happening?

    I had this problem too after i upgdatd to OS X Mavericks... only the songs on my iphone 5s that i purchased from itunes would play.
    i read something about it being a syncing issue. when you plug your phone into your computer with the usb cable, the person said to switch from automatic syncing of itunes to the "manual" option. mine was already set to manual so i wasn't sure anything would work. BUT, when i plugged my phone into my computer, it started to sync all of my music on my phone again (top of itunes bar where song playing/time is listed said "now syncing 123/534 songs to x's iphone"). once that was completed, i checked the music app on my iphone and everything was back to normal!
    so, i would suggest setting your music syncing settings to manual if you haven't tried that yet!
    hope this helps!

  • Question:  how to read winmail.dat attachments from others

    Based on a recommendation from an AppleCare rep, I downloaded "TNEF's Enough" so I could read winmail.dat attachments from others.  It won't work and when I called again, I was told AppleCare doesn't support third party apps.  How do I activate it?  I tried double clicking on it and nothing happened.

    http://www.joshjacob.com/mac-development/tnef.php

  • Open winmail.dat files?

    Anyone know how to open winmail.dat files?  I've been getting email attachments which I can't open on my MBP. 

    Hi ,
    The person that is sending you emails, has chosen in Outlook, to use the RTF format, for emailing and or specifically for emailing you. Perhaps this is default Outlook behavior at times.
    This results in the winmail.dat file, which is the RTF format, of the attachments that were intended for you.
    If the user would configure Outlook, to use the HTML (web)  format, for emails, then you would receive the attachments as intended. As well as anybody else.
    Apple mail and other mail systems, do not understand the RTF (rich text) format, and probably have to pay Microsoft licensing fees, to be able to use this format.
    The options, for setting this in Outlook, differ for different versions of Outlook, but are found generally under
    Tools > Address book, for setting a specific person to , use HTML format, and not RTF format, that persons email.
    Also, under "Tools" > "Options", > "Mail format", for setting that all emails, will use the HTML format, instead of the RTF format.
    More info
    http://support.microsoft.com/kb/278061

  • Winmail.dat Attachments are received whether TNEF is disabled or not

    Hi,
    we've got some issues when sending emails to some linux recipients, that attachments or s/mime signed emails are converted to the dreaded winmail.dat attachements. 
    On Exchange 2010 i've just configured the corresponding remote domain (or the default one) to disable TNEF sending to this mail domain.
    Apparently with Exchange 2013 this setting does not work anymore. With setting the parameter "TNEFenabled" to $false, the recipients still get winmail.dat attachments.
    do you have any idea how to work this out?
    Kind regards,
    Peter

    Hi,
    attached you will find the headers of an email which got that issue.
    Return-Path: <[email protected]>
    X-Original-To: [email protected]
    Delivered-To: [email protected]
    X-No-Auth: unauthenticated sender
    X-No-Relay: not in my network
    Received: from DOX13FE02.hex2013.com (DOX13FE02.hex2013.com [128.127.69.77])
    by web31.dogado.de (Postfix) with ESMTPS id 507B122E53F2
    for <[email protected]>; Fri, 10 Jan 2014 10:45:39 +0100 (CET)
    Received: from DOX13BE03.hex2013.com (2a02:a60:0:2013:d4c5:1b5b:26da:54e0) by
    DOX13BE01.hex2013.com (2a02:a60:0:2013:c4d:c9dc:c028:99f3) with Microsoft
    SMTP Server (TLS) id 15.0.775.38; Fri, 10 Jan 2014 10:45:41 +0100
    Received: from DOX13BE01.hex2013.com (2a02:a60:0:2013:c4d:c9dc:c028:99f3) by
    DOX13BE03.hex2013.com (2a02:a60:0:2013:d4c5:1b5b:26da:54e0) with Microsoft
    SMTP Server (TLS) id 15.0.775.38; Fri, 10 Jan 2014 10:45:40 +0100
    Received: from DOX13BE01.hex2013.com ([fe80::4aa:2b19:10bb:b3ff]) by
    DOX13BE01.hex2013.com ([fe80::4aa:2b19:10bb:b3ff%14]) with mapi id
    15.00.0775.031; Fri, 10 Jan 2014 10:45:40 +0100
    From: Peter Stutzinger <[email protected]>
    To: "[email protected]" <[email protected]>
    Subject: TNEF Testmail
    Thread-Topic: TNEF Testmail
    Thread-Index: Ac8N6LQ/yN5XQruBSFWwYuW7AIuW3g==
    Date: Fri, 10 Jan 2014 10:45:39 +0100
    Message-ID: <[email protected]>
    Accept-Language: en-US, de-DE
    Content-Language: de-DE
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator: <[email protected]>
    MIME-Version: 1.0
    X-Originating-IP: [128.127.69.74]
    Content-Type: multipart/mixed;
    boundary="_00cbcf5e-3076-4ee0-8a39-c8c8f01132f8_"
    X-HEX2013-Disclaimer: true
    --_00cbcf5e-3076-4ee0-8a39-c8c8f01132f8_
    Content-Type: text/plain; charset="iso-8859-1"
    Content-Transfer-Encoding: quoted-printable
    Herzliche Gruesse aus Duesseldorf
    Peter Stutzinger, Enterprise Architect - Messaging
    dogado Internet GmbH
    Saarlandstr. 25
    44139 Dortmund / DE
    Tel.: +49 (231) 28 66 20 0
    Fax: +49 (231) 28 66 20 20
    Profil auf XING: http://www.xing.com/profile/Peter_Stutzinger
    Corporate-Blog: http://www.webhostingblog.de
    Twitter: https://twitter.com/dogado
    Facebook: https://www.facebook.com/dogado
    Technischer Support: [email protected]
    Supportsystem: http://support.dogado.de
    Sitz der Gesellschaft: Dortmund Handelsregister: HRB 19737 Amtsgericht Dort=
    mund,
    Ust-IdNr: DE249338561 Gesch=E4ftsf=FChrer: Robin Tsch=F6pe, Timo Mankartz
    Jelastic Cloud Hosting, machen Sie Ihre Webseite hochverf=FCgbar und skalie=
    rbar!
    Jetzt 14 Tage kostenlos und unverbindlich testen! Mehr unter : http://www.j=
    elastic.de
    --_00cbcf5e-3076-4ee0-8a39-c8c8f01132f8_
    Content-Type: message/rfc822
    Received: from DOX13BE01.hex2013.com (2a02:a60:0:2013:c4d:c9dc:c028:99f3) by
    DOX13BE03.hex2013.com (2a02:a60:0:2013:d4c5:1b5b:26da:54e0) with Microsoft
    SMTP Server (TLS) id 15.0.775.38; Fri, 10 Jan 2014 10:45:40 +0100
    Received: from DOX13BE01.hex2013.com ([fe80::4aa:2b19:10bb:b3ff]) by
    DOX13BE01.hex2013.com ([fe80::4aa:2b19:10bb:b3ff%14]) with mapi id
    15.00.0775.031; Fri, 10 Jan 2014 10:45:40 +0100
    Content-Type: application/ms-tnef; name="winmail.dat"
    Content-Transfer-Encoding: base64
    From: Peter Stutzinger <[email protected]>
    To: "[email protected]" <[email protected]>
    Subject: TNEF Testmail
    Thread-Topic: TNEF Testmail
    Thread-Index: Ac8N6LQ/yN5XQruBSFWwYuW7AIuW3g==
    Date: Fri, 10 Jan 2014 10:45:39 +0100
    Message-ID: <[email protected]>
    Accept-Language: en-US, de-DE
    Content-Language: de-DE
    X-MS-Has-Attach: yes
    X-MS-Exchange-Organization-SCL: -1
    X-MS-TNEF-Correlator: <[email protected]>
    MIME-Version: 1.0
    X-MS-Exchange-Organization-OriginalSize: 18165
    X-MS-Exchange-Organization-OriginalArrivalTime: 10 Jan 2014 09:45:39.7572
    (UTC)
    X-MS-Exchange-Organization-MessageSource: StoreDriver
    X-MS-Exchange-Organization-MessageDirectionality: Originating
    X-MS-Exchange-Organization-Id: 00000000-0000-0000-0000-000000000000
    X-MS-Exchange-Organization-AuthSource: DOX13BE01.hex2013.com
    X-MS-Exchange-Organization-AuthAs: Internal
    X-MS-Exchange-Organization-AuthMechanism: 04
    X-MS-Exchange-Organization-BCC:
    X-MS-Exchange-Organization-OriginalClientIPAddress: 128.127.69.74
    X-Originating-IP: [128.127.69.74]
    X-MS-Exchange-Organization-OriginalServerIPAddress: fe80::4aa:2b19:10bb:b3ff%14
    X-MS-Exchange-Organization-MessageLatency: SRV=DOX13BE01.hex2013.com:TOTAL=0
    X-MS-Exchange-Organization-MessageLatency: SRV=DOX13BE01.hex2013.com:TOTAL=0
    X-MS-Exchange-Organization-MessageLatencyInProgress: LSRV=DOX13BE01.hex2013.com:TOTAL=0;2014-01-10T09:45:40.757Z
    X-MS-Exchange-Organization-Network-Message-Id: c0254cc7-4b09-4ea3-86cd-08d0dbffdba7
    Return-Path: [email protected]
    X-MS-Exchange-Forest-ArrivalHubServer: DOX13BE03.hex2013.com
    X-MS-Exchange-Organization-Cross-Premises-Headers-Processed: DOX13BE03.hex2013.com
    X-MS-Exchange-Organization-HygienePolicy: Standard
    X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
    X-MS-Exchange-Organization-Recipient-Limit-Verified: True
    X-MS-Exchange-Organization-Transport-Properties: DeliveryPriority=Normal
    X-MS-Exchange-Organization-Prioritization: 1
    X-MS-Exchange-Organization-Rules-Execution-History: TransportVersioned.Hosting Transport
    Restrictions%%%TransportVersioned.Disclaimer internal 970167
    eJ8+ImZ1AQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEJgAEAIQAAADUwQ0Y0RUY3
    AC8AcwBpAGcAbgBlAGQAAAAAAB8ADDoBAAAACgAAAEUAbgBVAHMAAAAAAOElDQo=
    --_00cbcf5e-3076-4ee0-8a39-c8c8f01132f8_--

  • Winmail.dat attachments

    We are running a Tiger Server for our mail service, several of our business clients keep on sending us winmail.dat attachments, I know why these are generated and that my users can use TNEFenough but they're irritated by the whole situation !! mutterings about using PCs (I think crap) ! is there anything I can do at the mail Server to remove this encoding so that my users receive ordinary attachments ? the senders aren't interested in resolving what to them isn;t a problem !

    Changing anything with Outlook in this regard affects messages sent with Outlook only, not with messages sent by the iPhone's Mail client. And if you are sending messages with your Exchange account using the Exchange SMTP server with the iPhone's Mail client, changing your Gmail account settings won't have any affect on this.
    Are you sending messages with your Exchange account and SMTP server, or with your Gmail account and SMTP server?
    I'm not sure how an ATT######.dat file is included when not using AT&T's SMTP server to send the message - the message is being sent by the Exchange SMTP server, but I'm not sure how such a file would be included regardless.
    If you are also accessing your Gmail account with the iPhone's Mail client, does the same occur when sending messages with your Gmail account and SMTP server?
    If not, the problem lies with the SMTP server used to send messages with your Exchange account or at the Exchange server.

  • Can't open "winmail.dat"

    Hi!
    I'm need help to open winmail.dat. "Ytnef" not working. The thunderbird plugin "lookout" not working too...I choose "winmail.dat" at attachments, "open" and nothing is going on there.
    Are anybody solved such problem?

    The Apple Mail Plug-in OMiC open winmail.dat files.

  • Outlook 2007 Clients receiving winmail.dat attachments

     I am running Exchange 2007 on Windows 2003 R2 64 bit.  End users run Outlook 2007 on XP  sp2 machines.  Users randomly receive winmail.dat attachments in their email.  Does anyone know how to fix this on Exchange 2007?

    That is what I find most interesting, is what Microsoft has released regarding winmail.dat files.  It seemed to me that it was the mail compliance of the recipient that was causing these files to appear.  Only recently have I found more discussion on the topic on other forums, including here, showing that it is also caused by other situational basis other than the recipients method of viewing the email...unless I misunderstood all along and it would seem so.  Because in my mind, it would make more sense if the recipients mail server is the cause of the issue, not so much the recipient.  if the recipients mail server does not interpret TNEF than could all their customers be experiencing this?  i must assume this because it would mean that if the recipient accesses their email via a webmail client that does not support TNEF, than they receive a winmail.dat...however if they check their email again from outlook or someform of email program that does understand TNEF, than shouldn't the email and attachments show up properly?  It is my experience that they do not.  That is how I began thinking that it must be the mail server of the recipient that is causing this.
    I tried setting the 1 user's outlook to send only plain text...I am waiting to hear the results, but they were already set to send in HTML only.  By my understanding is that TNEF is created only when RTF is used for outbound email, and HTML and Plain Text do not create TNEF...punch me if I'm wrong

  • Winmail.dat attachments from Exchange 2013 on premi and Hosted Office 365 set up.

    Hello TechNet,
    I have an on going situation with winmail.dat attachments. I currently have a ticket open with Microsoft, but I want to see if anyone has personal experience with this. Here is the rundown.
    We have migrated from an Exchange 2007 server to Exchange 2013 for the migration to Office 365. We also have a hosted Office 365 server with half of our mailboxes in the cloud and half of them on the Exchange 2013 on premise server.
    The current settings for TNEFEnabled:
    On Premise: False
    Hosted: False
     Whenever a internal email with a calendar invite(exchange calendar, go to meeting) goes out to any external domain the recipients receive winmail.dat.
    When settings for TNEFEnabled On Premise and Hosted are set to true both calendar invites and PDF, Excel attachments etc the recipients receive winmail.dat.
    When speaking with Microsoft about this issue. The representative was watching me through a LogMeIn session as I set both TNEFEnabled false on both on Premise and Hosted.
    This is really frustrating as many employees depend on this to be fully functional, and to be honest am tired of dealing with this.
    I need help.
    -Ben

    I am having the same issue.
    Luckily I have only migrated my own mailbox to office365.
    Tried both true and false TNEFEnabled on both onpremise and office365 via powershell and confirmed that both have been applied.
    If I send the email as a plain text then the attachment works ok. If I send it as HTML then I get winmail.dat.
    The above KB doesnt really help me, sending plain text emails is like going back to the dark ages!
    I am sending from outlook to outlook (I send from my external email address, to my work email address and visa-versa)
    If someone with an onpremise mailbox sends me an email, the attachment works ok.
    If someone sends me an attachment via hotmail, the attachment works ok.
    It seems to only effect emails I send to myself through outlook, i am sending it through a POP3 account to our onpremise exchange 2010 which forwards the email to office365

Maybe you are looking for

  • How to prevent release of PO by not more than one officials at a time

    HI Two questions. 1) For PO I am configuring the release process for one Client. I successfully configured a release strategy with 4 official names. GM. SGM, VP and CEO. When I tried to do individual release through ME29N, I am able to see all the 4

  • Saving an edit in Photoshop Elements 11

    I have edited an image in Elements 11, but I can't save it. When I 'save as' it saves the photoshop desktop and not the image. I am obviously doing something pretty stupid, but what? Can anyone tell me how to save my edited version of the pic I have

  • Object Class and Object Id for material Determination tables.

    I want to know what is the Object Class and Object Id for material Determination records to verify tables CDHDR and CDPOS. The purpose is to know the changes done by the different users for material determination records. Can any one help.

  • Integrating Excel with Java

    Hi, How can Excel be integrated with Java such that if a user is working on an Excel , my Java application should be able to capture all the events from Excel Sheet. I have looked into POI, but it seems to me , it can read and wriite to Excel from Ja

  • Closing a web page

    Easy one here - I've created a shockwave app that a client will have open in it's own browser window. When a user clicks an exit button within the shockwave app, I want the window it's playing in to close so they'll be taken back to whatever page the