esackbauer That’s what I suspected might be the case… Perhaps I will have to modify it.
PPseudoResonance
- 3 days ago
- Joined 4 days ago
- 1 discussion
- 3 posts
- 0 best answers
- Post posted... wait what?
- Edited
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.I 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?