
We are pleased to announce the release of Aspose.Email for .NET 16.11.0. This month’s release includes enhancements where the API functionality is improved by enriching the existing features of the API. It also improves the overall API functionality by fixing several bugs. For a complete list of what is new and fixed, please visit our documentation section for release notes of this version.
Enhancements
Conversion of MSG to EML without using Interpreter classes: Aspose.Email API uses Interpreter classes for conversion of Microsoft Outlook (MSG) files to Multipurpose Internet Mail Extensions (MIME) messages. This month’s release enhances and simplifies this functionality using the MapiMessage class with its toMailMessage method. This also provides the capability to specify additional saving options using the MailConversionOptions class.
MapiMessage msg = new MapiMessage(
"sender@test.com",
"recipient1@test.com; recipient2@test.com",
"Test Subject",
"This is a body of message.");
var options = new MailConversionOptions();
options.ConvertAsTnef = true;
MailMessage mail = msg.ToMailMessage(options);
MemoryStream ms = new MemoryStream();
msg.Save(ms, SaveOptions.DefaultHtml);
string fileName = "savedMessage.eml";
msg.Save(fileName , SaveOptions.DefaultEml);
Provision of the BCC field in Exchange Message Summary Information: This month’s release also modifies the ExchangeMessageInfo summary object by incorporating the BCC field as property in it. This helps retrieve the information in case messages are listed from Drafts or Sent Items folder.
Other Improvements
This month’s release also fixes several bugs reported with our previous version that further adds stability to the API functionality.
API Resources
The following API resources can be of help to you in getting started with Aspose.Email API.
- Product Documentation – Provides detailed examples of working with the API
- API Reference Guide – Details all the namespaces and classes of the API
- GitHub Examples – Provides ready to run API example
- Support Forum – Write to us if you have any query or inquiry about the API