MailerQ 2.1 release
MailerQ version 2.1 comes with a completely updated and more powerful plugin API, and a couple of other (relatively small) changes and improvements. We recommend all users to upgrade to this new version. But be careful: if you use the MailerQ plugin API, you may have to update your current plugins before you can upgrade.
Plugins for incoming emails
This MailerQ plugin API allows you to extend MailerQ by creating your own plugins. With the 2.1 release we have extended the available plugin functionalities. We added plugin support for authentication and it is now possible to store custom properties on the context and connections from plugins. If you want your plugin to interact with incoming SMTP traffic, you can implement several functions to do so. You can find out more on the plugin documentation page.
Plugins for outgoing emails
If you want your plugin to interact with outgoing SMTP traffic, you can implement the mq_smtp_out_data() function to do so. If your plugin contains this function, it will be called as soon as the SMTP connection enters the data state, giving you the chance to manipulate the message body before it is sent. Please note that this feature was already available before version 2.0, but that the name of the function has changed - you must therefore update existing plugins if you upgrade to MailerQ version 2.1!
Throttling failed authentication attempts in MailerQ
MailerQ now uses a small delay before reporting SMTP authentication failures. This means that every failed attempt takes a few seconds, which makes it harder to crack passwords by 'brute force'.
License file and CLI
MailerQ 2.1 can now be used in CLI mode on all your servers, even on servers that do not have one of the IP addresses assigned to them for which you purchased the MailerQ license. As a result, you can now use the CLI interface of MailerQ to inject emails in the RabbitMQ message queues on all your servers, even on servers for which you have no MailerQ license. To run MailerQ in daemon mode (which is the mode in which MailerQ delivers emails) you still need to start MailerQ on a server with an IP address for which you have a license.
What's new in the 2.* branche?
The most important change in version 2.1 is the extended plug-in functionality of MailerQ. If you upgrade to 2.1 from an earlier 1.* MailerQ version, you might be interested in the cool new features that we added in the 2.0 version, like the integrated Responsive Email algorithm, SMTP authentication and the changes that you must make to your config file. For more information about this, please read our article about the introduction of Mailer 2.0.
