If you or your recipients are receiving a winmail.dat attachment inside a secure email, there will be a misconfiguration on the sender's side, either in Outlook or their Exchange. 

Please pass this information on to the sender's IT department:

 

When the Egress Gateway receives the email from the Exchange, it wraps everything up in a .switch file and occasionally a Winmail.dat attachment is included. Unfortunately in certain instances the Exchange may not be able to process the email correctly (a known issue with Microsoft -http://support.microsoft.com/kb/278061) before passing it on to Gateway.

The attachment seems to be lost already before Egress Switch processes the message for encryption. As the linked article suggests, it could be a variety of reasons so we have come up with the following suggestions:

  1. We encourage you to look at whether these senders are using RTF instead of the default HTML formatting or any of the causes listed in that article. This can even be on a per-recipient basis, ie. it will send as RTF to a specific person.

  2. Changing an attribute in the actual contact on the Global Address List may resolve the issue, below are a number of screenshots and steps for each version of Exchange:

Exchange 2000/2003:

  1. Run the Exchange System Manager program.
  2. In the left panel go to Global Settings | Internet Message Formats | Standard.
  3. In the context menu choose Properties and go to the Advanced tab.
  4. Set the Exchange rich-text format option into Never use.

                 

 

Exchange 2007/2010:

  1. Run the Exchange System Manager program.
  2. In the left panel go to Global Settings | Internet Message Formats | Standard.
  3. In the context menu choose Properties and go to the Advanced tab.
  4. Set the Exchange rich-text format option into Never use.

              

 

Exchange 2013:

  1. Open Exchange Management Shell.
  2. To see your current settings please run the following command:

Get-RemoteDomain | Where {$_.TNEFEnabled -ne $false}

    3. For each Remote domain, please run the following command:

    Set-RemoteDomain -Identity DomainName -TNEFEnabled $false

 

If you experience this issue please contact your Systems Administrator who will be able to resolve this issue.



Have more questions? Submit a request