We faced with issue when we fetched emails with empty BodyEncoding in case while such info existed in initial email.
Note, when you load emails from using MailMessage.Load(…) your email contains BodyEncoding info, unlike fetching messages from email server case. We use the latest 20.9.1 Aspose.Email.dll
I uploaded _ToAsposeForum.zip (115.5 KB)
which included SampleEmail.msg, Apose logs and screenshots from VisualStudio debugger.
So, in case of we load this email from email server we can see:
FetchFromServer.png (31.2 KB)
While we try to load from file we can see another picture:
LoadFromFile.png (32.6 KB)
Apose log file contains info about charset:
AsposeLogSnip.PNG (15.7 KB)
I have created an issue with ID EMAILNET-39951 in our issue tracking system to further investigate and resolve the issue. This thread has been linked with the issue so that you may be notified once the issue will be fixed.
Could you clarify if this fix will be included to the 20.10 patch?
Yes, it has been fixed in Aspose.Email for .NET 20.10 which has not been published.
The issues you have found earlier (filed as EMAILNET-39951) have been fixed in this update.