maathimself/mailflow v3.4.3

on GitHub

MailFlow v3.4.3

A single fix for a login-breaking regression introduced in 3.4.0.

Fixes

• Logging in works again on Podman, Kubernetes and other non-Docker networks (#448): 3.4.0 changed the frontend's nginx to re-resolve the backend at runtime, so that recreating the backend container no longer left the proxy pointing at a dead address. That upstream hardcoded resolver 127.0.0.11, which is Docker's embedded DNS and exists only on a user-defined Docker network. Elsewhere every DNS query was refused, so every /api/ request returned 502: login failed, and on a clean install the register link disappeared because it is API-driven. The resolver is now read from the container's own /etc/resolv.conf, which is correct on every runtime. The re-resolve behavior from 3.4.0 is unchanged.

  Installs using the shipped docker-compose.yml were never affected, because it puts every service on a user-defined network where that address does exist.

Upgrading

Pull the new images and recreate. No configuration change, no migrations. If you had pinned the frontend to 3.3.x to work around this, you can move back to the current tag.