Thank you for considering Aspose.Email for .NET.
Can you please share your sample email message files with us for our reference? We will investigate these at our end for assisting you further. Also, please make sure that you are using the latest version of the API i.e. Aspose.Email for .NET 6.2.0 in your application.
I've discovered the cause of the problem. When saving the MSG file originally I was using SaveOptions.DefaultMsg instead of SaveOptions.DefaultMsgUnicode.
The resulting MSG file for both options contains proper Unicode characters, however when creating the MHTML file, they are all lost for the one that used SaveOptions.DefaultMsg.
Consider this problem resolved.
Thanks for responding so quickly.
Thank you for sharing your feedback.
Just for your information, in case the message is saved as DefaultMsg and loaded again for conversion to Mhtml, you can use the Message.PrefferredTextEncoding field to specify the encoding for conversion that will lead to correct result.
MailMessage msg = new MailMessage();
msg.IsBodyHtml = true;
msg.Body = “이것은 한국어 언어입니다.”;
msg = MailMessage.Load(“AEMsgKorean.msg”, new MsgLoadOptions());
msg.PreferredTextEncoding = Encoding.UTF8;