Kashif Iqbal January 20, 20150 Comments

SMTP, POP3 and IMAP protocols now supported with Aspose.Email for Java 4.9.0

SMTP, POP3 and IMAP protocols now supported with Aspose.Email for Java 4.9.0

January 20, 2015
Share on FacebookTweet about this on TwitterShare on LinkedIn

We are really excited to share that Aspose.Email for Java now supports communication protocols. What this means is that you can now send and receive emails using the most common email protocols such as SMTP, POP3 and IMAP. This month’s release also brings other enhancements to the API functionality such as sending Tasks requests and removing MAPI Properties from messages and message attachments. For complete details about what is new and fixed, please visit the product download page.

New Features

Sending Email Messages with SMTP: With this month’s release, Aspose.Email for Java now supports sending email messages using the Simple Mail Transfer Protocol (SMTP). You can use the API for sending emails right from within your applications using the SMTP settings from popular email services such as Gmail, Yahoo, Hotmail or any other server. The SMTP client provides the following features:

Managing Email Messages with POP3: Aspose.Email for Java now supports Post Office Protcol (POP) v 3.0 for connecting and retrieving email messages from mail servers. The Pop3Client class provides the entire necessary interface for instantiating communication with mail servers for manipulating messages. The POP3 Client provides the following features for retrieving messages:

Managing Email Messages with IMAP: Internet Message Access Protocol (IMAP) allows clients to connect and manage email messages on the mail server. Aspsoe.Email for Java API now supports the IMAP communication protocol for connecting to mail servers and retrieving email messages. The IMAP client provides the following functionality for retrieving messages:

Bug Fixes

This month’s release includes a number of bug fixes that further improves the overall API functionality. These include:

  • Encoding issues while converting message to other formats
  • Loss of body contents and detection of attachments as inline items
  • Issues related to removal of MAPI properties from MSG as well as attachments
  • Exceptions while loading messages, listing messages and interpreting messages as TNEF

If you have any queries or inquiries related to the existing/new features of the API, please feel free to contact us over the Aspose.Email forum. We’ll be glad to assist you further.

Leave a comment

Posted inAspose.Email Product Family
 

Related Articles