Message bodies can be in text format and HTML format. Microsoft Exchange also supports RTF, which ELOxc does not support due to its age and support issues with EWS. Processing the message body in this form is therefore not recommended. Message stubbing is in fact not possible with this format.

If you want ELOxc to change or process message bodies, you have to make sure to use the correct format in some actions. For example, if you want to stub part of the message, the body format is important.

Microsoft Outlook (and any other e-mail client) will display a formatted message, not the source text of the format. If you want ELOxc to replace "Hi! Here is" with "This is" to get the result "This is my message", you have to pay attention to the body format because it significantly influences the search pattern.

If your message is in text format, you can search for "Hi! Here is" using a regular expression. However, if the message is in HTML format, you must consider that ELOxc needs to process the source text instead of the displayed text:

<p class=MsoNormal>Hi!<o:p></o:p></p><p class=MsoNormal>Here is<o:p></o:p></p>

This is why it is important that you create the configuration in line with the format of the message body, if you want to change it. You need to read out the property "PidTagNativeBody". If the property value is 1, the message is in text format. If the value is 3, the message is is HTML format, and if the value is 2, it uses RTF. If this property is not read out and, for example, the "Match/Replace" action is used, this could destroy the message format, making it impossible to display the affected messages either partially or completely.