|0||Do not use HTML-to-RTF conversion. The resulting .MSG will not contain Rich-Text-Format part. Outlook will show HTML part (if available) or plain-text part.|
|1||Internal converter is used for HTML-to-RTF conversion. It provides only basic level of transformation so most advanced HTML formatting may be lost in the resulting RTF. Not supported in .NET Core and UWP.|
|2||Use the application-supplied OnHtmlToRtfConversion callback function to perform HTML-to-RTF conversion. You can also use this method when you need to create RTF body even for .EML which does not have HTML body part. The callback will be called for any .EML source, regardless if it actually has HTML part or not.|
.MSG files may have up to 3 alternative versions of the text body: plain-text, HTML, RTF (Rich-Text-format). By default, RTF body is displayed if present. However, .EML messages do not have RTF body. If, for some reason, you need to generate .MSG file with RTF body (HTML in .MSG is not enough for your purpose), the conversion between HTML and RTF must be performed. Such conversion is very complex because HTML and RTF formats are very different and both have very sophisticated formatting mechanisms, so it's not practically possible to match all the features of one format with another. MailBee provides only basic level of such conversions. If you, however, have a tool which is capable of making a better HTML-to-RTF conversion, you can use it with MailBee.
You can specify any of the values defined by HtmlToRtfMethod property.type through
OnHtmlToRtfConversion property allows you to specify the handler for performing custom HTML-to-RTF conversions.