What's new in MailerQ 0.7?
We are pleased to announce the release of MailerQ 0.7.0. Over last 3 weeks our development team worked on some new features, improvements and bug fixes. Let's have a look at them.
Automatic DKIM signing.
The feature many of you waited for. You can now add a DKIM-signature to your emails automatically with MailerQ. The process is as simple as it can be. All you need is private/public keys pair, proper DNS record and opendkim library installed on your MailerQ server.
How to sign emails with MailerQ?
First you need to install OpenDKIM library on your MailerQ machine. This library is available in repositories of all supported Linux distributions.
Second step is to make sure you have a DKIM DNS record set up properly. It should look like:
selector_name._domainkey.example.com IN TXT "v=DKIM1; h=sha1; p=PUBLICKEY; t=s"
Now all you need to do is to add your private key to MailerQ using web interface. In page 'DKIM keys' click on the 'Add DKIM key' button and fill in domain name, selector and your private key.
That's it. From now on, MailerQ will automatically sign all emails sent from domain name for which you have added the key.
Note that for now MailerQ only supports SHA1 hashing algorithm. Support for SHA256 will be added in the future.
The "domain" JSON property has been removed. It no longer has to be included in the JSON object. MailerQ now filters it out from the recipient's email address. See updated examples.
The "retry" result type has been split up in the "idle", "reuse" and "reset" result types. See their description in result queue documentation.
Log can be filtered on 'failure' to list all possible failures. You can now simply view all failed deliveries in one click.
Log now contains entire recipient's email address, not only the domain name. This is usefull to, for example, remove non-existing email addresses from your database.
Failed deliveries that are going to be retried are marked with an asterisk (*) in the log.
Important bug fixes
Fixed possible segmentation fault when multiple emails were received over the same connection.
Instructions were sent too early to worker threads (when they were not yet initialized), which could result in initial instructions being missed.
Improved validatity checks for email addresses and domain names. Checks are more tolerant now.