Currently running: dockerized 2025-07
As noted elsewhere, the SoGo login has been disabled since March 2025, however, my users are sent to the SoGo login page when their webmail session times out. Even thought the primary login is via the mailcow UI as intended, users get “trapped” in the SoGo login and many don’t know how or want to fix the URL. I assume there is a place to force that redirect within the settings, but I couldn’t find. Someone please feel free to share it.
The announcement here: mailcow/mailcow-dockerized6503
“All unauthenticated requests to /SOGo will be redirected to /. Users must use the new mailcow login. However, Administrators can define whether a user should be redirected to the mailcow UI or SOGo after login inside UI.”
However, in my instance this does not happen. unauthenticated requests are still presented with the SoGo login screen.
In the mean time, I created a short script and added it to the /data/conf/sogo/custom-sogo.js file:
userfield=document.querySelector('input[ng-model="app.creds.username"]');
if (userfield){
//oops we don't want to be here
location.href="/";
} else {
//carry on, nothing to see here
}
If you do this, bounce sogo with:
docker compose restart sogo-mailcow
Note, the idea here is to only fire this redirect if the login user field is on the screen. Which I assume will never show anywhere else in SoGo.
This seems to fix it for either a login timeout or an accidental visit to https://mysite.com/SOGo/…
Again, someone please share the proper way since couldn’t find one.
