Insular email distribution - mail server as Docker images
When "Enable marking spam mails as read" was disabled, new spam messages were still marked as read. Updated documentation with the setting "Enable marking spam mails as read".
This release was triggered by PR/Issue 3068.
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images `docker compose pull && docker compose up -d`.
The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.
Ensure we always send ISRG_X1 root when LE is configured. Switch to the non-crossigned version as the other one will expire in September
This release was triggered by PR/Issue 3187.
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images `docker compose pull && docker compose up -d`.
The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.
Add a semicolum to DMARC records
This release was triggered by PR/Issue 3150.
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images `docker compose pull && docker compose up -d`.
The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.
Add required quotes to traefik-certdumper to ensure that shell characters are usable.
This release was triggered by PR/Issue 3129.
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images `docker compose pull && docker compose up -d`.
The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.
Long term fix against SMTP smuggling (disable bare_newline), see https://www.postfix.org/smtp-smuggling.html
This release was triggered by PR/Issue 3101.
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images `docker compose pull && docker compose up -d`.
The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.
Prevent SMTP smuggling; see https://www.mail-archive.com/[email protected]/msg100901.html
This release was triggered by PR/Issue 3101.
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images `docker compose pull && docker compose up -d`.
The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.
Setup: Regular expression for checking the Mailu storage path was invalid. Added checks to make sure JavaScript is enabled and that all JS files could be loaded. The setup site malfunctions if this is not the case. Added server side validation of entered values in setup. Simplified setup by removing the settings for configuring the WEB_* settings. Advanced users can still modify mailu.env.
This release was triggered by PR/Issue 2890.
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images `docker compose pull && docker compose up -d`.
The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.
Ensure that we do not silently discard PUAs flagged by clamav. Instead we will reject emails.
This release was triggered by PR/Issue 3048.
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images `docker compose pull && docker compose up -d`.
The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.
Upgrade to roundcube 1.6.5 (fix XSS)
This release was triggered by PR/Issue 3041.
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images `docker compose pull && docker compose up -d`.
The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.
"Host or domain name not found. Name service error for name=outlook-com.olc.protection.outlook.com type=AAAA: Host found but no data record of requested type"
Update clamav to address a vulnerability in clamav.
This release was triggered by PR/issue #3011
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
The main version X.Y (e.g. 1.9) will always reflect the latest version of the branch. To update your Mailu installation simply pull the latest images `docker compose pull && docker compose up -d`.
The pinned version X.Y.Z (e.g. 1.9.1) is not updated. It is pinned to the commit that was used for creating this release. You can use a pinned version to make sure your Mailu installation is not suddenly updated when recreating containers. The pinned version allows the user to manually update. It also allows to go back to a previous pinned version.