The client had an Exchange 2010 environment with 2008 R2 DC’s , some of the users were complaining that every now and then they get Winmail.dat attachments and the Issue affects both Outlook and OWA users
After extensive troubleshooting we found out that there was a Firewall/ SMTP Gateway Watch Guard XTM device in place to receive the emails and it was striping out the header of the email that identify it as Rich Text formatted. This header is needed by the outlook client to interpret the winmail.dat attachment. When the email client cannot read the proper formatting of the email, it displays the attachment as a winmail.dat file
Before running towards the solution or editing the config of the SMTP gateway , it would be best to probably bypass the gateway and forward port 25 (TCP) directly towards the Hub Transport server, than test the issue again to see if its resolve. As now if are not getting the winmail.dat attachment and are receiving the emails fine then we can be sure its the SMTP gateway issue.
In our case, we made changes to SMTP-proxy on the Watch Guard to allow the header of type •X-MS-Has-Attach:* •X-MS-TNEF-Correlator:* •X-MimeOLE:* through the SMTP proxy.You may have to make similar changes to what ever SMTP gateway you have.
Hope this helps you to fix the issue in hand, for more visit our support options here
Latest posts by Shishir Chandrawat (see all)
- Exchange 2010 Std: Mailbox server has reached the maximum database limit of 5 Error RcrExceedDbLimitException - December 12, 2016
- Exchange 2010: Unable to add Mailbox Database copies on DAG member servers, Error: An error occurred while processing a request on server - December 12, 2016
- Unable to Mount Microsoft Exchange DAG Database, Error: Failed to determine the mount status of the active database copy - December 12, 2016