mailcow
Support for SOGo 6
Summary
The upgrade to SOGo 6 will require a lot of Mailcow changes:
https://www.sogo.nu/news/2025/sogo-v6-septembre.html
Motivation
Highlights from the above URL:
- SOGo 5 was using AngularJS and Objective-c. SOGo 6 now uses Python for its backend and Reactsjs for its frontend.
- The backend uses Flask and will serve a RESTful API.
- SOGo 6 still is a caldav/cardav server.
- For performance and troubleshooting reasons, support for ActiveSync will be removed and replaced by another Microsoft protocol: MAPI over http
- SOGo 6 embarks a new process called Agent. It runs a tasks queues, using Celery and Redis, the new cache system. This agent will allow new features and tasks planification like : scheduling the sending of a mail or having a few seconds to cancel a sending.
- A brand new configuration system. Instead of a long sogo.conf file, SOGo 6 now has a proper admin interface to configure it.
- Multi-domains management has been reviewed to make it easy.
- The cache server Memcached is replaced by Redis
- SOGo’s database - for calendar, address books, user’s preferences… - has changed with SOGo 6. Table’s has been completely redone and PostgreSQL is required. Scripts to move data from your old database to your new database will be provided
- SOGo’s configuration has completely been redone. Only a few core parameters needs to be in ENV or a file. All the others one are stored in the database and are accessible through a brand new Admin interface. Except those core parameters, admin users will be able to import their old sogo.conf file on the admin interface and SOGo 6 will configure it automatically. Apart from this, all the others services stay as they are!
Additional context
No response
This blog post update might be relevant:
Updated: 2025-09-30:
After the community’s feedbak, we decided to keep the support of MariaDB. You will still need to use the scripts to migrate from the old table structure to the new one.
We have this on track and are in close contact with Alinto regarding our partnership and the usage of SOGo in mailcow, as they know how relevant mailcow is for their SOGo Project and how important SOGo is for mailcows Groupware part.
- For performance and troubleshooting reasons, support for ActiveSync will be removed and replaced by another Microsoft protocol: MAPI over http
This is the most important change I've seen for my users. Everything I've been reading online says that MoH is mainly for desktop clients and EAS is for mobile devices. I don't know how many mobile devices support MoH as well as EAS (online searches lead me to think that no mobile clients support it). The fear is that users will lose functionality by going to SoGo 6 vs. SoGo 5.
Right now MAPI is only for Desktops. Mobile Devices need to setup IMAP/CAL/CARDDAV manually.
On Apple you can use the Mobileconfigs, available from mailcow UI in order to setup mails + calendars. On Android autoconfig should work, which (if configured via DNS) will present you Calendars and contacts too.
So theoretically there is no feature loss.
It's actually improving the usage of Outlook Desktop Clients in many ways, as MAPI is the more reliable protocol in general, which is currently not available on mobile devices (if anytime ever).
So theoretically there is no feature loss.
What about (instant) push notifications on iOS?
What about (instant) push notifications on iOS?
(Offtopic) For that there is IMAP Idle, but still not supported from Apple Mail AFAIK.
What about (instant) push notifications on iOS?
(Offtopic) For that there is
IMAP Idle, but still not supported from Apple Mail AFAIK.
This would be a massive feature loss and in my opinion an argument not using mailcow / sogo anymore.
- For performance and troubleshooting reasons, support for ActiveSync will be removed and replaced by another Microsoft protocol: MAPI over http
This is the most important change I've seen for my users. Everything I've been reading online says that MoH is mainly for desktop clients and EAS is for mobile devices. I don't know how many mobile devices support MoH as well as EAS (online searches lead me to think that no mobile clients support it). The fear is that users will lose functionality by going to SoGo 6 vs. SoGo 5.
Couldn't ActiveSync be readded by using Z-Push in another container?
