Bumps all six mailu services lockstep on one tag (mailu ships every service from the same version
code). redis (8.10.2-alpine) and ldez/traefik-certs-dumper (v2.11.4) are already current — unchanged.
service
image
current → new
app
ghcr.io/mailu/nginx
2024.06.61 → 2024.06.64
admin
ghcr.io/mailu/admin
2024.06.61 → 2024.06.64
imap
ghcr.io/mailu/dovecot
2024.06.61 → 2024.06.64
smtp
ghcr.io/mailu/postfix
2024.06.61 → 2024.06.64
antispam
ghcr.io/mailu/rspamd
2024.06.61 → 2024.06.64
webmail
ghcr.io/mailu/webmail
2024.06.61 → 2024.06.64
db
redis
8.10.2-alpine (unchanged)
certdumper
ldez/traefik-certs-dumper
v2.11.4 (unchanged)
Upstream changes (2024.06.61 → 2024.06.64)
2024.06.62 (2026-10-12): deal with the DNS KSK rollover, ensure it does not happen again.
2024.06.63 (2026-10-13): resolver healthcheck now fails on SERVFAIL from unbound instead of
reporting healthy while every lookup fails.
2024.06.64 (2026-10-15, latest): same resolver-healthcheck fix re-released.
No migrations, no breaking changes, no config/env/volume/label changes. Patch-level bug fixes only.
Deterministic advisory-scan.py mailu --from 2024.06.61 --to 2024.06.64 → 0 CVEs fixed by this
upgrade; union with release-note reading = 0. (Roundcube CVEs CVE-2026-54432/54433 were already
fixed at 2024.06.56; CVE-2026-62356 concerns redis, unchanged here.) Note the scan's GitHub-advisory
sources were rate-limited, so the count is a floor — release notes name no CVEs for .62–.64.
Operator Action Required
None. No config or migration changes.
Release command (operator, after merge)
abra recipe release mailu -z
The recipe version label is intentionally not bumped in this PR — the operator runs the release
command above (which bumps the label + tags + publishes) after the upstream PR merges.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
## mailu image upgrade: 2024.06.61 → 2024.06.64
Bumps all six mailu services lockstep on one tag (mailu ships every service from the same version
code). `redis` (8.10.2-alpine) and `ldez/traefik-certs-dumper` (v2.11.4) are already current — unchanged.
| service | image | current → new |
|---------|-------|---------------|
| app | ghcr.io/mailu/nginx | 2024.06.61 → 2024.06.64 |
| admin | ghcr.io/mailu/admin | 2024.06.61 → 2024.06.64 |
| imap | ghcr.io/mailu/dovecot | 2024.06.61 → 2024.06.64 |
| smtp | ghcr.io/mailu/postfix | 2024.06.61 → 2024.06.64 |
| antispam | ghcr.io/mailu/rspamd | 2024.06.61 → 2024.06.64 |
| webmail | ghcr.io/mailu/webmail | 2024.06.61 → 2024.06.64 |
| db | redis | 8.10.2-alpine (unchanged) |
| certdumper | ldez/traefik-certs-dumper | v2.11.4 (unchanged) |
### Upstream changes (2024.06.61 → 2024.06.64)
- **2024.06.62** (2026-10-12): deal with the DNS **KSK rollover**, ensure it does not happen again.
- **2024.06.63** (2026-10-13): resolver healthcheck now **fails on SERVFAIL** from unbound instead of
reporting healthy while every lookup fails.
- **2024.06.64** (2026-10-15, latest): same resolver-healthcheck fix re-released.
- No migrations, no breaking changes, no config/env/volume/label changes. Patch-level bug fixes only.
**Upstream release notes:** app/admin/imap/smtp/antispam/webmail (mailu) 2024.06.61→2024.06.64: https://github.com/Mailu/Mailu/releases/tag/2024.06.64
(and https://github.com/Mailu/Mailu/releases/tag/2024.06.63 , https://github.com/Mailu/Mailu/releases/tag/2024.06.62)
### Security / advisory scan
Deterministic `advisory-scan.py mailu --from 2024.06.61 --to 2024.06.64` → **0 CVEs fixed by this
upgrade**; union with release-note reading = 0. (Roundcube CVEs CVE-2026-54432/54433 were already
fixed at 2024.06.56; CVE-2026-62356 concerns redis, unchanged here.) Note the scan's GitHub-advisory
sources were rate-limited, so the count is a floor — release notes name no CVEs for .62–.64.
### Operator Action Required
None. No config or migration changes.
### Release command (operator, after merge)
```
abra recipe release mailu -z
```
The recipe version label is intentionally **not** bumped in this PR — the operator runs the release
command above (which bumps the label + tags + publishes) after the upstream PR merges.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
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.
mailu image upgrade: 2024.06.61 → 2024.06.64
Bumps all six mailu services lockstep on one tag (mailu ships every service from the same version
code).
redis(8.10.2-alpine) andldez/traefik-certs-dumper(v2.11.4) are already current — unchanged.Upstream changes (2024.06.61 → 2024.06.64)
reporting healthy while every lookup fails.
Upstream release notes: app/admin/imap/smtp/antispam/webmail (mailu) 2024.06.61→2024.06.64: https://github.com/Mailu/Mailu/releases/tag/2024.06.64
(and https://github.com/Mailu/Mailu/releases/tag/2024.06.63 , https://github.com/Mailu/Mailu/releases/tag/2024.06.62)
Security / advisory scan
Deterministic
advisory-scan.py mailu --from 2024.06.61 --to 2024.06.64→ 0 CVEs fixed by thisupgrade; union with release-note reading = 0. (Roundcube CVEs CVE-2026-54432/54433 were already
fixed at 2024.06.56; CVE-2026-62356 concerns redis, unchanged here.) Note the scan's GitHub-advisory
sources were rate-limited, so the count is a floor — release notes name no CVEs for .62–.64.
Operator Action Required
None. No config or migration changes.
Release command (operator, after merge)
The recipe version label is intentionally not bumped in this PR — the operator runs the release
command above (which bumps the label + tags + publishes) after the upstream PR merges.
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
mailu@69afb870✅ passedfull logs · dashboard
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.