With the release of version 5.8, weâre introducing several improvements including two new powerful features: Suppression List and support for external MTA IPs.
Introducing Suppression List and External MTA IPs in MailerQ 5.8.0
Global Sender Summit in review
On the 7th of November, email industry professionals from around the world gathered in Amsterdam for the inaugural edition of the Global Sender Summit, a one day conference with the most serious and educated email senders to share their knowledge and experience with their industry colleagues.
BIMI: a new way to combat email fraud and to increase brand recognition
The latest news in the land of email fraud: "A new real estate email scam has cybercriminals cashing in. Losses have soared [...] to $1.3 billion last year." - (CBS Evening News, September 25 2019). Unfortunately, these types of messages are not uncommon. In fact, as time goes on and more of our data gets stored online, phishing and email attacks are only increasing - with drastic consequences. It is more important than ever for senders to put the right email authentication in place to minimize these attacks. The newest addition in email authentication is created to help with this: BIMI (Brand Indicators for Message Identification). As other methods for email authentication, BIMI does not only prove the legitimacy of the sender but also helps to improve deliverability. In this blog post, we'll take a closer look at what it is and how it works.
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").
Introducing REST API in MailerQ 5.6.3
We rolled out an initial version of our REST API in which we introduce two endpoints for injecting messages and pausing/unpausing ongoing deliveries.