# Official MIAB Upgrade path in near future

**URL:** <https://discourse.mailinabox.email/t/official-miab-upgrade-path-in-near-future/17123>\
**Category:** uncategorized\
**Created:** [November 2, 2026, 10:06pm UTC](https://discourse.mailinabox.email/t/official-miab-upgrade-path-in-near-future/17123 "2026-11-02T22:06:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![urs.riggenbach](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/u/eb9ed0/32.png) [@urs.riggenbach](https://discourse.mailinabox.email/u/urs.riggenbach)\
**Post date:** [November 2, 2026, 10:06pm UTC](https://discourse.mailinabox.email/t/official-miab-upgrade-path-in-near-future/17123/1 "2026-11-02T22:06:58Z")

</div>

Hello @JoshData and collaborators,

The LTS Ubuntu version 22.04 coming to end-of-life in a couple of months.

I wanted to ask if MIAB will officially support a new Ubuntu LTS version in the near future.

I am asking because I see a lot of vibe coded forks that are announcing upgrades are possible, but none of these are official.

And: Great job over the years, always loved MIAB for putting the word idempotent in my vocabulary. \<3

Kind regards,  
Urs

---

<div class="post-metadata">

**Author:** ![david.blythe](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/david.blythe/32/3143_2.png) [@david.blythe](https://discourse.mailinabox.email/u/david.blythe)\
**Post date:** [November 3, 2026, 12:56am UTC](https://discourse.mailinabox.email/t/official-miab-upgrade-path-in-near-future/17123/2 "2026-11-03T00:56:56Z")

</div>

We have a few options:

> <https://github.com/mail-in-a-box/mailinabox/pull/2603>
>
> I've worked extensively this past week to comb through the codebase, to accompli…sh the following:
> 
> \- Ubuntu 26.04 Support
> \- Nextcloud 34 Support (with proper upgrade stepping)
> \- PHP 8.5
> \- Dovecot 2.4.5
> \- Spamassassin / Dovecot migration to IMAPSieve
> \- Roundcube 1.7.5
> \- zpush 2.7.7
> \- Various fixes
> 
> PRs resolved:
> https://github.com/mail-in-a-box/mailinabox/pull/2600
> https://github.com/mail-in-a-box/mailinabox/pull/2599
> https://github.com/mail-in-a-box/mailinabox/pull/2575
> https://github.com/mail-in-a-box/mailinabox/pull/2571
> https://github.com/mail-in-a-box/mailinabox/pull/2537
> https://github.com/mail-in-a-box/mailinabox/pull/2485
> Potentially:
> https://github.com/mail-in-a-box/mailinabox/pull/2319
> https://github.com/mail-in-a-box/mailinabox/pull/2309
> (these depend on the approach that is accepted, to upgrade Nextcloud)
> 
> changelog:
> 
> update: bump PHP\_VER to PHP 8.5
> update: bump OS to Ubuntu 26.04
> update: migration to newer PPA for php versioning
> update: adjusted when curl gets installed
> update: bump Nextcloud to 34.0.3
> update: bump Nextcloud contacts App to 8.8.0
> update: bump Nextcloud calendar App to 6.5.4
> update: bump Nextcloud user\_external App to 4.0.0
> update: added Nextcloud upgrade blocks to step from 27.1.11 --\> 34.0.3
> fix: added Nextcloud SHA1 hashes for each upgrade block
> fix: resolved Python VENV issue by installing OS-available packages
> fix: removed ntp package, as 26.04 uses Chrony for time
> fix: resolved pollinate issue, pollinate now runs with 'pollinate' user
> fix: adjusted file for 'max\_user\_instances'
> fix: migrated to updated dovecot variable 'auth\_allow\_cleartext'
> fix: migrated to new dovecot 2.4.x syntax
> fix: migrated to new dovecot 2.4.x ssl syntax
> fix: removed tls variable that is already default
> update: bump dh key length to 4096 bits
> update: switched to dovecot configuration files, instead of python edits
> update: switched to imapsieve
> update: migrated to required modern sieve syntax
> update: switched to recommended pop3 uidl format
> fix: adjusted user auth syntax
> fix: switched to updated spamassassin path
> fix: switched to updated spampd path
> fix: time reference for z-push
> update: updated roundcube to 1.7.4
> update: updated carddav to 5.1.3
> fix: adjusted enable for mailinabox.service
> fix: adjusted enable for munin.service
> fix: adjusted nginx-top
> update: added PHP\_LEGACY\_VER variable for Nextcloud upgrade blocks
> fix: adjusted nginx config for roundcube webmail
> fix: adjusted nginx config for proper auth pass
> fix: bumped owncloud-restore php-fpm service to 8.5
> fix: bumped backup.py php-fpm service to 8.5
> fix: adjusted 'default\_client\_limit' to proper limit
> fix: updated http2 syntax to proper syntax
> fix: syntax error in apt-get purge
> fix: migrated to non-deprecated code in ssl\_management script
> 
> NOTE: Extensive testing is still required. I myself don't use every feature.
> 
> Disclaimer: No AI was used to develop commits made by me

This is explicitly ported without the use of AI. There are other PRs which take different approaches, namely, @KiekerJan’s, which we could also use.

At the moment, we are waiting on @JoshData to review these PRs and make a decision on the direction he wants to take.

---

<div class="post-metadata">

**Author:** ![KiekerJan](https://discourse.mailinabox.email/user_avatar/discourse.mailinabox.email/kiekerjan/32/2339_2.png) [@KiekerJan](https://discourse.mailinabox.email/u/KiekerJan)\
**Post date:** [November 3, 2026, 9:46am UTC](https://discourse.mailinabox.email/t/official-miab-upgrade-path-in-near-future/17123/3 "2026-11-03T09:46:14Z")

</div>

> [@david.blythe](#):
>
> There are other PRs which take different approaches, namely, @KiekerJan’s, which we could also use.

Thanks for the mention, but I don’t feel I’ve earned it. Just came here to say that I did not post PRs that are for a 26.04 migration. The ones I have are aimed at php and nextcloud updates.

---

<div class="post-metadata">

**Author:** ![FixFaier](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/f/fbc32d/32.png) [@FixFaier](https://discourse.mailinabox.email/u/FixFaier)\
**Post date:** [November 3, 2026, 4:55pm UTC](https://discourse.mailinabox.email/t/official-miab-upgrade-path-in-near-future/17123/4 "2026-11-03T16:55:20Z")

</div>

Hey @urs.riggenbach, if you want to upgrade directly, you can use our fork.  
We’ve spent weeks and days testing it and should be well prepared for all upgrade scenarios

> **[GitHub - LM1337/Mail-in-a-box-26: Unofficial Mail-in-a-Box fork for Ubuntu 26.04:...](https://github.com/LM1337/Mail-in-a-box-26)**
>
> Unofficial Mail-in-a-Box fork for Ubuntu 26.04: current packages (PHP 8.5, Nextcloud 34, Dovecot 2.4, Roundcube 1.7), full-text search, adaptive fail2ban, in-place upgrade and migration tools

---

<div class="post-metadata">

**Author:** ![hirehestand6873](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/h/ee59a6/32.png) [@hirehestand6873](https://discourse.mailinabox.email/u/hirehestand6873)\
**Post date:** [November 17, 2026, 11:08am UTC](https://discourse.mailinabox.email/t/official-miab-upgrade-path-in-near-future/17123/5 "2026-11-17T11:08:03Z")

</div>

No official statement yet—the PRs mentioned are community efforts, not merged. Until maintainers respond or merge a migration PR, the official upgrade path remains undefined. If you need to move off 22.04 soon, watch the GitHub PR status and release notes; testing a fork is an option but carries risk.
