Disabled TNEF and messages with PDF still arrive as winmail.dat

%3CLINGO-SUB%20id%3D%22lingo-sub-45224%22%20slang%3D%22en-US%22%3EDisabled%20TNEF%20and%26nbsp%3Bmessages%20with%20PDF%20still%20arrive%20as%20winmail.dat%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45224%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%20some%20of%20our%20customers%20and%20our%20users%26nbsp%3Busing%20Office%20365%20start%20see%26nbsp%3Bafter%20last%20builds%26nbsp%3BOffice%202016%20strange%26nbsp%3Bthings%26nbsp%3Babout%20sending%20e-mails%20with%20PDF%20attachments.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOutside%26nbsp%3Bworld%20complain%2C%20that%20they%26nbsp%3Breceive%20winmail.dat%20instead%20of%20original%20e-mail.%20I%20know%2C%20there%20are%20programs%20how%20to%20read%20this%20type%20of%20attachment%20and%26nbsp%3Brecover%20message%20but%2C%20it%26nbsp%3Bis%20not%20good%20for%20users%20and%20experience.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20is%20strange%20in%20this%20issue%2C%20is%20that%20at%20Office%20365%20side%2C%20the%20TNEF%26nbsp%3Bformat%20is%20disabled%20(set%20to%20%22Never%22)%20in%26nbsp%3Ball%20Remote%20Domains.%20Also%20registry%20key%20to%20disable%20TNEF%20on%20Outlook%202016%20side%20are%20set%20correctly.%20All%20name%20cache%20was%20deleted%20and%20records%20in%20address%20book%20check%20for%20settings.%20All%20of%20them%20are%20correct.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20other%20side%20still%20receive%20winmail.dat.%20The%20combination%2C%20which%20we%20tracked%20are%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3ESender%3A%20Outlook%202016%20with%20PDF%20attachment%2C%20at%20Windows%2010%20from%20Office%20365%3C%2FLI%3E%3CLI%3ERecipient%3A%20Outlook%2C%20every%20version%2C%20iOS%20and%20macOS%20and%20Windows%2C%20on%20Office%20365%20or%20different%20mail%20server%3C%2FLI%3E%3C%2FUL%3E%3CP%3EDo%20you%20see%20some%20other%20things%20to%20look%20at%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-45224%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45697%22%20slang%3D%22en-US%22%3ERe%3A%20Disabled%20TNEF%20and%26nbsp%3Bmessages%20with%20PDF%20still%20arrive%20as%20winmail.dat%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45697%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20to%20reply%2C%20Loryan.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20we%20did%20that%20on%20tenant%20level%20in%20Exchange.%20We%20also%20full%20patch%20all%20Outlook%202016%20clients%20and%20check%20their%20settings%20and%20they%20seems%20to%20be%20correct%20at%20contact%20or%20application%20level.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20now%20try%20to%20create%20explicit%20Mail%20Contacts%20to%20such%20problematic%20external%20users%20with%20TNEF%20disabled%2C%20maybe%20it%20helps.%20We%20also%20created%20Service%20Request%20to%20official%20support%2C%20but%20no%20progress%20so%20I%20also%20wrote%20here%20for%20sure.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-45663%22%20slang%3D%22en-US%22%3ERe%3A%20Disabled%20TNEF%20and%26nbsp%3Bmessages%20with%20PDF%20still%20arrive%20as%20winmail.dat%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-45663%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you've%20done%20it%20at%20the%20tenant%20level%20then%20it%20*should*%20be%20working.%3C%2FP%3E%3CP%3EThis%20article%20might%20help%2C%20but%20you've%20probably%20already%20done%20it%20all%3A%20%3CA%20href%3D%22http%3A%2F%2Fwww.deargeek.co.uk%2F2013%2F11%2Fhow-to-stop-office-365-sending-those-pesky-winmail-dat-attachments%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwww.deargeek.co.uk%2F2013%2F11%2Fhow-to-stop-office-365-sending-those-pesky-winmail-dat-attachments%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOtherwise%20I'd%20suggest%20creating%20a%20Service%20Request%20to%20see%20if%20perhaps%20the%20TNEF%20setting%20isn't%20actually%20being%20applied.%3C%2FP%3E%3C%2FLINGO-BODY%3E
MVP

Hello, some of our customers and our users using Office 365 start see after last builds Office 2016 strange things about sending e-mails with PDF attachments.

 

Outside world complain, that they receive winmail.dat instead of original e-mail. I know, there are programs how to read this type of attachment and recover message but, it is not good for users and experience.

 

What is strange in this issue, is that at Office 365 side, the TNEF format is disabled (set to "Never") in all Remote Domains. Also registry key to disable TNEF on Outlook 2016 side are set correctly. All name cache was deleted and records in address book check for settings. All of them are correct.

 

But other side still receive winmail.dat. The combination, which we tracked are:

 

  • Sender: Outlook 2016 with PDF attachment, at Windows 10 from Office 365
  • Recipient: Outlook, every version, iOS and macOS and Windows, on Office 365 or different mail server

Do you see some other things to look at?

2 Replies

If you've done it at the tenant level then it *should* be working.

This article might help, but you've probably already done it all: http://www.deargeek.co.uk/2013/11/how-to-stop-office-365-sending-those-pesky-winmail-dat-attachments...

 

Otherwise I'd suggest creating a Service Request to see if perhaps the TNEF setting isn't actually being applied.

Thanks to reply, Loryan.

 

Yes, we did that on tenant level in Exchange. We also full patch all Outlook 2016 clients and check their settings and they seems to be correct at contact or application level.

 

We now try to create explicit Mail Contacts to such problematic external users with TNEF disabled, maybe it helps. We also created Service Request to official support, but no progress so I also wrote here for sure.