github docker-mailserver/docker-mailserver v11.1.0

latest releases: v14.0.0, v13.3.1, v13.3.0...
2 years ago

In this release the relay-host support saw significant internal refactoring in preparation for a future breaking change. Similar extensive restructuring through the codebase also occurred, where each PR provides more details. Care was taken to avoid breakage, but there may be some risk affecting unsupported third-party customizations which our test suite is unaware of.

Features

Fixes

  • Using Port 465 to authenticate with a relay-host no longer breaks the Amavis transport for Postfix (#2607)
  • When mounting /var/mail-state, disabled services will no longer copy over data redundantly (#2608)
  • Amavis is now aware of new domains detected during Change Detection, no longer skipping virus and spam filtering (#2616)
  • setup.sh -c <container name> no longer ignores <container name> when more than 1 docker-mailserver container is running (#2622)

Improvements

  • The Change Detector service will now only process relevant changes (#2615), in addition to now monitoring postfix-sasl-password.cf, postfix-relaymap.cf, and postfix-regexp.cf (#2623)
  • For LDAP users that only need to support a single mail domain, setup config dkim should now detect the domain implicitly (#2620)
  • The container capability SYS_PTRACE is no longer necessary (#2624)
  • Added an example for configuring a basic container healthcheck command (#2625)
  • Postfix main.cf setting compatibility_level was set to 2 during our startup scripts. This is now part of our default shipped main.cf config (#2597)
  • The Postfix main.cf override/extension support via postfix-main.cf has been improved to support multi-line values, instead of the previous single-line only support (#2598)

Deprecation Notice

  • SASL_PASSWD ENV
    An old ENV SASL_PASSWD has been around for supporting relay-host authentication, but since superceded by the postfix-sasl-password.cf config file. It will be removed in a future major release as detailed here.

  • Platform Support - ARMv7
    This is a very old platform, superceded by ARMv8 and newer with broad product availability around 2016 onwards.
    Support was introduced primarily for users the older generations of Raspberry Pi. ARM64 is the modern target for ARM devices.

    If you require ARMv7 support, please let us know.

What's Changed (Generated)

New Contributors

Full Changelog: v11.0.0...v11.1.0

Don't miss a new docker-mailserver release

NewReleases is sending notifications on new releases.