An extended feature comparison
For most MTAs, disk performance is a bottleneck. This does not account for MailerQ. With MailerQ messages never hit a disk, but are stored inside RAM. It relies on RabbitMQ and NoSQL storage for message queues and deferred messages. Disk operations, as used by PowerMTA, slow down the software. MailerQ is therefore much faster.
ISPs can limit the amount of email that is allowed through their network. Throttling can be used to control the amount of emails that ISPs can receive from a certain network. MailerQ offers more parameters to base your throttling settings on than PowerMTA does. Throttling settings are applied automatically to all aliases of a domain.
PowerMTA supports standard validation mechanisms such as SPF, DKIM and DMARC. MailerQ offers all the validation mechanisms that PowerMTA offers. However, MailerQ is the first MTA that also supports ARC. By doing this, a receiving service can also validate an email when SPF and DKIM records are rendered invalid (e.g. in the case of an intermediate service such as forwarding).
The setup of PowerMTA can be quite challenging. All settings have to be made by altering rather long and complex configuration files that are hard to maintain and difficult to update. Furthermore, PowerMTA has to be restarted after each time changes have been applied to this config file. MailerQ, on the other hand, offers a simple config file and reads most of its configuration from a relational database. This setup makes Mailerq easy to tune, both manually and programmatically. MailerQ instances pick up these configuration settings automatically by a adjustable time interval, so no restart or reload is needed.
Due to the use of the relational database it is also very easy to integrate MailerQ with your existing systems. While we cannot provide a fully automated conversion from your PowerMTA config file, we can assist you in translating your current configuration so it also works for MailerQ.
MailerQ offers a very slick, but powerful management console. Our management console allows you to monitor the performance of your email delivery in real-time. Compared to PowerMTA, the MailerQ management console can be used to change all settings in memory to maximize deliverability on the fly (e.g. reroute emails to other IP addresses or set up flood patterns to react to server responses). And if you have multiple instances of MailerQ running in a cluster, you can easily switch between them. All of this makes MailerQ really easy to maintain and update.Discover our Management Console
|Live SMTP traffic monitor|
|Live logfile monitor|
|Automatic recognition of domain groups|
|Pause and resume campaigns based on message tags|
* The PowerMTA management console is only available from version 4.5 with a separate license.
While MailerQ also provides central log files, the use of RabbitMQ and JSON enables users to get more detailed information about successful or unsuccessful mail deliveries. Log files are much more limited compared to the JSON result objects. For example, the result JSON also holds a chain of all delivery attempts so you can exactly see what happened to your mail before it got delivered or failed.MailerQ's management console also gives you direct access to its internal data structures and network traffic, so that you no longer need own tools to see exactly what your MTA is doing. We offer a live overview for both SMTP, logs and the rendered emails.
|JSON over AMQP|
|Command Line Interface|
|Message compression before sending|
|CSS stylesheet to attributes|
|JSON to MIME conversion|
|DKIM message signing|
|ARC message signing|
|DMARC report handling|
|Local address database|
|Support for clustering|
|Support for chaining|
|C/C++ plugin API|
|Domain MTA and IP based rates|
|Support for per-message overrides|
|SMTP reply pattern matching|
|Configurable deferral periods|
Supported SMTP extensions
We understand that your MTA is important for your business
and that it is not an easy decision to make.
However, if there ever was a time for a replacement, it is now. We have a better alternative.
MailerQ is fast due to its non-blocking architecture. Emails don't pile up just because there is one slow receiving server. MailerQ will use multiple threads to maximize your sending potential and make every bit of email sending process as smooth as possible.
Furthermore, MailerQ tries to skip the slowest part of your servers: the hard drive by using RabbitMQ queue for queuing emails. Since, RabbitMQ stores it's queues inside RAM memory (the fastest memory on your server) it serves emails lightning fast.
You can install MailerQ and send huge volumes without the need for big investments in hardware or disks. With our alternative solution you can shut down most of your old MTA machines because of MailerQ's better performance.
MailerQ is flexible. It uses message queues and JSON, giving you full control over your email flow. With this alternative you can monitor and intervene when necessary. Prioritizing and routing has never been easier.
MailerQ is competitive. It beats every MTA in performance and pricing, and it has all the features that you could find in alternative MTAs.