Aspose.Email for .NET 5.3.0 has been released. This month’s release includes new features, enhancements and bug fixes that contribute more towards the value of the product. These features are related to various functional areas of the API including Outlook properties of a message, Exchange client, and Microsoft Outlook tasks and messages encryption. We have published the complete details of API changes in our documentation article Public API Changes in Aspose.Email for .NET 5.3.0 for reference.
Syncing Exchange Server Folder Items
With this month’s release of Aspose.Email for .NET, you can now sync Exchange server items for changes incurred to an Exchange folder. This is done by calling the SyncFolder method of the API’s IEWSClient and specifying the respective folder. This helps detect the changes such as new message arrival, changed message items, deleted items and changes in message read status. For a sample code, you may refer to our documentation article, Syncing Folder Items on Exchange Server.
Support for Email Tracking
This month’s release also includes a new feature of email tracking using Message Disposition Notification (MDN) support. This is achieved by requesting the read receipts and creating the required information. The MailMessage class’s ReadReceiptTo property gets or sets the set read receipt address. The CreateReadReceipt and ReadReceiptRequested methods are used for creating and retrieving the information whether read receipts are requested. We have illustrated the usage of this feature with the help of sample code that can be consulted for getting an idea.
Detecting Message for Encryption: This month’s release of Aspose.Email has further enhanced the MailMessage class with inclusion of IsEncrypted property. The property can be used to check a received/load message file for encryption. This is different to the already available IsSigned property that shows if message is signed. Our online documentation article, Message Encryption and Decryption, demonstrates the usage of this property with the help of sample code.
Support for additional MultiValue Property: Aspose.Email API already supports adding multi value Mapi properties to a message’s store. We have added the support for MV_LONG property in this month’s release which allows adding this property using both NamedProperty and Custom property message store. Please refer to our documentation article, Setting Mapi Properties for working sample code.
Setting Notes format for Contact: This month’s release has further enhanced setting the format of Outlook Contact notes. The Aspose.Email.Mail.Contact.NotesFormat property can be used to get the notes format. The possible values of this are represented by the Aspose.Email.TextFormat enumerator that can also be used to select a specific format for setting purpose.
We have also fixed a number of bugs related to various areas of API functionality. These include issues related to:
- Encoding issues during message conversion to other formats
- Missing information during messages conversion to MHTML
- Wrong message body type detection by MailMessage
- Loss of linked resource images when sending email using the API
- Exceptions such as using the IEWSClient of API with Mono framework, conversion to messages to MailMessage, loading certain email message files, and malformed address compilation
If you have any query related to the API, you can share your feedback with us on Aspose.Email forum for further assistance.