I am pleased to announce the much anticipated release of our new API for SocketLabs Email On-Demand. Email On-Demand is SocketLabs’ cloud based SMTP server platform. With a SocketLabs’ Email On-Demand account, users simply relay their email to our cloud based server and let us take care of the rest. SocketLabs actively manages all aspects of your email delivery including bounce processing, feedback loops, SPF, DomainKeys/DKIM, traffic shaping and more. Customers are given access to their account through our web based control panel, and the new API.

The new Email On-Demand API enables software developers and application integrators to pull real-time data from their cloud based account. It provides easy programmatic access to mailing data, from wide angle statistics right down to the individual message level.

If you tag your outbound messages with user defined data (in the headers) that information is also exposed through the Email On-Demand platform, including the API. This makes it incredibly easy for your application to get the status of and individual message or an entire campaign/mail blast. The API is based on REST making it completely platform independent. An SDK including the API documentation and sample code can be downloaded from http://www.socketlabs.com/download/od-api.zip.

To find out more about the SocketLabs Email On-Demand service, please visit: http://www.socketlabs.com/od.

Follow John Alessi on Twitter: @johnalessi

Automatic Suppression Lists

The latest production release of Hurricane MTA Server adds powerful automatic suppression lists that boost your deliverability and protect your reputation by automatically blocking repeat emails to invalid addresses and email addresses that have filed complaints against you. This incredibly intelligent and automatic feature is out of beta and currently in production.

See this article for more information.

More Powerful IP Based Authentication and Account Mapping

Now, any account can be selected and authenticated by the source IP address. Simply edit the IP whitelist and add the account id to the end of the IP address separated by a pipe.

For example if you wanted all email coming from 66.72.15.29 to go through account 1024, you would enter the following entry in the whitelist:

66.72.15.29|1024

Critical Alerts

System alerts are now broken out into two levels: critical and standard. Critical and standard alerts can be sent to different email address lists, making it easy to escalate critical issues.

The alert level of each Dynamic Block Rule can now be set to standard or critical.