Getting Differen body in different Aspose version

Aspose.Email Product Family
1

Old Aspose Version: 23.2.0.0
New Aspose Version: 24.5.0.0

Sample Code:

_msg = MapiMessage.Load("File Path");
string bodyString = string.Empty;
try
{
    IMapiMessageItem baseProperty = _msg.ToMapiMessageItem();
    if (baseProperty != null)
        bodyString = baseProperty.Body;
}
catch (Exception ex)
{ }
if (string.IsNullOrEmpty(bodyString))
{
    try
    {
        MailConversionOptions option = new MailConversionOptions();

        bodyString = _msg.ToMailMessage(option).Body;
    }
    catch (Exception ex)
    { }
}
else if (string.IsNullOrEmpty(bodyString))
{
    bodyString = _msg.Body;
}

Let us know if you require any more information.

2

@hemalp

It seems you are experiencing differences in the body content when using different versions of Aspose, specifically between versions 23.2.0.0 and 24.5.0.0. This issue has been noted in the past, particularly regarding the handling of HTML bodies when converting between MapiMessage and MailMessage.

To address this, you might want to consider using the ForcedRtfBodyForAppointment option. This option can help maintain the HTML body unchanged for appointment EMLs. Here’s how you can implement it in your code:

MapiConversionOptions mco = MapiConversionOptions.getUnicodeFormat();
mco.setForcedRtfBodyForAppointment(false); // Set this option to false
MapiMessage mapiMessage = MapiMessage.fromMailMessage(mailMessage, mco);

By setting ForcedRtfBodyForAppointment to false, you can ensure that the HTML body remains consistent across different versions of Aspose.

If you continue to face issues, it may be beneficial to check the release notes or issue tracking for any known bugs related to body content changes between these versions.

Feel free to reach out if you need further assistance or clarification!

Sources:
[1]: HTML Body different when open with MapiMessage vs MailMessage
[2]: HTML Body different when open with MapiMessage vs MailMessage

3

Can you suggest any method same like provide code

4

Hello @hemalp,

Could you please share the original MSG file? This will help us investigate your issue.

Thank you.