Right-click the mail-enabled contact in the right-pane, and then click Properties.To do this, click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.Ĭlick the container where the mail-enabled contact is located.Open Active Directory Users and Computers.To resolve this issue, change the settings in Active Directory Users and Computers so that the mail-enabled contact does not use RTF as the default message format. Note: This typically occurs if the mail-enabled contact is added by using a script. The mAPIRecipient attribute is missing, is set to null, or is set to true.

The default message format is set to Rich Text Format (RTF).This issue may occur if the following conditions are true for the mail-enabled object on the Exchange computer: When a Microsoft Exchange Server user sends a Simple Mail Transfer Protocol (SMTP) e-mail message with an attachment to a mail-enabled contact in the Global Address List, the mail-enabled contact may receive a Winmail.dat file attachment with the e-mail message instead of receiving the correct file attachment. Please read all of the information below to find the correct solution for your specific environment.Īrticle 841668 – A mail-enabled contact may receive a Winmail.dat file attachment with an SMTP e-mail message instead of receiving the correct file attachment in Exchange 2000 Server. However, if the e-mail systems do not support RTF, the attachment cannot be separated correctly from the body of the message.įor more information about Microsoft Exchange Server settings, we have included three Microsoft articles from the Microsoft Knowledge Base to assist you with this. Client e-mail systems can receive e-mail messages that have an attachment. The Microsoft Exchange Server settings may cause the attachment to be sent in RTF format. When I email a PDF, the file attachment appears incorrectly as Winmail.dat instead of in PDF format, or it is missing.

Dat to pdf converter