TNEF and Winmail.dat attachments

Currently the email application in the N97 cannot open attachments sent from Outlook e-mail program, when it sends e-mails in the Transport Neutral Encapsulation Format (TNEF). Here is an explanation of the problem:
Have anybody succeeded in finding a workaround or a patch tha resolves this ?
Message Edited by autowinder on 22-Oct-2009 09:14 AM

Please refer the following post about how to disable TNEF in exchange 2010 server:
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

  • 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!

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

    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,

    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 ( [])
    by (Postfix) with ESMTPS id 507B122E53F2
    for <[email protected]>; Fri, 10 Jan 2014 10:45:39 +0100 (CET)
    Received: from (2a02:a60:0:2013:d4c5:1b5b:26da:54e0) by (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 (2a02:a60:0:2013:c4d:c9dc:c028:99f3) by (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 ([fe80::4aa:2b19:10bb:b3ff]) by ([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: []
    Content-Type: multipart/mixed;
    X-HEX2013-Disclaimer: true
    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:
    Technischer Support: [email protected]
    Sitz der Gesellschaft: Dortmund Handelsregister: HRB 19737 Amtsgericht Dort=
    Ust-IdNr: DE249338561 Gesch=E4ftsf=FChrer: Robin Tsch=F6pe, Timo Mankartz
    Jelastic Cloud Hosting, machen Sie Ihre Webseite hochverf=FCgbar und skalie=
    Jetzt 14 Tage kostenlos und unverbindlich testen! Mehr unter : http://www.j=
    Content-Type: message/rfc822
    Received: from (2a02:a60:0:2013:c4d:c9dc:c028:99f3) by (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 ([fe80::4aa:2b19:10bb:b3ff]) by ([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
    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-AuthAs: Internal
    X-MS-Exchange-Organization-AuthMechanism: 04
    X-Originating-IP: []
    X-MS-Exchange-Organization-OriginalServerIPAddress: fe80::4aa:2b19:10bb:b3ff%14
    X-MS-Exchange-Organization-Network-Message-Id: c0254cc7-4b09-4ea3-86cd-08d0dbffdba7
    Return-Path: [email protected]
    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

  • 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.

    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

  • 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.

  • 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

  • One user receiving WINMAIL.DAT attachments from one or two domains

    I have a single user in our organization that is RECEIVING WINMAIL.DAT attachments which contain PDF's from only one or two domains external to the organization.
    Let me be clear that he is not sending out WINMAIL.DAT attachments to anyone. I have tested sending him RTF emails with a PDF attachment from an external address and he is receiving them just fine. We are running two Exchange 2013 servers in
    HA configuration and this user is using Outlook 2010 for his email client. If he looks at these messages in OWA, they still have the WINMAIL.DAT attachment within OWA. I cannot find an answer for this anywhere, and this is not related to disabling TNEF on
    our exchange servers.  Does anyone have any ideas?  I would really appreciate the assistance.

    Did you try this article -
    If the above article did not help then you can try the following
    1) Create an external contact for sender email address from whom the email is sent to the affected user.
    Run the below command for that sender external contact
    Set-MailContact "External Contact" -UseMapiRichTexFormat Never
    Ask the user to send email once again to that affected recipient and see if it still occurs.
    Most likely the latter should fix your problem.
    Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.

  • 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.
    Here is a solution that Apple users can get for $30.  An Austrian program and APP called Letter Opener is the solution to seamlessly opening Winmail.dat files. 

  • 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.

  • 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

  • I get winmail.dat attachments from my Co. they will not open I tried notepad and got nonsence

    I just started with a new Co. And they send e-mail attachments as winmail.dat When I open I get junk. I've gone into applications in Options but all form still give me junk notebook ect...
    Any suggestions

    90 known files types using the '''.dat''' extension. <br />
    Ask your company's IT department or a co-worker who's been there for a while what program you should use to open those files.

  • TNEF Issue - Winmail.dat or messages stuck in submission queue

    Hi guys, 
    I've looked around the forums and have found people that have had submission queue issues when they set TNEF to $null or $false, and have found that the unified answer is to set TNEF to $true.
    I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
    I have both issues. If I set TNEF to $true, I encounter the winmail.dat file problem. If I set TNEF to $false or $null, I encounter the submission queue issue (submission queue states "A transient storage failure occured", and users get a queue
    expiration bounce). Neither of these states are acceptable. I cannot have messages stuck in the queue only to be expired, and I cannot have recipients in remote domains failing to receive attachments in emails. 
    Does anyone have a possible workaround that might resolve this particular situation? It seems that this has been an issue in Exch 2010.
    Current Environment Configuration:
    I am running Exchange 2013 SP1 Standard on both of my CAS/MBX servers, running on Server 2012 R2 patched to the latest updates. I have an inbound spam filter, but mail outbound is not filtered, therefore the spam filter on our side should not play a role.
    I do have not made any changes to the exchange default malware filter either. Other than this issue, mail is flowing correctly and as expected.

    I also see folks having issues with recipients in remote domains receiving winmail.dat files in some instances (with a .pdf or .xls file attached) if TNEF is set to $true.
    According to your description, my understanding is that all the remote domain's recipients would receive winmail.dat files when you send the message to them if TNEF is set to $true, right?
    The Winmail.dat file is used to preserve Rich Text formatting. Outlook uses it when sending a Rich Text-formatted message. During transport, the content of the message may be changed, preventing the receiving client from being able to read the formatting
    instructions. In other cases, the receiving client does not use or recognize the winmail.dat file.
    I recommend that you refer to the following article to solve the issue:
    Method 1: Change the default message format
    The sender can change the format of the email messages that they send by using the following steps:  
    On the Tools menu, click Options, and then click
    Mail Format.
    In Compose in this message format, click to select Plain Text, and then click
    NOTE: To send to certain recipients that use RTF format and others recipients that use plain text format, the sender must set the option for the recipient in either the Personal Address Book or the recipient's contact record.
    Method 2: Modify the recipient's entry in the Personal Address Book
    The sender can use the following steps to remove the RTF format from the recipient attribute in the Personal Address Book:  
    On the Tools menu, click Address Book.
    In Show Names From, click the Personal Address Book.
    Select the addressee that you want to set as plain text, and then click
    Properties on the File menu.
    In the SMTP-General tab, click to clear the Always send to this recipient in Microsoft Exchange rich text format check box, and then click
    Method 3: Change the specific contact format
    The sender can use the following steps to set plain text in the recipient's contact record:  
    Open the recipient's record in the Contacts folder.
    Double-click the recipient's e-mail address.
    In the E-Mail Properties dialog box, click Send Plain Text only under
    Internet Format.
    Method 4: Set the Outlook Rich Text Format Internet e-mail setting
    In Outlook 2003 and Outlook 2007, click Options on the Tools menu.
    Click the Mail Format tab.
    Click Internet Format.
    Under Outlook Rich Text options, click either Convert to HTML format or
    Convert to Plain Text format.
    Hope this helps!
    Niko Cheng
    TechNet Community Support
    The Winmail.dat issue is only part of the problem, as described in my original post. For these messages (which it's a different set of messages every time, and it's becoming impossible for me to track them all down), if I set exchange or outlook to encode
    the message in Rich Text, the message gets encoded and sent to the recipient. Some of our recipients will reject the message because it is rich text, others receive a winmail.dat file.
    However, if I set exchange to not encode messages (TNEF= $false or $null), the message becomes stuck in the submission queue and eventually times out with an error resembling "Storage Transient Failure". 

  • Problem with winmail.dat Attachments in our company

    First, i did read all Entries in this Community about winmail.dat, but there's no entry for my problem.
    We use exchange server 2010 and outlook 2010. All Mails are written as HTML-Mails. There's no RTF Mails in our company.
    The problem ist, our cio ist using a ipad with a hotmail mal address and most mails with attachments arrives as winmail.dat on the ipad.
    But not all!
    I could verify, that a Mail with doc, pdf, xls attachments was opened ok on a iphone4s (with ios6) but showed as winmail.dat on ipad3 (ios6) at the same time!
    Has anyone a explanation to this?

    Winmail.dat files are attachments sent by Microsoft mail applications (Outlook, Outlook Express or Exchange) on a proprietary RTF format called TNEF (transport neutral encapsulation format).
    An e-mail containing an winmail.dat attachment looks like an empty e-mail with only one attachment. The original e-mail information like subject, body and attachments is packed into a single winmail.dat file, which in some cases also receives a generic name like information01.dat.
    If you wanna open it, you should download a winmail viewer.
    Hope this help u!
    <Link Edited By Host>

  • Winmail.dat attachments after importing PST into online archive

    Hi, we enabled the online archive feature on one of our Office365 exchange account. Later, we used the PST capture tool to import a PST file into the archive. Now after importing, the user came back saying he sees winmail.dat files as attachments. Prior
    to uploading the PST to the online archive the attachments were visible normally. The PST file belongs to the same user. Its an old PST file attached to his mailbox since a long time. We then subscribed to the online archive plan for his account and used the
    PST capture tool for importing the emails. To isolate the cause of the issue we tried dragging an email with an attachment from themailbox to the online archive from within Outlook. The moved email appeared correctly with attachment in his archive. We have
    not tried importing the whole PST from within outlook, as the size of the PST is too large (32 GB). Could someone please help resolve the issue.
    Thanks in advance.

    I recommend that you post this in the Office 365 Exchange Online Forum:
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • 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": 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.

Maybe you are looking for

  • Phone not responsive after recent software update

    I have just updated my phone (iPhone 5) with the most recent software update and it's now "died".  It was 100% charged and I'm now faced with an unresponsive phone which just shows the "plug to iTunes" visual. Anyone else have the problem and know ho

  • MM period / Year Closing Activity and inventory Valuation ??

    Hallow Experts ! At the time of Period end, we close the Posting Period in Transaction Code - MMPV. So as a Result system opens Next posting period Automatically. (Please Correct if i am wrong). At a time two posting periods are open, Current and pre

  • Problem in Receiver File adapter :Module XML2PLAIN

    Hi Friends, I have a FILE -> FILE scenario ,In this when I am downloading the data in XML format it is getting downloaded successfully.The output look like this ... <b>I have only one field to be displayed in the output</b>. <?xml version="1.0" encod

  • Receiver FTP  Error

    Hi Experts In the receiver file adapter we are getting the following error while writing the file to FTP: Message processing failed. Cause: An error occurred while connecting to th

  • Scheduled start and Finish date .

    Hi Everyone, I am facing a problem in dates in creating a process order in Production . In the tcode COR1, when input the BASIC START DATE manually, the BASIC FINISH DATE ,scheduled start date and finished dates should get calculated automatically  a