Phase 1's lessons as pins: every image is the digest running and verified tonight — webmail under the name 2024.06 actually uses (the draft's roundcube pin misled a whole hop), antivirus on upstream clamav/clamav-debian with its DB in its own directory (the mailu-built image ended at 2.0), REAL_IP_FROM set to what the live config actually trusts, welcome texts for parity, and a data/clamav directory resource.
TLS_FLAVOR stays letsencrypt deliberately where live .env says cert: those cert files are copies whose HAL-era renewal hook died with HAL (they expire Nov 27); mailu managing its own issuance through the existing ACME passthrough is the fix, with the files on disk as the fallback flavor if first issuance misbehaves in the window.
Phase 1's lessons as pins: every image is the digest running and verified tonight — `webmail` under the name 2024.06 actually uses (the draft's `roundcube` pin misled a whole hop), antivirus on upstream `clamav/clamav-debian` with its DB in its own directory (the mailu-built image ended at 2.0), `REAL_IP_FROM` set to what the live config actually trusts, welcome texts for parity, and a `data/clamav` directory resource.
`TLS_FLAVOR` stays `letsencrypt` deliberately where live `.env` says `cert`: those cert files are copies whose HAL-era renewal hook died with HAL (they expire Nov 27); mailu managing its own issuance through the existing ACME passthrough is the fix, with the files on disk as the fallback flavor if first issuance misbehaves in the window.
Phase 1 (MAILU-CUTOVER.md) upgraded the live stack 1.9→2024.06 and its
lessons land here as pins: every image is the digest running and
verified tonight — webmail under the name 2024.06 actually uses (the
draft's roundcube pin misled a whole hop), antivirus on the upstream
clamav image with the signature DB in its own directory (the mailu-built
image ended at 2.0), and the front trusting the proxy address the live
config actually names. The welcome-mail texts ride along for parity.
TLS_FLAVOR stays letsencrypt deliberately where the live .env says cert:
the cert files are copies whose HAL-era renewal hook died with HAL
(expiry Nov 27); mailu managing its own issuance through the existing
ACME passthrough is the fix, and the files remain on disk as the
fallback flavor if first issuance misbehaves during the window.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Phase 1's lessons as pins: every image is the digest running and verified tonight —
webmailunder the name 2024.06 actually uses (the draft'sroundcubepin misled a whole hop), antivirus on upstreamclamav/clamav-debianwith its DB in its own directory (the mailu-built image ended at 2.0),REAL_IP_FROMset to what the live config actually trusts, welcome texts for parity, and adata/clamavdirectory resource.TLS_FLAVORstaysletsencryptdeliberately where live.envsayscert: those cert files are copies whose HAL-era renewal hook died with HAL (they expire Nov 27); mailu managing its own issuance through the existing ACME passthrough is the fix, with the files on disk as the fallback flavor if first issuance misbehaves in the window.