Configure Outlook to not use Winmail.dat to send attachments

We already talked in this post about the Winmail.dat file, which is part of the proprietary TNEF format used by Exchange and Outlook to encapsulate attachments files, notes and meta-data inside mail messages: the main focus there was figuring out how to open these files when we receive them to other, non-Microsoft e-mail clients. Now we’ll approach the same issue from the other side, seeing how we can configure Outlook to stop sending its attachment files using the Winmail.dat.

Why should we do such a thing? The answer is based upon our previous post. Since it’s a proprietary format, there’s no (native) way to read these attachments for the e-mail receiver, unless he’s using Outlook aswell. This cuts out Thunderbird, Eudora, all Android clients, all Mac clients – including Outlook – and more. That’s an excellent reason to disable this feature, which is what we’re about to do.

We can achieve such result either in a centralized way, using the global MS Exchange settings for external domains, or on client-basis, by changing the options of each Outlook client. The choice, as always, is up to you, depending to your specific network configuration and/or scenario.

Disabling Winmail.dat via Exchange

You can enable or disable TNEF (Transport-Neutral Encapsulation Protocol, which is the format upon which the Winmail.dat file is based as explained here) in the following ways, depending on which Exchange version you’re using:

  • Exchange Online Dedicated: Open the Exchange Admin Center (EAC) and modify the TNEF conversion options by setting the Mail flow > Remote domains > Edit > Use Exchange rich-text format option to “Never“.
  • Exchange Online, Exchange 2013 & Exchange 2010: you can disable TNEF either by using the Exchange Management Console (see image below) or via the command-line, by using the TNEFEnabled parameter supported by the Set-RemoteDomain cmdlet to configure the TNEF conversion settings for remote domains. Here’s the command to disable TNEF:
    If you need additional information regarding the Set-RemoteDomain usage, or you want to take a look to all its supported commands, you can read this great KB guide.

exchange-2010-remote-domains

To get even more info regarding the TNEF and how to disable/enable it, you can also check out this other KB guide.

Disabling Winmail.dat using Outlook

If you’re not using MS Exchange or if the above method doesn’t work for your scenario you can also operate per-client basis by modifying the settings on your Outlook client: as usual, how to do that depends on the Outlook version.

Outlook 2007

Select Tools > Options > Email Format > Internet Options: from there, select Convert to HTML format.

outlook-2007-disable-tnef

Outlook 2010 e 2013

Select File > Options > Mail and scroll down to the bottom. From there, select Convert to HTML format.

outlook-2010-disable-tnef

If you prefer, you can also disable the TNEF for specific contacts by going into their Outlook Properties: you can do that by double-clicking their e-mail and then selecting “Outlook Properties” from the resulting modal (see screenshot below): from there, you can set the Internet Format options to make Outlook behave as you want to.

contact-outlook-properties

IMPORTANT: if you’re using this method, you can have some caching issues due. To remove the cache used by Outlook, just begin to type the contact e-mail address until the auto-complete feature kicks in: then, use the arrows to select the contact e-mail and tap DEL to delete it. The cache will be removed as well. Type again the full contact e-mail address and you’re set.

Disable TNEF using the Registry Editor

If all the above method fail, you can resort to entirely remove TNEF by altering your registry settings. It will be a rather harsh way of doing that, and we only suggest it to System Administrator who know what they’re doing. Take in mind that perform this task will also disable each Outlook TNEF-based feature, such as the built-in Voting System and Meeting Manager.

  • Close Outlook
  • Launch the Registry Editor from the Start menu by selecting Run, then typing regedit and pressing ENTER.
  • navigate through the following registry key:
    • Outlook 2007
    • Outlook 2010
    • Outlook 2013
  • Add a new DWORD entry with the following name: , and give it a value of 1.
  • Close the Registry Editor.
  • Restart Outlook.

And that’s it.

RELATED POSTS

About Ryan

IT Project Manager, Web Interface Architect and Lead Developer for many high-traffic web sites & services hosted in Italy and Europe. Since 2010 it’s also a lead designer for many App and games for Android, iOS and Windows Phone mobile devices for a number of italian companies.

View all posts by Ryan
  • Pingback: How to read/open Winmail.DAT files()

  • Cristi

    Hello.
    In registry, instead of DWORD I put QWORD; It’s ok? … or?

    • Are you using Windows 2008 Datacenter? If yes, use a DWORD (32-bit), you should have it. If you don’t have DWORD as an option you can use a QWORD (64-bit), which should evaluate as 1 aswell.

      • Cristi

        No, is a Windows 10.
        The user left with that PC and I want to know if is ok the mistake I did.

  • Cristi

    …anybody?

    • I’ve tested with a QWord and it seems to behave just fine. A 1 is a 1, it will evaluate as 1 with any type of data and shouldn’t cause problems.

      • Cristi

        Thanks

  • Pingback: How to disable winmail.dat outlook attach file | Everything Note !!!()