Insular email distribution - mail server as Docker images
No longer advertize IMAP ID capability before authentication. This fixes issues with clients which send ID commands before authentication. One notable client with this issue is offlineimap.
This release was triggered by PR/Issue 2938-remove-id.
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.
This release was triggered by PR/Issue 2985.
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.
forbidden_file_extension.map could not be overridden. This file can be overriden to tweak with file extensions are allowed. The instructions on https://mailu.io/master/antispam.html#can-i-change-the-list-of-authorized-file-attachments work again.
This release was triggered by PR/Issue 2937.
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.
Update hardened malloc as the original package is not available from alpine anymore. The newer version of hardened malloc requires AVX2: Disable it by default at startup and hint in the logs when it should be enabled instead. Upgrade snappymail to v2.29.1
This release was triggered by PR/Issue 2959.
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.
Remove the version pinning on hardened malloc
This release was triggered by PR/Issue 2955.
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.
Remove the version pinning on hardened malloc
This release was triggered by PR/Issue 2955.
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 webmails: roundcube 1.6.3, rcmcarddav 5.1.0, snappymail 2.28.4
This release was triggered by PR/Issue 2945.
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.
fix fetchmail when used with POP3: disregard "folders"
This release was triggered by PR/Issue 2928.
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.
Switch the admin container from port 80 to port 8080. This should solve issues related to capabilities not working as expected Document that systemd-resolve may need to be configured to validate DNSSEC Ensure that dovecot is not attempting to bind a v6 socket if SUBNET6 is not configured
This release was triggered by PR/Issue 2906.
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 delete any pre-exising PID files Make Rspamd retry for longer when connecting to clamav
This release was triggered by PR/Issue 2917.
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.