Remotely cancel individual deliveries using new REST API endpoint in MailerQ 5.6.4

Last week, we released MailerQ version 5.6.4 which, after the introduction of our REST API in the previous version, now includes a new endpoint for setting, removing and getting forced errors. In case you don't know what a forced error is in MailerQ: with this functionality, you can fail individual deliveries including error code and description based on a combination of sending IP or IP Pool, target domain, and tags (many-to-many labels, used for identifying individual or organized deliveries such as "campaign_X", "customer_Y" or "transactional").

The forced error functionality in MailerQ is often used by MTA administrators and deliverability managers to cancel individual problematic deliveries (for a certain ISP) or deliveries that were accidentally sent out. Amongst other use-cases, the introduction of the new API endpoint can be really useful for the latter situation.

Some applications that allow users to send bulk mailings, such as some Email Service Providers, already provide a cancel button. However, this typically means cancelling the injection of the campaign into the MTA and does not affect the messages already queued for delivery.

Using the forced error API endpoint, you can enable your end-user to instruct all the MTAs across a cluster to permanently fail all messages matching specific conditions - in this case, each message containing the tag associated with the campaign they wish to cancel. And since this forced error information is available in the result objects and logs, you can easily keep track of which messages were cancelled as a result of this action, and which got through before the interception took place.

Do you want to learn more about this and other endpoints in our new REST API? Check out our documentation for details.