It provides the capability to specify search string encoding while searching for messages using ImapQueryBuilder and Sending DKIM signed email messages. Moreover, it also fixed issues related to TNEF messages conversion and display at receiver’s end, Message content encoding issues during message conversion to different formats, Limitation on adding more than 1020 inline images, message conversion to TIFF, loading certain EML files and adding messages to PST files.
Lane Cove, Australia, April 29, 2015 –(PR.com)– Aspose team is pleased to announce the new release of Aspose.Email for Java 5.2.0. This release allows signing messages with DKIM has been implemented in this month’s release. In addition, the API also provides the capability to specify search string encoding while searching for messages using ImapQueryBuilder. For a detailed list of API changes, please consider visiting Aspose documentation section, Public API changes in Aspose.Email for Java 5.2.0. This latest version of Aspose.Email for Java includes enhancements like Sending DKIM Signed Messages and Using Encoding in ImapQueryBuilder. With this month’s release, the API now provides the feature of signing email messages with DKIM (Domain Keys Identified Mail). The MailMessage class’s dKIMSign method provides the usage of this feature by using the private key file and DKIM signature Info. Once signed, the message can be sent using the API’s SMTP client. Aspose.Email provides the capability of listing messages from IMAP server mailbox, with the capability of applying criterion based searches using ImapQueryBuilder. This month’s release further enhances the functionality of searching messages by specifying search string encoding. This helps querying the mailbox for different search strings based on the specified encoding e.g. Turkish characters such as ğüşıöç. This month’s release also includes a number of bug fixes as part of either ported from its equivalent .NET version or reported actually with the Java version of the API. These include, a number of issues related to TNEF messages conversion and display at receiver’s end, message content encoding issues during message conversion to different formats, Limitation on adding more than 1020 inline images while adding message to PST and exceptions while message conversion to TIFF, loading certain EML files and adding messages to PST files. The main improved features & bug fixes added in this release are listed below.
· Add the DomainKeys Identified Mail (DKIM) signature to the email message headers
· 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-Java
· 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
· EML to MSG conversion raises NULL exception
· MapiMessage with more than 1020 inline images cannot be added to PST folder (Java)
· 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 ByteArrayOutputStream raises exception
· MSG to PST: Subject Encoding issue
Other most recent bug fixes are also included in this release
Newly added documentation pages and article
Some new tips and articles have now been added into Aspose.Email for Java documentation that may guide users briefly how to use Aspose.Email for performing different tasks like the followings.
– Sign Emails with DKIM: http://www.aspose.com/docs/display/emailjava/Sign+Emails+with+DKIM
– Filtering Messages from IMAP Mailbox: http://www.aspose.com/docs/display/emailjava/Filtering+Messages+from+IMAP+Mailbox
Overview: Aspose.Email for Java
Aspose.Email for Java is a Non-Graphical Java component that enables Java applications to read and write MS Outlook MSG files from within a Java application without using MS Outlook. It enables developers to create new MSG file from scratch, update an existing MSG file, read Outlook MSG file & get its properties like subject, body, recipients in to, cc and bcc, adding or removing attachment, sender information & MAPI properties. Aspose.Email can be used with Web as well as Desktop Application.
More about Aspose.Email for Java
– Homepage of Aspose.Email for Java: http://www.aspose.com/java/email-component.aspx
– Download Aspose.Email for Java: http://www.aspose.com/community/files/72/java-components/aspose.email-for-java/default.aspx
– Online documentation of Aspose.Email for Java: http://www.aspose.com/docs/display/emailjava/Home
– Demos of Aspose.Email for Java: http://www.aspose.com/demos/java-components/default.aspx
– Post your technical questions/queries to Aspose.Email for Java Forum:http://www.aspose.com/community/forums/aspose.email-product-family/499/showforum.aspx
– Receive notifications about latest news and supported features by subscribing to Aspose.Email for Java blog: http://www.aspose.com/blogs/aspose-products/aspose-email-product-family.html
Aspose Pty Ltd,
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066