Feature or Bug in Sogo Morch 2026 Update?

Ganzjahresgriller

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.

CK_beats

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…

DocFraggle

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 in #7086
[SOGo] Update to 5.12.5 by @FreddleSpl0it in #7098

CK_beats

DocFraggle
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.

DocFraggle

CK_beats did you already roll back? Is it working again?

CK_beats

Ganzjahresgriller
DocFraggle

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.

Ganzjahresgriller

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

DocFraggle

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?

CK_beats

DocFraggle 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.

DocFraggle

CK_beats There seem to have been some hotfixes 2 hours ago:

mailcow/mailcow-dockerizedcommits/master/

I updated after they got merged, so maybe try again now. For me, everything works out right now (on my testcow that is)

CK_beats

DocFraggle
Thank you very much for the tip!
Maybe my error was reproducible.
I’ll make a new attempt this evening.

jprpic

Hi, i just make an update and get in the problems, login UI opens but when i enter user credentials and try to login, just get white blank page. Login in /admin works OK. Also get this error message:

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] => jtest@test.hr [1] => test [2] => Array ( [role] => user [service] => MAILCOWUI ) ) ) [1] => Array ( [file] => /web/inc/triggers.user.inc.php [line] => 136 [function] => check_login [args] => Array ( [0] => jtest@test.hr [1] => test [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] => )

Edit: I’m using LDAP (389 directory) in container as Identity Provider. So far, no problems until this update.

Stollentroll

I have the sam Failure. I installed the update on the backup mail server this morning. I can log in locally as both admin and user. However, when I try to authenticate using LDAP, I get the white screen of death:
Message:
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] => xxxx@xxxx.com [1] => Password [2] => Array ( [role] => user [service] => MAILCOWUI ) ) ) [1] => Array ( [file] => /web/inc/triggers.user.inc.php [line] => 136 [function] => check_login [args] => Array ( [0] => xxxx@xxxx.com [1] => Password [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] => )

If I switch my test-user from LDAP to “Mailcow” authentication, the login works. VM ESX snapshot rollback and LDAP are working. I restarted the update 10 Minutes ago – the same error. No errors in the SoGo log, and the crontask only shows the usual background noise.

CK_beats

This confirms my suspicion that there is a problem with authentication via LDAP data.
I checked the LDAP connection to our domain controller via the admin console. No error was reported here.
Currently I haven’t found any other solution than performing a complete rollback.

jprpic

CK_beats
Yes, rollback solved the problem, will stay on 2026-01 until this is fixed. I the future, first will update test server before prod. 🙂

Ganzjahresgriller

I’ve had yesterday probems with certificates too. Today it’s ok now, but this Problem already exists: "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."

I have now started an issue on GitHub.

DocFraggle

Ganzjahresgriller I just updated my Testcow again and checked out your issues, no problem here with the latest Sogo container… I can reply and forward, the original mail is included, no empty window. And also the signature is inserted like it should.

Ganzjahresgriller

I just ran the update. My problems are solved. Thanks to the MC Team

CK_beats

jprpic Good if you have a test server. 😅😅😅 I always install the updates straight into the productive system. Then you have to live with a certain amount of downtime. But as long as there is no data loss, everything is fine.

Has anyone already checked whether the problem with LDAP authentication was also solved with the hotfix?

esackbauer

CK_beats LDAP authentication was also solved with the hotfix?

One user reported on github that is was fixed. Dont know if this fix is already in the repo and active.

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.