SSL Mode Auto Detection for Servers & Retaining Content Disposition Using Aspose.Email for Java 6.7.0
It includes SSL Mode Auto Detection for Servers. The SecurityOptions mode offered by the API included None, Auto, SSLImplicit and SSLExplicit options. It adds another option of SSLAuto to this Enumerator that avoids setting the security options to none while selecting between the two SSL options at the same time. The API now retains the content-transfer encoding strings while loading email & then saving it back. It also includes all the bug fixes as inherited from its equivalent .NET version.
Lane Cove, Australia, July 24, 2016 --(PR.com)-- What's New in this Release?
Aspose team is pleased to announce the new release of Aspose.Email for Java 6.7.0. This month’s release is sort of maintenance release with minor enhancements as well. Ported from its equivalent .NET version, it also includes the same bug fixes as were part of the .NET equivalent version. The API now retains the content-transfer encoding strings while loading an email and then saving it back. Provision of this feature makes it possible to keep meta0record data of emails intact while they are processed using the API. The SecurityOptions mode offered by the API included None, Auto, SSLImplicit and SSLExplicit options. This month’s release adds another option of SSLAuto to this Enumerator that avoids setting the security options to None while selecting between the two SSL options at the same time. This month’s release also includes all the bug fixes as inherited from its equivalent .NET version. This further adds to the overall stability of the API. The main improved features & bug fixes added in this release are listed below:
• Retain Content disposition and Content-Transfer-Encoding while saving and loading an Email
• Alternative for SecurityOptions.Auto, but without possibility of SecurityOptions.None
• IEWSClient: ExchangeQueryBuilder.To field returns empty results
• mapiConversionOption.setPreserveOriginalAddresses(true) is not working on setReplyTo()
• EML can't be converted to XPS
• SetBodyContent() breaks the special character €
• Properties disappear when message is fetched from Pst
• Body lost while converting EML to MSG
• ImapClient cannot rename folder to a name containing special characters like double quote (")
• Error While Fetching Emails Of Folder that contains double quotes(") in folder Name
• Creating Forwarded Message doesn't include To address and brackets for the email address
• Subject can't be read from EML
• Adding value to Header raises error
• VCF files created by Aspose.Email are corrupted and cannot be opened Thunder bird, Google Mail, Apple Address book
• FolderInfo.AddMessages raises ArgumentNullException sometimes
• Length cannot be less than zero exception while loading the attached VCS files
• Specified argument was out of the range of valid values exception raised while loading the VCS files
• Object reference not set to an instance of object exception raised while loading the VCS files
• Exception while saving MapiMessage after replacing the attachment-Java
• "Specified argument was out of the range of valid values." exception while converting MapiMessage to MailMessage using InterpretAsTnef
• Adding MapiRecipient raises "The Exchange Address is not in a recognized format" exception
• Invalid URI exception when adding email to PST
• Null Reference Exception when converting Calendar EML to MapiMessage
• Exception on Content-Transfer-Encoding: x-uuencode
• Exception "ArgumentOutOfRangeException: Cannot be negative" raised while converting EML to MapiMessage
• Exception "The address of recipient can't be null or empty" raised while converting EML to MapiMessage
• Value is not equivalent to either TrueString or FalseString while converting EML to MapiMessage
• Exception "Input string was not in the correct format" raised while converting EML to MapiMessage
• DateTime FormatException: Invalid format string while converting EML to MapiMessage
• ArgumentNullException: The address of recipient can't be null or empty
• Creating Forward Message raises ArgumentNullException
• Creating Forward Message from EML->MSG raises ArgumentNullException
• List Messages by Page raises exception
Other most recent bug fixes are also included in this release.
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/downloads/email-family/java
- Online documentation of Aspose.Email for Java: http://www.aspose.com/docs/display/emailjava/Home
Contact Information
Aspose Pty Ltd,
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
http://www.aspose.com/
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465
Aspose team is pleased to announce the new release of Aspose.Email for Java 6.7.0. This month’s release is sort of maintenance release with minor enhancements as well. Ported from its equivalent .NET version, it also includes the same bug fixes as were part of the .NET equivalent version. The API now retains the content-transfer encoding strings while loading an email and then saving it back. Provision of this feature makes it possible to keep meta0record data of emails intact while they are processed using the API. The SecurityOptions mode offered by the API included None, Auto, SSLImplicit and SSLExplicit options. This month’s release adds another option of SSLAuto to this Enumerator that avoids setting the security options to None while selecting between the two SSL options at the same time. This month’s release also includes all the bug fixes as inherited from its equivalent .NET version. This further adds to the overall stability of the API. The main improved features & bug fixes added in this release are listed below:
• Retain Content disposition and Content-Transfer-Encoding while saving and loading an Email
• Alternative for SecurityOptions.Auto, but without possibility of SecurityOptions.None
• IEWSClient: ExchangeQueryBuilder.To field returns empty results
• mapiConversionOption.setPreserveOriginalAddresses(true) is not working on setReplyTo()
• EML can't be converted to XPS
• SetBodyContent() breaks the special character €
• Properties disappear when message is fetched from Pst
• Body lost while converting EML to MSG
• ImapClient cannot rename folder to a name containing special characters like double quote (")
• Error While Fetching Emails Of Folder that contains double quotes(") in folder Name
• Creating Forwarded Message doesn't include To address and brackets for the email address
• Subject can't be read from EML
• Adding value to Header raises error
• VCF files created by Aspose.Email are corrupted and cannot be opened Thunder bird, Google Mail, Apple Address book
• FolderInfo.AddMessages raises ArgumentNullException sometimes
• Length cannot be less than zero exception while loading the attached VCS files
• Specified argument was out of the range of valid values exception raised while loading the VCS files
• Object reference not set to an instance of object exception raised while loading the VCS files
• Exception while saving MapiMessage after replacing the attachment-Java
• "Specified argument was out of the range of valid values." exception while converting MapiMessage to MailMessage using InterpretAsTnef
• Adding MapiRecipient raises "The Exchange Address is not in a recognized format" exception
• Invalid URI exception when adding email to PST
• Null Reference Exception when converting Calendar EML to MapiMessage
• Exception on Content-Transfer-Encoding: x-uuencode
• Exception "ArgumentOutOfRangeException: Cannot be negative" raised while converting EML to MapiMessage
• Exception "The address of recipient can't be null or empty" raised while converting EML to MapiMessage
• Value is not equivalent to either TrueString or FalseString while converting EML to MapiMessage
• Exception "Input string was not in the correct format" raised while converting EML to MapiMessage
• DateTime FormatException: Invalid format string while converting EML to MapiMessage
• ArgumentNullException: The address of recipient can't be null or empty
• Creating Forward Message raises ArgumentNullException
• Creating Forward Message from EML->MSG raises ArgumentNullException
• List Messages by Page raises exception
Other most recent bug fixes are also included in this release.
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/downloads/email-family/java
- Online documentation of Aspose.Email for Java: http://www.aspose.com/docs/display/emailjava/Home
Contact Information
Aspose Pty Ltd,
Suite 163, 79 Longueville Road
Lane Cove, NSW, 2066
Australia
http://www.aspose.com/
sales@aspose.com
Phone: 888.277.6734
Fax: 866.810.9465
Contact
Aspose
Sher Azam
888.277.6734
http://www.aspose.com/
Sher Azam
888.277.6734
http://www.aspose.com/
Contact
Categories