Some more info, I found in the github commit notes from a couple weeks ago it says sogo has not released a version for Debian 12 yet, so there's a condition in the install script to exclude it from the selection interface.  But there is Sogo 5.8.0-1 in the official Debian repository for 12/Bookworm, can we not just use that during the installer routine rather than the sogo deb repositories that the install script currently uses?

Two options if SOGo team doesn't build packages for new linux distro release:

1) Use the SOGo packages from yum/apt repositories offered by Linux vendor.

Pros:

- No need to wait for SOGo team to build binary packages.
- Receive regular updates from linux vendors. NOTE: the updates are usually security and minor bug fixes for same release (e.g. 5.8-0 -> 5.8-1 -> 5.8-2), not big version update (e.g. 5.8 -> 5.9 -> 5.10 -> 5.11).

Cons:

- No big version update. If you're running SOGo v5.8.0, and SOGo team releases new version v5.9.0, or even v6.0.0, usually you won't get such updates from yum/apt repos offered by Linux vendor.
- If you need some features available in new SOGo release, you have to figure out a way to smoothly switch to SOGo nightly build (built by SOGo team), it should be easy by simply backup config files and SQL databases, then uninstall packages and install them from SOGo repo, but sysadmin must handle it manually. i hope no junior sysadmin messes it up.

2) Wait for SOGo team to offer the binary packages for this new distro release.

Pros:

- Get new SOGo releases as soon as SOGo team builds the binary packages and publishes on its nightly repo. https://packages.sogo.nu/nightly/

Cons:

- SOGo nightly build packages may be unstable. This happened few times in one decade.
- SOGo team may take a long time to build packages for this new distro release, especially after acquired by Alinto. History:

+ took 4 months for CentOS Stream / Rocky / Alma 9 after requested (by me): https://bugs.sogo.nu/view.php?id=5697
+ 7 months for Ubuntu 22.04 after requested (by me): https://bugs.sogo.nu/view.php?id=5511
+ 2 months for Debian 11 after requested (by me): https://bugs.sogo.nu/view.php?id=5380
+ 1 month for Ubuntu 18.04 after requested (by me): https://bugs.sogo.nu/view.php?id=4459
+ 8 months for CentOS 8 after requested (by me): https://bugs.sogo.nu/view.php?id=4829
+ 9 DAYS for Ubuntu 20.04 after requested (by me): https://bugs.sogo.nu/view.php?id=5015
+ 2 months for Debian 10  after requested (by me): https://bugs.sogo.nu/view.php?id=4775

So, which option do you prefer?

While Ubuntu 22.04 was released, we chose option #2 and waited for 7 months to enable SOGo in iRedMail.

SOGo now supports Debian 12: https://bugs.sogo.nu/view.php?id=5787

any idea when the released installer will have support for SOGo? Or does it already?

Do you mean clone the iRedMail github repo and install from there?

Or do you mean I can install SOGo manually by downloading the nightly dev version?  If so, I think I'd rather just wait until SOGo is officially part of the iRedMail installer for Debian 12.  Any idea when that might be?

Now that it looks like iRedMail, iRedAdmin-Pro, and SoGo (dev) are all supported on Debian 12, I'm about to try an upgrade from Debian 11. Before I do, two questions:

1. Does any iRedMail/iRedAdmin-Pro upgrade require any changes from the standard Debian upgrade guide?

2. Current Debian 11 system runs both Roundcube and SoGo. I don't think I need both.

To remove Roundcube, I think all I need to do is delete the directory under /opt/www and change any Nginx links to point to the SoGo login page. Are any other steps needed?

Thanks!