Planning Your mailcow Upgrade Around the November 2026 Release
The mailcow project has dated its next release for November 5, 2026. The announcement labels it a feature and security update and names three items: mailbox groups, a rework of imapsync, and SOGo 5.12.13.
That is essentially all the announcement gives us. It does not describe how the new mailbox groups behave, what changed inside imapsync, or which security issues are addressed. So this piece is not about the specifics of the release — it is about how to approach it, because the three areas it touches are exactly the ones where a surprise costs you the most.
Who this affects
Every self-hosted mailcow operator, regardless of size. If you run mail for a family or a couple of domains, the upgrade is still worth a planned window. If you run it for clients or a team, the stakes are higher: mailbox organization, account migration and groupware are all day-to-day surfaces, not edge features.
Why it matters
Mail is unforgiving. A half-finished upgrade can mean deferred messages, clients that stop syncing or a calendar that silently goes quiet — and you usually find out from someone else. A release that combines feature work with security fixes is not one to apply casually on a Friday afternoon.
The imapsync rework deserves particular attention. Migrations are often the one moment when people touch accounts they otherwise leave alone, and any change there is worth understanding before a migration window rather than during one.
Commentary for self-hosters
A few habits that have served me well with mailcow over the years:
- Read the full release notes and any linked documentation before touching the server, not after something breaks.
- Snapshot the host or back up volumes and configuration first. A rollback path is cheaper than a rebuild.
- Check your own automation. If you have scripts that create mailboxes, manage accounts or drive migrations, review them against the notes before upgrading.
- Upgrade a staging or low-traffic instance first if you have one, then watch logs and mail flow for a day.
- Keep the upgrade on your schedule, not on the announcement's.
None of this requires knowing the details of the release in advance. It just requires treating a mail server like the critical piece of infrastructure it is.
If you want tooling that sits alongside mailcow and makes the administrative side less manual, our mailcow tools are built for exactly this kind of self-hosted setup.
Back up first, read the notes, and plan the window.