Open
Conversation
* Initial plan * Fix duplicate login announcement display Co-authored-by: DerLinkman <62480600+DerLinkman@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: DerLinkman <62480600+DerLinkman@users.noreply.github.com>
…rify-hash Support for PBKDF2-SHA512 hash algorithm in verify_hash() (FreeIPA compatibility) (issue 6646)
🐄🛡️ January 2026 Update | Limited EAS/DAV Access and Restricted Alias Sending
[Hotfix] Update 2026-01
Update 2026-03
Hotfix 2026-03
Hotfix 2026-03
Hotfix 2026-03
Update 2026-03a
Hotfix 2026-03a
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
This fixes two related issues in the user webmail SSO flow:
Webmailentrypoint currently links directly to/SOGo/so, which bypasses the intended SSO handoff path.sogo-auth.phpcan reject a mailbox user's own SSO login because it only accepts alias-based lookup in paths where the mailbox itself should also be valid.Changes
/sogo-auth.php?login=%u/sogo-auth.php?login={{ mailcow_cc_username }}sogo-auth.php, allow the currently logged-in mailbox user through the same SSO path without requiring alias lookupuser_get_alias_details()is not the matching mechanism%uWhy
In our reproduction, mailbox users could hit
Unauthorized/ broken webmail navigation because the user-facing entrypoint skipped the SSO helper, and the SSO helper itself was stricter than necessary for the mailbox owner case.Validation
I was able to reproduce the broken user webmail flow and confirm that these changes restore the expected SSO navigation path.
I could not run local PHP linting in this environment because
phpis not installed here.