Releases: Mailu/Mailu
2.0.13
Changelog 📫
- Update the documentation:
- debian Stretch -> debian stable (see #2826)
- docker 24.0.0 is broken (see #2827)
- document how to get rid of "mount: Deactivated successfully" messages from moby (see #2797)
-
This release was triggered by PR/Issue 2829.
-
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
Update
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.
2.0.12
Changelog 📫
-
Fix SCAN_MACROS: OLETOOLS wasn't always enabled/disabled like it should have been
-
This release was triggered by PR/Issue 2805.
-
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
Update
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.
2.0.11
Changelog 📫
-
Allow other supported languages in Roundcube's spellchecker
-
This release was triggered by PR/Issue 2798.
-
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
Update
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.
2.0.10
Changelog 📫
-
The SMTP container wasn't logging things like it should
The health-check of dovecot was creating zombies
Document that COMPRESSION=zstd is now possible (see #2139) -
This release was triggered by PR/Issue 2793.
-
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
Update
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.
2.0.9
Changelog 📫
-
In front, config.py can be called several times. LD_PRELOAD may have already been removed from ENV. This caused issues when letsencrypt was enabled on ARM systems.
-
This release was triggered by PR/Issue 2789.
-
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
Update
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.
2.0.8
Changelog 📫
-
Always exempt login attempts that use app-tokens from rate-limits
Ensure that unsuccessful login attempts against a valid account hit the ip-based rate-limit too -
This release was triggered by PR/Issue 2772.
-
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
Update
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.
2.0.7
Changelog 📫
-
Filter unwanted logs out.
Disable hardened-malloc if we detect a processor not supporting the AVX extension set -
This release was triggered by PR/Issue 2644.
-
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
Update
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.
2.0.6
Changelog 📫
-
Fix downloading attachments through snappymail.
-
This release was triggered by PR/Issue 2776.
-
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
Update
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.
2.0.5
Changelog 📫
-
Letsencrypt only works if port 80 is reachable. Users behind reverse-proxies don't read instructions... this makes the common misconfiguration work too.
-
This release was triggered by PR/Issue 2720.
-
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
Update
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.
2.0.4
Changelog 📫
-
Fix a bug preventing POP3 from being usable
-
This release was triggered by PR/Issue 2756.
-
The release notes of the original main release can be accessed via menu item 'Release notes' on mailu.io.
Update
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.