Kashif Iqbal May 11, 20162 Comments

Binding SMTP Client to specific IP Address on Host supported with Aspose.Email for Java 6.5.0

Binding SMTP Client to specific IP Address on Host supported with Aspose.Email for Java 6.5.0

May 11, 2016
Share on FacebookTweet about this on TwitterShare on LinkedIn

Aspose.Email for Java 6.5.0 has been released. Ported from its  equivalent .NET version, this month’s release includes the same features, enhancements and bug fixes as were included in the .NET version of the API. Specifically, the API has been enhanced to bind SmtpClient to specific IP address and the functionality of working with events on secondary calendar folder of Office 365. For a complete list of public API changes, please visit the Release Notes article in Aspose.Email for Java documentation section.

Features & Enhancements

Using EWS Client to Work with Secondary Calendar Folder: This month’s release introduces a new feature of working with Secondary Calendar folder on Office 365 server. This enables you to:

  • Add a secondary Calendar folder to the server
  • Create calendar events
  • Update and Delete calendar events

For complete details about the API methods and sample code, please visit our documentation article, Working with Calendar Items on Secondary Calendar folders.

Binding SMTP Client to Specific IP Address: For a server having multiple interfaces for communicating with external world, it may sometimes be required to use a specific IP address for sending out emails. This month’s release of Aspose.Email for Java enhances the API’s SmtpClient to specify the IP address through which all the emails should be sent out.

SmtpClient client = new SmtpClient(
    client.bindIPEndPoint( new BindIPEndPointHandler() {
        public InetSocketAddress invoke(InetSocketAddress remoteEndPoint) {
            return new InetSocketAddress(0);
finally { if (client != null) ((IDisposable)client).dispose(); }

Adding Mail Header at Specific Location: This month’s release also enhances the functionality of adding headers to a message’s header collection. It now provides the capability of inserting the new header at a specific location. If collection contains headers with the same name, this header will be inserted before other headers with the same name.

Other Improvements

This month’s release also fixes a number of bugs that were reported with the last version of the API. As the version is auto-ported from the .NET version of the API, it also inherits all the fixes from the .NET version as well.

API Resources

We have detailed information available online for getting started with the Aspose.Email for Java API. These are:

Join the Conversation


Leave a comment

Posted inAspose.Email Product Family

Related Articles