Issue saving the message after converting in 17.12.0

Aspose.Email Product Family
1

we have updated our application to Aspose 17.12.0, some unit test have failed. After investigation we have found the reason.
The reason is that when we have a Clear Signed Message, Or Encrypted Message, or Opaque Signed Message and we convert this message to EML using

message.ToMailMessage(new MailConversionOptions()
{
ConvertAsTnef = false

        });

Then, we try to save this message after converting (Original Message not Mime Message) using this code message.Save(@“c:\test\AfetrConvertingToMime.msg”, SaveOptions.DefaultMsgUnicode)

We couldn’t open this message in outlook and it becomes corrupted. Please note that this test was working smoothly in previous versions.

Code:
asposeLicense.SetLicense(new MemoryStream(Resources.Aspose_Email));

        var message = MapiMessage.FromStream(new MemoryStream(Resources.Signed_Opaque_Only));

        var convertedToMime = message.ToMailMessage(new MailConversionOptions()
        {
            ConvertAsTnef = false
            
        });


        message.Save(@"c:\test\enc.msg", SaveOptions.DefaultMsgUnicode);

Sample Messages.zip (38.4 KB)

2

@bahakh,

Could you also please share which earlier version of the API works fine at your end? We need the information to report this as regression in that case.

3

It was working on 17.5.0 and maybe other versions, but this is what we have tests running on.

4

@bahakh,

We were able to reproduce the issue at our end and have logged it as EMAILNET-38894 for further investigation by our Product team. We’ll update you here once there is further information or a fix version available in this regard.

5

Hi Kashif,

should we expect a fix in the next release ? If so, when will it be ?

6

@bahakh,

i am afraid to share that this issue is not resolved as it is logged to recently and still in queue for analysis by the product team. As there are many high priority tasks in the queue, so it may take time to analyze the resolve this issue. You will be automatically notified once any update is received in this regard.

7

@bahakh,

This issue has been fixed in the latest version of Aspose.Email for .NET 18.1.