EnglishI currently have 2 domains pointing to my mailcow. The subdomain email is what I normally use to get there, however I also have a subdomain webmail that I setup with a custom Nginx config that always redirects users to /SOGo/.
With the new authentication system, if I configure mailcow to use an external identity provider, can I then make it redirect users to either mailcow or SOGo depending on the initial domain they used to connect?
With “domains” you mean 2 different hostnames or FQDNs?
What is a “subdomain email”?
Please use proper DNS terms like MX domain/record, A records etc. as used in the 
documentation. docs.mailcow.email
Have something to say?
Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!
esackbauer Sorry for the confusion. This has nothing to do with email, it’s just 2 different subdomains. I go to email.example.com to access mailcow, and webmail.example.com to access SOGo.
Also, I guess another way that my desired setup could be achieved is if mailcow properly redirects you to your original URL after login. Because the webmail subdomain simply redirects / to /SOGo/, as long as mailcow keeps track of the fact that I originally navigated to /SOGo/ before being redirected for login, then it can just send me back there after login is complete, regardless of the host the server sees.
You can configure where the users should land after authentication.
There is now only 1 link: mail.example.com
After logon, users are automatically transferred to SOGo, and have a mailcow button in the corner to reach their user mailcow UI.
Or you can configure that they stay in mailcow UI, and need to press the Webmail button to be transferred to SOGo.
No need anymore for a second FQDN/hostname. I guess its not even possible anymore to use a second.
esackbauer That’s what I suspected might be the case… Perhaps I will have to modify it.
