MailerQ is a high-performance on-premise Mail Transfer Agent built for sending and controlling large volumes of email. It is built with a strong focus on performance, ease-of-use, and insight. And as such is considered as an alternative to the conventional MTA tools.
Delivery control, data transparency, a REST API, plugin support and open-source components such as RabbitMQ and MySQL/PostgreSQL make MailerQ a fast and flexible solution.
MailerQ offers a free testing license or purchase a perpetual, unlimited license for lifetime usage.
Are you looking for an MailerQ alternative for your email marketing? We listed some MailerQ alternatives.
Products and services
As a Mail Transfer Agent (MTA) the MailerQ platform has the following features:
Define delivery rates using email throttling
Using Email throttling, you can specify the number of connections and delivery rates for specific combinations of source IP and target ISP.
Examples of capacities that can be set here are: messages per minute, new connections per minute, bytes per minute, the maximum number of active simultaneous connections, timeouts throughout the SMTP handshake and more. These rules will automatically apply to all target domains with matching MX records.
Identify messages using tags
Tags are many-to-many labels that you can attach to messages for identification, for example, to specify a customer, a campaign, whether it’s a transactional or bulk email, and so forth. These tags can be used to set up rules for a selection of ongoing deliveries or to organize results.
Adapt MTA behaviour based on server responses
Using Response Patterns, you can adapt MTA behaviour based on server responses. You can define a trigger, being a combination of a message selection based on IP, ISP and tag, and a server response pattern.
For every trigger, you can add suitable follow-up actions such as adding or removing IP addresses for the matching deliveries, fail or retry the delivery, adding or removing tags and changing other message properties. And with Flood Patterns, you can temporarily pause communication and then start sending again on a reduced capacity based on server responses (such as “temporarily rate limited due to IP reputation”).
Classify or reroute deliveries using rewrite rules
Rewrite rules can be used to dynamically reroute messages. To create a rewrite you need two things: a trigger and at least one action. A trigger is a combination of IP, target domain and a tag, that will say what kind of messages – such as a specific campaign that’s being delivered to a certain ISP – should trigger an action.
An action tells what MailerQ should do for matching messages – this can be adding, removing or setting an IP and/or a tag for a specific delivery, or redirecting a message to a smarthost.
Additionally, you can provide conditions, which means MailerQ will only apply the rule if for the selected message certain properties do or do not equal/contain/match specific values or patterns.
Extensive delivery rate limiting per IP/ISP
Organize deliveries per campaign, customer, delivery type, priority or anything else
Configure reroutes, modify message properties or adapted sending rates based on server responses
Set up message classification rules and apply actions such as rerouting or tagging
Intercept deliveries (pausing/failing), either manually or through the REST API
IP warm-up schedules
Management console for real-time insights and on-the-fly configuration across a cluster
Inject messages over SMTP, HTTP, AMQP, Spool Directory or CLI
Result objects including message properties and attempts chain per message stored in JSON format