When Salesforce receives an inbound email via Email-to-Case, the attachment appears as a file named winmail.dat instead of the original file the sender attached.
The winmail.dat attachment behavior is a known issue with Microsoft Outlook when it uses an Exchange Server to send emails. This issue originates outside of Salesforce — it is not caused by the Salesforce inbound messaging system.
A winmail.dat file is generated when:
Microsoft Outlook automatically converts email attachments into a winmail.dat TNEF file when the outgoing email format is set to Rich Text Format (RTF). Email clients that are not Microsoft Outlook — including the Salesforce inbound email processor — cannot decode TNEF files, so the attachment arrives as winmail.dat instead of the original file.
This is a sender-side configuration issue in Microsoft Outlook or Exchange Server, not a Salesforce bug.
To prevent inbound attachments from arriving as winmail.dat in Salesforce Email-to-Case, the sender's Microsoft Outlook configuration needs to be updated to use HTML or Plain Text email format instead of Rich Text Format (RTF).
Option 1 — Change the default format for a specific contact in Outlook:
Option 2 — Change the global default email format in Outlook:
Option 3 — Exchange Server-level fix (for administrators):
An Exchange Server administrator can configure the server to convert RTF to HTML for outbound SMTP messages, preventing TNEF encoding entirely.
After the sender updates their format, future emails from that sender arrive in Salesforce Email-to-Case with properly attached files.
Note: This change must be made by the email sender or their IT/Exchange administrator. Salesforce administrators cannot resolve this issue from within Salesforce.
000385576

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.