b]What is new in this release? [/b]
We are pleased to announce the release of Aspose.Email for .NET 5.2.0 . With this month?s release, you can now send DKIM signed emails. We have also provided the facility to fetch message size from Exchange server before the whole message is fetched. This month?s release provides the feature of signing email messages with DKIM (Domain Keys Identified Mail) that enables organizations to take responsibility for the message that is in transit. A digital signature is added to the email message headers using the user defined private keys. The API?s MailMessage class provides the method DKIMSign that uses the Crypto Service Provider and DKIM Signature Info for signing the message. Once signed, the message can be sent using the API?s SMTP as well as Exchange Clients. Outlook InterOp provides the feature of retrieving message size before actually fetching the complete message from the Exchange server. In case of Aspose.Email API, the summary information retrieved from Exchange server is represented by ExchangeMessageInfo class and represents the only information that is fetched before actually retrieving the whole message. This month?s release enhances the functionality provided by this class to fetch message size as well before the complete message is fetched from the server. This information is represented by the Size property of the class. We have also enhanced the ImapQueryBuilder for specifying search string encoding while listing messages from IMAP server. This helps querying the strings that are, for example, in Unicode format and were not supported earlier. An example is Turkish characters such as ğ?şı??. This month?s release also fixes a number of bugs that were discovered by our valued customers while working with our API. We have fixed them all, resulting in improved API functionality. Some of these include issues related to TNEF messages sending via SMTP and Exchange clients, Encoding issues while converting messages to other formats, issues related to PST during exporting messages, exceptions while listing messages from IMAP client, loading certain message files and converting messages to TIFF and Exchange Server. The main bug fixes, new & improved features added in this release are listed below
- Add the DomainKeys Identified Mail (DKIM) signature to the email message headers
- EWS: Can there be any way of retreiving Message size before actually fetching it?
- Check oauth support for SMTP and IMAP clients for Yahoo and Yandex mail servers. Make TokenProvider as server-independent class if possible.
- Refactoring properties Body and TextBody of MailMessage.
- Provision of flag to avoid validity check while adding header values to HeaderCollection
- Behavior of connectin gto Exchagne Server on nonsecure port (143) and negotiate secure connection
- MSG created from TNEF attachment doesn't open in Outlook
- MailMessage.Subjec loses the ending "space"
- DOCx->MHTML->MSG->Send using Outlook: Line Breaks are no more respected
- Changing the embedded message name of TNEF formatted EML does not take effect
- System.NullReferenceException raised while conversion of EML to MSG
- IEWSClient: Appending InterpretAsTNEFDraft message includes Winmail.dat in message attachments
- MapiMessage with more than 1020 inline images cannot be added to PST folder
- IEWSClient: InterpretAsTnef changes message class when appended to Inbox
- Message printing: problem with russian charset
- Mail subject is corrupted after load and save it as EML
- MailMessage.Load converts embedded inline image to attachment.
- MailMessage.Save as HTML to MemoryStream closes the stream
- MSG to PST: Subject Encoding issue
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.
- Pre-Fetch Message Size
- Sign Emails with DKIM
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
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.2.0 . With this month?s release, you can now send DKIM signed emails. We have also provided the facility to fetch message size from Exchange server before the whole message is fetched. This month?s release provides the feature of signing email messages with DKIM (Domain Keys Identified Mail) that enables organizations to take responsibility for the message that is in transit. A digital signature is added to the email message headers using the user defined private keys. The API?s MailMessage class provides the method DKIMSign that uses the Crypto Service Provider and DKIM Signature Info for signing the message. Once signed, the message can be sent using the API?s SMTP as well as Exchange Clients. Outlook InterOp provides the feature of retrieving message size before actually fetching the complete message from the Exchange server. In case of Aspose.Email API, the summary information retrieved from Exchange server is represented by ExchangeMessageInfo class and represents the only information that is fetched before actually retrieving the whole message. This month?s release enhances the functionality provided by this class to fetch message size as well before the complete message is fetched from the server. This information is represented by the Size property of the class. We have also enhanced the ImapQueryBuilder for specifying search string encoding while listing messages from IMAP server. This helps querying the strings that are, for example, in Unicode format and were not supported earlier. An example is Turkish characters such as ğ?şı??. This month?s release also fixes a number of bugs that were discovered by our valued customers while working with our API. We have fixed them all, resulting in improved API functionality. Some of these include issues related to TNEF messages sending via SMTP and Exchange clients, Encoding issues while converting messages to other formats, issues related to PST during exporting messages, exceptions while listing messages from IMAP client, loading certain message files and converting messages to TIFF and Exchange Server. The main bug fixes, new & improved features added in this release are listed below
- Add the DomainKeys Identified Mail (DKIM) signature to the email message headers
- EWS: Can there be any way of retreiving Message size before actually fetching it?
- Check oauth support for SMTP and IMAP clients for Yahoo and Yandex mail servers. Make TokenProvider as server-independent class if possible.
- Refactoring properties Body and TextBody of MailMessage.
- Provision of flag to avoid validity check while adding header values to HeaderCollection
- Behavior of connectin gto Exchagne Server on nonsecure port (143) and negotiate secure connection
- MSG created from TNEF attachment doesn't open in Outlook
- MailMessage.Subjec loses the ending "space"
- DOCx->MHTML->MSG->Send using Outlook: Line Breaks are no more respected
- Changing the embedded message name of TNEF formatted EML does not take effect
- System.NullReferenceException raised while conversion of EML to MSG
- IEWSClient: Appending InterpretAsTNEFDraft message includes Winmail.dat in message attachments
- MapiMessage with more than 1020 inline images cannot be added to PST folder
- IEWSClient: InterpretAsTnef changes message class when appended to Inbox
- Message printing: problem with russian charset
- Mail subject is corrupted after load and save it as EML
- MailMessage.Load converts embedded inline image to attachment.
- MailMessage.Save as HTML to MemoryStream closes the stream
- MSG to PST: Subject Encoding issue
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.
- Pre-Fetch Message Size
- Sign Emails with DKIM
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
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
