Winmail.dat files

Question

Is there anyone competent enough to solve the winmail.dat conversions of files in outlook? And the answer cannot be to request the sender to change his/her settings because 90% of the time that is just not an option in the commercial world. the other 10% don't understand what to change anyway. What would really help if the original file extension could be named somewhere so that one can at least change it oneself and recover the attachment. For now using Gmail is the only way around this nuisance. Regards

Answer 1

Hi @Hannes Minnaar

I understand your frustration. In many business environments, asking external senders to change their mail settings is often not a practical solution.

The winmail.dat file is typically generated when a message is sent using Microsoft's proprietary TNEF (Transport Neutral Encapsulation Format). Although Outlook provides options intended to prevent TNEF formatting, there is currently no recipient‑side feature in Outlook that automatically restores the original attachment type once a winmail.dat file is received.

Please note that we are not Microsoft Support, this is a user‑to‑user support forum. We cannot make changes to product design or influence feature development. What we can do here is clarify the behavior and help each other understand the current limitations.

Thank you for your patience and understanding.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

Answer 2

Winmail.dat files are created when messages are sent using Outlook Rich Text Format with TNEF (Transport Neutral Encapsulation Format). The Winmail.dat attachment can contain the formatted message, embedded objects, and any regular file attachments. Non‑Outlook clients or systems that strip TNEF cannot interpret this file, so the original attachment type and name are not exposed in a usable way.

There is no supported way in Outlook to automatically recover or expose the original file extension from Winmail.dat on the receiving side. The supported solutions focus on preventing TNEF/Winmail.dat from being sent in the first place:

1. Disable TNEF in Outlook globally (for senders under the same admin or where configuration is possible):
   • In Outlook: File > Options > Mail.
   • Under “Compose messages in this format”, select HTML or Plain Text instead of Rich Text.
   • This prevents Outlook from using TNEF for most outgoing messages.
2. Disable TNEF via registry (for managed environments):
   • Configure the DisableTNEF registry entry under HKEY_CURRENT_USER\Software\Microsoft\Office\<version>\Outlook\Preferences to 1 to ensure Outlook does not use TNEF for outgoing messages unless a feature requires it.
3. Configure Exchange/Exchange Online to remove TNEF for external recipients:
   • Admins can set TNEF conversion options on remote domains or per recipient so that messages leaving the organization are converted to HTML or plain text instead of TNEF. This prevents external recipients from getting Winmail.dat.
4. Per‑message control (for senders who can change individual messages):
   • In Outlook, on a specific message, use the Format Text tab and choose HTML or Plain Text so that TNEF is not used for that message.

If a message has already been received as Winmail.dat and the sender cannot change settings, Outlook does not provide a built‑in, supported way to extract or infer the original attachment name or extension from that file. The practical and supported mitigation is to configure senders’ Outlook/Exchange environments to avoid TNEF for recipients that do not use Outlook.

---

References:

• How message format affects email messages
• Exchange Server: TNEF conversion options
• TNEF conversion options
• Message format and transmission in Exchange Online