What's New in this Release?
We are pleased to announce the release of Aspose.Email for .NET
3.0.0. 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. This
month’s release 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. 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. 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. 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. 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 etc. The main bug fixes & improved features added in this release are listed below
- Message Disposition Notifications (MDN) support
- Synchronizing Exchange folders
- Create Assignable Task using Aspose.Email for .NET
- Provide support for MapiPropertyType.PT_MV_LONG
- NDR from Exchange server with "content conversion error" for message with Outlook item from Drafts folder
- Pop3Client: The server returned an invalid response to the TOP command.
- MSG to MHTML: Footer signature is not included in output
- Message body truncated while extracting from PST
- PersonalStorage: FolderInfo.HasSubFolders returns FALSE
- IEWSClient.UpdateContact changes Contact Notes to HTML
- MSG to Mhtml places headers at wrong position in the body
- MailMessage.BodyType returns wrong body type
- Tab character in body replaced by 8 spaces while converting MSG to EML
- Images added as Linked Resource are lost using Aspose.Email 5.2.0
- MailMessage.Load never returns
Other most recent bug fixes are also included in this release.
Overview:Aspose.Email for .NET
Aspose.Email for .NET is a set of .net email components allowing developers to easily implement email functionality within their ASP.NET web
applications, web services & Windows applications. It Supports Outlook PST, EML, MSG & MHT formats. It allows developers to work with SMTP, POP3, FTP
& MS Exchange servers. It supports mail merge, iCalendar, customized header & body, header information, embedded files, Twitter & many more. It
makes it easy to work with HTML or plain text emails & their attachments.
- Homepage of Aspose.Email for .NET C#
- Download Aspose.Email for .NET
No comments:
Post a Comment