RTF Message Handling |
User's Manual Start Page |
| Firstly, if a disclaimer is added to an RTF message, it's always added at its end. This means it cannot be inserted directly after the text of a response in replies and forwards. | |
| Secondly, if you use RTF format for internal correspondence (sent between the users of a local Exchange organization), and it contains images, that graphics will not be visible to the recipients. | |
To minimize the inconveniences of the limited footer compatibility with RTF messages, we recommend you to make sure that RTF is not your default mail format in Outlook or in the OWA applications for users of your Exchange organization.
Converting RTF messages to the HTML format on the server
E-mails are sent outside the organization in the RTF format very rarely. If a user writes an RTF message in Outlook and sends it to an external address, Outlook will transform it to HTML by default (although the option may be disabled to prevent Outlook from converting the message format) and a disclaimer will be added to such a message.
If as an administrator you want to make sure that messages in RTF are never sent outside via Exchange Server, take the following steps:
| 1. | Run the Exchange Management Console program. |
| 2. | In the left panel go to Organization Configuration | Hub Transport. |
| 3. | In the right pane choose Remote Domains, then select the remote domain (the default remote domain applies to address space *), then right click and select Properties. |
| 4. | In properties window select Format of original message sent as attachment to journal report:tab (Yes, the tab is mislabeled! Actually it is the "Message Formats" tab). |
| 5. | Set the Exchange rich-text format option to Never use (See picture below) |
After configuring the Exchange server in this way, messages sent by users in RTF will be converted into HTML by the server.