Recently, reaslized realized that when we updated to Aspose 17.10 we had one test failing. The problem is that If we have a message with Message Format to ASCII and trying to save it as Unicode. It becomes corrupted. Please note this behavior was not happening in previous versions. It was working smoothly without any bugs or problems such as Aspose.Email 17.5
I have tried to re-produce the scenario using following sample code however issue is not reproduced using latest library Aspose.Email for ,NET 17,11.
var nonUnicodeMapiMessage = MapiMessage.FromFile(@“AsciMessageFormat.msg”);
nonUnicodeMapiMessage.Save(@“notWorkedMessage.msg”, Aspose.Email.SaveOptions.DefaultMsgUnicode);
If issue is still there with the latest version, please send us the ascii stream saved in a file for our testing as using the MSG file does not re-produce the issue.
I apologize I forgot to mention explicitly that the error appear when you try to open the message in outlook after you run the sample code. See attachment:
This issue is observed and logged under Id:EMAILNET-38876 for further investigation by the product team. You will be automatically notified once any update is received in this regard.
The issue has been logged too recently and is pending for investigation by our Product team. If you want to escalate the severity of issue, you can raise a ticket in paid support section. Please let us know if we can be of any additional help to you in this regard.
Thank you for writing to Aspose support team again.
We are glad to share that this issue is resolved and will be part of our next release expected in the mid of January 2018. You will be automatically notified once this new version is released and available online for download.