New REST API endpoints introduced in MailerQ 5.8.5

Today, we released MailerQ version 5.8.5. This version, besides various improvements, introduces three brand new endpoints for the REST API. These new endpoints will further aid automation, integration with third-party platforms as well as work towards headless deployment.

Besides injecting messages and pausing/unpausing and failing certain deliveries, with the latest version you can now also control the following options through the REST API:

Manage IP Pools

In MailerQ, you can organize IP addresses in IP Pools. These pools can contain IP addresses shared between multiple customers, IPs dedicated to individual senders or IPs destined for certain purposes such as transactional or bulk traffic only.

With one of the newly introduced endpoints, you can now create or remove IP Pools. Additionally, you can assign IP addresses to certain pools, or remove them. Because IPs are automatically reloaded on-the-fly, you will not need to restart the MTA when new IPs are made available on your machine.

This new endpoint may prove particularly useful for automating the onboarding of new customers, be it on shared or on dedicated IP Pools. Additionally, it may help automate infrastructure expansion.

Add or remove destinations on the global Suppression List

We recently discussed the importance of globally suppressing bad traffic using one of our latest features, the Suppression List. With the introduction of a REST API endpoint for this, you can now add or remove destination domains and addresses to be suppressed from external authorized platforms. If you use certain tools or scripts to identify bad destinations, you can now use this endpoint to automatically add those to MailerQ’s Suppression List.

Configure External MTA IPs

Using the newly introduced External MTA IPs functionality, you can set up NAT rules to translate local IP and port combinations to external public IP addresses. This feature can be used to send emails using your own IPs that are on a different server. Specifically for deployments in cloud environments such as Amazon Web Services or Google Cloud Platform, this allows you to use all of your own IP addresses while still leveraging the advantages cloud has to offer. Using the new REST API endpoint for this functionality, you can now configure these NAT rules remotely, for example when scaling up your infrastructure.

For the full list of changes and updates in this release, please refer to the release notes.