Mailu Files

Changelog :mailbox:

• Fix three boolean settings that could not be turned off. Each reached a jinja template through os.environ, where every value is a string -- and "False" is a non-empty string, which jinja reads as true. DEFER_ON_TLS_ERROR=False left smtp_tls_dane_insecure_mx_policy at dane and strict_testing at true in the postfix container; ADMIN=false, which is what the setup wizard writes when the admin interface is disabled, still gave the webmail a Mailu button and a support link pointing at the admin UI that nginx does not route; and FULL_TEXT_SEARCH_ATTACHMENTS=False still configured dovecot's tika decoder. The admin container read all of these correctly, so a deployment that turned one off got inconsistent behaviour between containers. Also fix a NameError that replaced the error message for an unusable PROXY_PROTOCOL entry, such as a list written with spaces after the commas, with a traceback at container start.

• This release was triggered by PR/Issue 4103.

• 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.