MailerQ 5.14.4

We have released version 5.14.4 of MailerQ. In this release, we have fixed multiple bugs.

HTTP(S) servers can now be used as storage backend

To reduce the load on RabbitMQ, MailerQ can use external storage platforms like MongoDB or Couchbase to store and retrieve message bodies. It is now also possible to let MailerQ connect to a HTTP(S) server for storing and retrieving message bodies via REST calls. This allows users to build their own message store (or even generate messages on the fly).

Download proxy can now dynamically resolve domain names

MailerQ can be configured to use a HTTP proxy for downloading resources from the internet. Previously, if you would configure this setting using a domain name, it would only resolve at application startup. Now, MailerQ resolves this domain name dynamically at runtime. This is especially useful for hostnames with short TTL's that regularly change their IP address.

Responsive message can now be text-only

In previous versions of MailerQ, specifying a message in RabbitMQ using the responsiveemail.com format, would always generate an HTML body, even if only plaintext was provided; this would result in an empty HTML document. Now, if you only specify a plaintext message, MailerQ will only send a plaintext e-mail, without generating an empty HTML body.

MX Patterns now get deleted when its group gets deleted

We fixed a bug, where MX patterns would not get deleted from the database when you delete an MX pattern group. This meant that you were not able to use that same MX pattern again, since there is a unique constraint on this database field. In this version, when deleting an MX pattern group, its child MX patterns also get deleted.

DKIM and ARC signatures now always include List-Unsubscribe-Post header

The List-Unsubscribe-Post header is now always included in the DKIM signature. This is compliant with the specification in RFC 8058.