In many situations or scenarios Microsoft Outlook, instead of regular (consumable by other mail clients) meeting invitations can start sending “windmail.dat” instead. This is a proprietary format that other mail clients (like Thunderbird, Mac mail clients, web clients) ignore as not readable.
List of situations and configuration switches that may cause Outlook to behave like this is long. And so is the solution list. In my case only the most aggressive solution worked.
I’ve read through entire slipstick.com’s article reading through every chapter, checking every detail, all for nothing. Even after applying every suggested solution, receivers of my meeting invitations were still getting forsaken
winmail.dat instead of regular invitation which they could accept or reject.
Finally, the solution was to block sending rich messages at Windows Registry level.
To follow this solution you need to:
- Close Outlook
- Hit Win + R type
regeditand hit Enter.
- Locate the
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Preferencesregistry key (for Outlook 2013; for other versions — refer to original article).
- Right click main Registry Editor’s window and select
DWORDitem from context menu.
- Name it
DisableTNEFand hit Enter to confirm.
- Double click it and in the
Valuedata box type
- Close the Registry Editor and restart Outlook.
This should solve your problem in most cases.
If it is still not solved (i.e. some of your contacts are still getting
winmail.dat) you must clear whole auto-complete cache, by closing Outlook again and restarting it with:
or by going to File > Options > Mail > Send Messages section and by clicking the
Empty Auto-Complete Lists button.
This will unfortunately — as the name says — clear all your contacts auto-complete cache forcing you to start typing email addresses by hand or using contacts list again.