MailerQ product update Q2 2022
The past few months we have implemented a new way of releasing and we have fixed some bugs. In this product update, we would like to inform you about the changes in our software.
Introducing the CI/CD pipeline and minor releases
We are changing the way we release MailerQ. Instead of a significant update a couple of times per year, we now implemented a CI/CD pipeline (Continuous Integration en Continuous Delivery) so we can release small changes and bug fixes more often. Read everything you need to know in our blog post.
After an experimental phase of two months, we have now passed the experimental phase, as it was described in the blog post.
Reducing support for CentOS
With the change in releasing, we are reducing support for CentOS. As CentOS is end of life per December 31st 2021, we decided to focus on Debian and Ubuntu only. If you are still running MailerQ on CentOS, we advise to migrate to Ubuntu 20.04.
Regarding Debian, the updates in the CI/CD pipeline will be supported for Debian 10 and onward.
RabbitMQ consumer timeout
We received reports of a crashing MailerQ due to a RabbitMQ timeout issue. It turns out that RabbitMQ introduced a default consumer timeout of 30 minutes. MailerQ however does not acknowledge all messages within this timeframe. We therefore recommend disabling this timeout. Read how to do this in our blog post.
Duplicate message ids
We received a report of a customer where duplicate message ids were generated. We introduced a fix that absolutely guarantees the integrity of the uniqueness of a message id.
Linking response patterns with actions
It was no longer possible to link actions to the correct trigger in the Response Patterns feature. Due to a bug, all actions were connected to the first trigger. This issue has been resolved in our newest release.
Smarthost on-message level
When setting a smarthost on-message level, this resulted in a relaying denied error, because the username was not properly passed. This issue was fixed in our newest release.