What is new in this release?
We are pleased to announce the release of Aspose.Email for .NET 5.1.0 . There might be cases where message body is not correct due to any reason. In such cases, certain characters may not be returned properly while accessing the message body such as hyphens converted to ???. When this is the case, getting the HTML contained information from message?s HTML body is helpful. This month?s release provides an enhancement where this information can be obtained in plain text format from the message?s Html body using the HtmlBodyText property. Message headers contain encoded information that is almost useless in majority of the cases as these are accompanied by coded characters. If users want to get the decoded value of the header, requested to use the latest version of Aspose.Email for .NET to achieve this. It is often possible that email address of a message may contain invalid characters such as a backslash (\) character. Microsoft Exchange provides Exchange service address format that is one example of such address. In addition, it might be required to preserve such an email address while adding them to a Personal Storage (PST) file. Thus, it required the API to accommodate such invalid/malformed headers where necessary. In order to cater for this requirement, the MapiConversionOptions class now introduces a new property, named PreserveOriginalAddresses. If set to true, the address fields allow setting email addresses such as ?a\xasadf@xam.com?. As can be seen from the product release notes, the API includes further improvements by fixing a number of functionality bugs and exceptions. These include issues related to Exchange Web Service when creating voting buttons, loss of Notes information while fetch and save Outlook Contacts, and missing information while resolving contacts from Exchange server as well as Problems with message subject, message formatting and dynamic tags during mail merge and Issues related to PST such as message sender name visibility in PST preview pane, corrupted meeting body and reminder value, invalid Task body and exceptions while extracting messages. Other exceptions related to message conversion, parsing message headers and loading certain EML files are als part of this release. The main bug fixes, new & improved features added in this release are listed below
- OAuth support for SMTP and IMAP clients for Outlook.com
- Option to save original email address with invalid characters in MapiMessage
- Encoded header "Thread-Topic" not visible properly
- Take value of Body from PR_HTML if Body Property is disturbed
- Sender Name not shown in PST
- IEWSClient: Voting buttons not present in downloaded MSG
- MailMessage.Subject returns wrong Subject
- Message body garbled while loading from Mhtml and sending through Outlook
- Task body corrupted after adding it to PST
- Meeting body corrupted after adding to PST
- Appointment body and reminder values corrupted after adding to PST
- IEWSClient: Contact.Save loses Notes Information
- ExchangeQueryBuilder not working for SentDate.On
- IEWSClient: Appending InterpretAsTNEF messages include Winmail.dat in message attachments
- The MimeBasePart.DecodeHeaderValue method not working properly
- EWS: Client.ResolveContact doesn't fetches complete information
- Saved message formatting corrupted after sending it
- Dynamic Tag not working in template MSG file
Other most recent bug fixes are also included in this release.
Newly added documentation pages and articles
Some new tips and articles have now been added into Aspose.Email for .NET documentation that may guide you briefly how to use Aspose.Email for performing different tasks like the followings.
- Setting Default Text Encoding in Email Message
- Parsing Microsoft Outlook Message Files
Overview: Aspose.Email for .NET
Aspose.Email for .NET is a set of 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, POP, 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.
More about Aspose.Email for .NET
- Homepage of Aspose.Email for .NET C#
- Download Aspose.Email for .NET
- Online documentation of Aspose.Email for .NET
- Demos of Aspose.Email for .NET
Contact Information
Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465
We are pleased to announce the release of Aspose.Email for .NET 5.1.0 . There might be cases where message body is not correct due to any reason. In such cases, certain characters may not be returned properly while accessing the message body such as hyphens converted to ???. When this is the case, getting the HTML contained information from message?s HTML body is helpful. This month?s release provides an enhancement where this information can be obtained in plain text format from the message?s Html body using the HtmlBodyText property. Message headers contain encoded information that is almost useless in majority of the cases as these are accompanied by coded characters. If users want to get the decoded value of the header, requested to use the latest version of Aspose.Email for .NET to achieve this. It is often possible that email address of a message may contain invalid characters such as a backslash (\) character. Microsoft Exchange provides Exchange service address format that is one example of such address. In addition, it might be required to preserve such an email address while adding them to a Personal Storage (PST) file. Thus, it required the API to accommodate such invalid/malformed headers where necessary. In order to cater for this requirement, the MapiConversionOptions class now introduces a new property, named PreserveOriginalAddresses. If set to true, the address fields allow setting email addresses such as ?a\xasadf@xam.com?. As can be seen from the product release notes, the API includes further improvements by fixing a number of functionality bugs and exceptions. These include issues related to Exchange Web Service when creating voting buttons, loss of Notes information while fetch and save Outlook Contacts, and missing information while resolving contacts from Exchange server as well as Problems with message subject, message formatting and dynamic tags during mail merge and Issues related to PST such as message sender name visibility in PST preview pane, corrupted meeting body and reminder value, invalid Task body and exceptions while extracting messages. Other exceptions related to message conversion, parsing message headers and loading certain EML files are als part of this release. The main bug fixes, new & improved features added in this release are listed below
- OAuth support for SMTP and IMAP clients for Outlook.com
- Option to save original email address with invalid characters in MapiMessage
- Encoded header "Thread-Topic" not visible properly
- Take value of Body from PR_HTML if Body Property is disturbed
- Sender Name not shown in PST
- IEWSClient: Voting buttons not present in downloaded MSG
- MailMessage.Subject returns wrong Subject
- Message body garbled while loading from Mhtml and sending through Outlook
- Task body corrupted after adding it to PST
- Meeting body corrupted after adding to PST
- Appointment body and reminder values corrupted after adding to PST
- IEWSClient: Contact.Save loses Notes Information
- ExchangeQueryBuilder not working for SentDate.On
- IEWSClient: Appending InterpretAsTNEF messages include Winmail.dat in message attachments
- The MimeBasePart.DecodeHeaderValue method not working properly
- EWS: Client.ResolveContact doesn't fetches complete information
- Saved message formatting corrupted after sending it
- Dynamic Tag not working in template MSG file
Other most recent bug fixes are also included in this release.
Newly added documentation pages and articles
Some new tips and articles have now been added into Aspose.Email for .NET documentation that may guide you briefly how to use Aspose.Email for performing different tasks like the followings.
- Setting Default Text Encoding in Email Message
- Parsing Microsoft Outlook Message Files
Overview: Aspose.Email for .NET
Aspose.Email for .NET is a set of 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, POP, 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.
More about Aspose.Email for .NET
- Homepage of Aspose.Email for .NET C#
- Download Aspose.Email for .NET
- Online documentation of Aspose.Email for .NET
- Demos of Aspose.Email for .NET
Contact Information
Aspose Pty Ltd
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
Aspose - Your File Format Experts
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465
