Messages from Apple devices and mobile devices are sent in plain text
A message sent from an Apple device (iPhone, iPad, Mac, etc.) or a mobile device (e.g. based on Android) is sent in the plain text format. As a result, the signature added by CodeTwo software to this message does not look as expected (Fig. 1.) or is not added at all (if you have not configured the template for the plain text format). In some scenarios, messages previously converted to the HTML format are rolling back to the plain text format.
This problem is related to the default behavior in these devices:
- Most mobile devices use plain text as their default format. Often, there is no option to set the message format (plain text / RTF / HTML) before sending it.
- In the case of Apple Mail, when you reply, forward or compose new messages on a Mac, this mail client automatically uses the plain text or HTML format. Unfortunately, even if you set the default mail composition format to Rich Text in the application's preferences, it does not always work: creating a message without any text formatting results in Apple Mail using plain text regardless of the program's settings and the original message format. Such behavior has also been observed in earlier versions of Mac OS X.
The naming convention in Apple devices does not entirely meet the one used by Microsoft. While Microsoft refers to Rich Text as a separate document format (RTF), in the Apple Mail app Rich Text means HTML (Apple devices are not able to send messages directly in the Microsoft’s RTF format).
- If you use CodeTwo Exchange Rules Pro, you can use the Force email format action or force an email format directly on your Exchange Server;
- If you use CodeTwo Exchange Rules, you can force an email format directly on your Exchange Server;
- If you use CodeTwo Email Signatures for Office 365, you can force email format conversion on the Design tab of the signature management app, as explained in the user's manual;
- If you do not use the above applications and you are trying to fix this problem on a Mac, see this section.
To force an email format in CodeTwo Exchange Rules Pro version 2.x, you need to:
- Open the software's Administration Panel. In this scenario we will force all messages to be converted to the HTML format.
- Create a new rule or edit an existing one.
- Ensure that this rule is at the top of the rules list.
- If necessary, configure the rule's conditions and exceptions. If you skip this step, the rule will apply to all emails.
- On the Actions tab, add a new action and choose Force email format. Configure the action to convert messages to HTML. For more information, see the user's manual.
- Go to the Options tab and select Go to the next rule in both scenarios (both when the rule is and is not applied).
If you use version 1.x of CodeTwo Exchange Rules Pro, the steps are similar (see Fig. 2.).
Open the Exchange Management Shell, wait until the console connects to your server and execute the following command:
set-remotedomain -Identity Default -ContentType MimeHtml
Note that this cmdlet sets the HTML format as preferred on your Exchange. However, it will not cause automatic conversion of the plain text format to HTML. If you would like to allow a client-based choice or force plain text, see our Knowledge Base article.
- Open the Mail app on your Mac.
- On the top menu, click Mail and then Preferences.
- Switch to the Composing section (Fig. 3.).
- Set Message Format to Rich Text.
- Start composing a new message and apply some formatting at least once (it is enough to just bold some text).
- Send the message.
The message should be sent in HTML and stamped with the HTML version of your signature (assuming that the HTML signature template was correctly configured in your CodeTwo software).
|Related products:||CodeTwo Email Signatures for Office 365 1.x, CodeTwo Exchange Rules 2007 4.x, CodeTwo Exchange Rules 2010 3.x, CodeTwo Exchange Rules 2013 2.x, CodeTwo Exchange Rules 2016 1.x, CodeTwo Exchange Rules 2019 1.x, CodeTwo Exchange Rules Pro 1.x, 2.x|