Back to overview
What is new in MailerQ 4.3.1?
Published on March 17, 2017 | By MailerQ
We have released MailerQ version 4.3.1. This is a mainly a bugfix release that solves a number of issues that came to the light in version 4.3.0.
- Fixed a possible crash when a message was submitted to a message-specific DSN queue
- Fixed a possible crash when a message could not be found in the external nosql storage
- Fixed directory lookups on XFS filesystems (the management console did not correctly display the available log files)
- Fixed setting of empty attributes in authentication-results headers (empty parameters are not permitted, but MailerQ did set them)
- Messages with a wrong "ips" properties were not reported in the charts on the management console
- The ARC signatures of incoming messages can be verified and the result can be added to the "authentication-results" message header and inside the JSON (this can be enabled in the log file)
- If using directory based storage (instead of nosql storage), MailerQ now runs a garbage collector thread to remove files that are expired
- The "content" property of a responsive document may now also contain personalization code
- MailerQ now opens multiple sockets for incoming messages, and handles the TCP accept() call in the dedicated SMTP threads (and no longer in the main thread). This prevents that incoming mail gets slow if MailerQ main thread is busy.
- The algorithm to publish data to RabbitMQ has been improved (message are no longer copied around)