mailu: the containers are named by the vocabulary 2024.06 reads #79

2026-09-25T21:56:35Z

jschoubben commented

2026-09-25 21:56:35 +00:00

Front resolves upstreams from *_ADDRESS (defaulting to bare compose service names) and reads the 1.9-era HOST_* not at all. Phase 1 never noticed because HAL's service names were the defaults; the mesh's containers are mailu-*, and front 502'd asking docker DNS for admin. Dead vocabulary removed; every upstream named as the container actually is.

Front resolves upstreams from `*_ADDRESS` (defaulting to bare compose service names) and reads the 1.9-era `HOST_*` not at all. Phase 1 never noticed because HAL's service names *were* the defaults; the mesh's containers are `mailu-*`, and front 502'd asking docker DNS for `admin`. Dead vocabulary removed; every upstream named as the container actually is.

jschoubben added 1 commit 2026-09-25 21:56:35 +00:00

mailu: the containers are named by the vocabulary 2024.06 reads 4e37b3e84d

The front resolves its upstreams from *_ADDRESS, defaulting to the bare
compose service names — admin, antispam — and reads the 1.9-era HOST_*
not at all. Phase 1 never noticed because the predecessor's service
names WERE the defaults; the mesh's containers are mailu-*, and the
front answered 502 asking docker for a name nothing carries. The dead
vocabulary goes; every upstream is named as the container actually is.

jschoubben merged commit b8a50ee7a0 into main

2026-09-25 21:56:41 +00:00

jschoubben deleted branch fix/mailu-speaks-2024-06-addresses

2026-09-25 21:56:41 +00:00

jschoubben referenced this issue from a commit

2026-09-26 13:04:34 +00:00

mailu: one WEBMAIL_ADDRESS, the mesh's container name

jschoubben referenced this pull request

2026-09-26 13:04:39 +00:00

mailu: one WEBMAIL_ADDRESS, the mesh's container name #93

Sign in to join this conversation.