Migrating your legacy Hermes install to Docker now works end to end.

Hermes SEG v260722 is out, and the headline is one many of you have asked for: if you have been running the legacy bare-metal Ubuntu build, the path onto the Docker edition is now hardened and tested against real backups.

What that means

• Safe cutover by default. A migrated box comes up with outbound delivery held, so stale quarantine notifications can't blast out to real recipients. You verify the box, then release mail when you are ready.
• Your setup comes across. Domains, mailboxes, and quarantine are restored, SPF/DKIM/DMARC keep working, and mail flows after the restore.
• Tested against real backups. We ran the migration end to end against actual legacy backups and fixed every failure it turned up.

You can move an existing Hermes deployment onto the modern, reproducible Docker stack without losing your setup, with a built-in safety hold so nothing embarrassing goes out during the switch.

One prerequisite: stand up a fresh Hermes SEG Docker install first, then run the migration to restore your legacy backup into it. The step-by-step Post-Migration Checklist: Legacy to Docker walks you through releasing delivery and verifying the box afterward.

Also in v260722

• Pause / Resume Outbound Delivery on the Mail Queue page, for maintenance windows, upstream outages, or investigating a suspected compromise. The hold survives later config saves instead of being quietly undone.
• Fixes: DKIM key generation on fresh installs, Postfix re-injection restored to the production design, and path-independent tooling. For existing Docker installs it is a low-impact update with no manual step.

Read the full write-up  |  Post-migration checklist  |  Release notes on GitHub

One honest note: the Docker line is still an early-adopter track. The migration path is tested against real backups, but every legacy install differs, so migrate a copy first and confirm mail flow before cutting over production.

Thanks for running Hermes,
The Hermes SEG team