I just installed the Moorch 2026 update. When I try to reply to or forward an email in Sogo, I get a new, empty window, as if I were starting a new email. The signature isn't inserted in new emails, even though it's selected in the settings.

Nothing works at all in my instance. No synchronization between Outlook and the server, between mobile devices and the server, and SoGo. Everything dead. Only the admin interface is accessible. The following error message is displayed: `An unknown error occured: TypeError Object( [message:protected] => Cannot access offset of type string on string [string:Error:private] => [code:protected] => 0 [file:protected] => /web/inc/functions.auth.inc.php [line:protected] => 368 [trace:Error:private] => Array ( [0] => Array ( [file] => /web/inc/functions.auth.inc.php [line] => 39 [function] => user_login [args] => Array ( [0] => meine E-Mail Adresse [1] => mein geheimes Passwort [2] => Array ( [role] => user [service] => MAILCOWUI ) ) ) [1] => Array ( [file] => /web/inc/triggers.user.inc.php [line] => 136 [function] => check_login [args] => Array ( [0] => meine E-Mail Adresse [1] => mein geheimes Passwort [2] => Array ( [role] => user [service] => MAILCOWUI ) ) ) [2] => Array ( [file] => /web/index.php [line] => 3 [args] => Array ( [0] => /web/inc/triggers.user.inc.php ) [function] => require_once ) ) [previous:Error:private] => )` Trying to roll back...

Hmm, I guess I'll wait with updating... anybody else with problems? They seem to have rebuilt Sogo from scratch in this release: [SOGo] Build SOGo from source with security patches by @"FreddleSpl0it"#2234 in #7086 [SOGo] Update to 5.12.5 by @"FreddleSpl0it"#2234 in #7098

@"DocFraggle"#p31237 The update was installed without any errors for me after I had reset my modified rspamd.local.lua back to its original state. All services were online and Docker was completely available. After that nothing worked at all. Only the admin interface was accessible.

@"CK_beats"#p31238 did you already roll back? Is it working again?

@"CK_beats"#17326 Did you perform the rollback? Would you mind posting here exactly how you did it?

@"Ganzjahresgriller"#p31240 @"DocFraggle"#p31239 We use Microsoft Hyper-V on Windows Server 2025 as a hypervisor. I will create a snapshot before every update and close all incoming ports beforehand so that no more changes can be made. We don't have high availability. As soon as the update appears to have been successful for me, I open the ports again and the bounced emails are delivered. A few hours later I usually remove the snapshot. So I simply rolled back to my created snapshot and everything went back to normal. I am now on version 2026-01 back and everything works as fine as bevore.

I just updated my testcow (clone of my production mailcow, using the cold standby script every night) to 2026-03, no problem here. Replying, forwarding, everything in Sogo works normally here Do you have any other overrides/changes in your setup? [upl-image-preview uuid=7b764960-9a9d-4324-a0d6-59c218d41cf8 url=https://community.mailcow.email/assets/files/2026-03-10/1773142141-774030-image.png alt={TEXT?}]

@"DocFraggle"#p31242 I only adjusted the `Rspamd.local.lua` because we keep having problems with the file attachments and Outlook 2016. In addition, the "bad file attachments" for RspamD have been reconfigured. But no changes made to SoGo. I suspect that the error is related to our LDAP domain controller. An account set up via LDAP cannot be accessed via SoGo. Admin access is set up locally on Mailcow.

@"CK_beats"#p31247 There seem to have been some hotfixes 2 hours ago: https://github.com/mailcow/mailcow-dockerized/commits/master/ I updated after they got merged, so maybe try again now. For me, everything works out right now (on my testcow that is)

@"DocFraggle"#p31249 Thank you very much for the tip! Maybe my error was reproducible. I'll make a new attempt this evening.

Feature or Bug in Sogo Morch 2026 Update?

CK_beats

esackbauer
Thank you for your feedback.
The changes have not yet been incorporated into the current update.
Still getting a blank page after entering user details.
Active-Sync is also no longer functional.

I guess I still have to wait.

DocFraggle

CK_beats Active-Sync is also no longer functional.

That was fixed already, did you update again?

CK_beats

DocFraggle
I updated 10 minutes before my last post.
The problem had still occoured.
Perhaps the hotfix was implemented some minutes after my last try to update.

DocFraggle

CK_beats I was talking about this:

mailcow/mailcow-dockerized9ad84ee

that was merged yesterday, so I thought ghcr.io/mailcow/sogo:5.12.5-3 should have ActiveSync now

CK_beats

DocFraggle
I understand. Then I definitely downloaded the last staple.
But the problem still existed.
Admin interface can be accessed normally. But LDAP authenticated users cannot log in.
All you see in SoGo is a blank white page, Active Sync doesn’t work at all.
Here the client reports that the server is offline.

The update only reports that my rspamd.local.lua is modified. The rest of the files are unchanged.

DocFraggle

Kevo I had to rerun the update to get the Sogo Active Sync fix. Now everything seems to be working fine for me.

CK_beats But LDAP authenticated users cannot log in.
All you see in SoGo is a blank white page, Active Sync doesn’t work at all.

So this may be due to the LDAP problems, then… ActiveSync seems to work for Kevo

Kevo

I had to rerun the update to get the Sogo Active Sync fix. Now everything seems to be working fine for me. Thanks for the quick resolution on that one. :-)

Kevo

DocFraggle

Just to confirm, I am not using LDAP.

CK_beats

DocFraggle
I can neither confirm nor deny whether Active-Sync works.
I can’t test this because all of our users synchronize on an Active-Sync basis.

Unfortunately, as of now, I can’t apply the update because then our entire mail system stops.

Stollentroll

Unfortunately, everything is the same as before. Thank God I have VM-Ware and snapshots, plus a replica of my active mail server. So I can try things out completely relaxed. 18:30 rollback to 2026-01, login with LDAP users works, update again to 2026-03. The error is there again. Picture-1 and control test login with local admin and user works, The Blacked is only the Log-In Credentials.

Function check of the LDAP connection - see picture 2 = OK. So a few mailboxes I deleted manually, LDAP query reduced to 10 minutes - and waited… No false “all good” message, after that time the missing mailboxes were recreated from the ADC. So the LDAP access must work properly.

And so my active MailCow will remain at the January level :-)

CK_beats

Stollentroll
Same here.
It currently does not seem to be possible to install the Moorch update in a productive environment.

Stollentroll

I am going to have the fun this evening of completely deleting my replica and reinstalling it. Let’s see if the error also occurs with a new installation. Just out of curiosity.

DocFraggle

It seems @FreddleSpl0it fixed something regarding the LDAP problem:

mailcow/mailcow-dockerized7123/changes

It’s not merged into master yet, so you would need to edit this manually

Stollentroll

Its functional. After applying and restart of all Docker-Containers LDAP Auth is working. Via Putty to the Host-Console:

cd /opt/mailcow-dockerized

curl -L https://patch-diff.githubusercontent.com/raw/mailcow/mailcow-dockerized/pull/7123.patch -o pr7123.patch

git apply pr7123.patch

docker-compose restart

Reload the Webinterface in Browser and its working.
Many thanks to the programmer of the patch!

CK_beats

Wohooo!
I got it, too!

Thank you very much for your instructions Stollentroll .
With integrating this patch we got up to version 2026-03.
Active-Sync and the SoGo webinterface works now great.

Now it would only be an advantage if the patch is implemented in the main update. To make it easier for the next admins.
I have another general question: Is it possible to tell the update script to simply overwrite standard system files that I have changed?
Except of course the extra.conf. But this is ignored with every update.
I always have problems with the update getting stuck on my rspamd.local.lua because it is modified.

Don’t any of you actually use the domain-wide footer together with Outlook (and file attachments or embedded graphics in the text)?
Is it just me that has problems

Heini_usw

Stollentroll

Thank you. That fixed it for me too.

Stollentroll

This isn’t my work. The patch was made available on GitHub – I only created the instructions. Because I spent quite some time puzzling over how to get it into my Mailcow.

esackbauer

Update Moorch Revision A is available:
mailcow/mailcow-dockerizedreleases/tag/2026-03a

CK_beats

👍👍👌👌 Installed and working!

bpsintl

i’ve been monitoring this thread as I was scared to update our production server. Is it safe to upgrade now? I just have a default install with about 50 domains and about 360 mailboxes.

« Previous Page Next Page »