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

I can unreservedly recommend the current update status 2026-03a.
Our configuration with LDAP, Active-Sync & standard clients such as. B. Outlook now works smoothly.
We’re still on Snapshot until tomorrow or the day after. But so far no problems have been identified during the installation.

DocFraggle

I upgraded yesterday evening, everything works just fine.

bpsintl

Thanks, I will give it a go next week. Luckily I can do a snapshot on the vps beforehand so can roll it back if need be.

Ganzjahresgriller

Yes, 2026-03a works fine for me

bpsintl

Just upgraded to 2026-03a and everything looks ok so far

« Previous Page