Mailcow-dockerized: Change main URL for Admin panel

[lucianlazar1983]

Hi there, how can I change the main URL? I would like that whoever reaches mail.host.com instead of seeing the MailCow login, instead redirect to /sogo, and for administrative login use for an instance /admin.
Is it possible?
Thank you

[chaosbunker]

why not forward host.com/webmail to mail.host.com/SOGo instead?

I think the way it is set up right now is good.

[lucianlazar1983]

My problem is not that, the problem is whoever try to access https://server_host will default to the login page. I am trying to hide the login page and make it accessible only with a custom url

[Braintelligence]

You do realize, that people need that page to set up some personal stuff for their mail account?

[lucianlazar1983]

I perfectly realize, but i know my customers very well and they only need a webmail and change the password (that si done from sogo right?)

[chaosbunker]

No, that is done via mailcow ui

[lucianlazar1983]

ok, no problem with that and the user can use /admin in order to access that. My purpose is to not have the admin UI login as the default page for server_address. Can it be done without being overwritten by future updates?

[Braintelligence]

You change the password via Mailcow ui. People also see the mail app configuration instructions there and can create aliases. These are core features...

[Braintelligence]

You can try forwarding or change the nginx.conf and stash the changes. Pop them after an update, as we did before we had a update.sh script.

Still the user and "admin" login to manage the mail account on a meta level are the same page. I don't see the use-case yet trying to hide this, since people will want to be able to change their password and set up aliases.

All my users wanted to be able to do this. Especially the temporary spam alias can be very helpful.

[lucianlazar1983]

I did not say that this should be a core feature or modification of the product. I simply asked if there is a way for ME to change this behavior without loose changes over upgrades.

[lucianlazar1983]

of course, this is useful, but my customers could get confused on where they should input their details in order to read emails. Unfortunately, they are not technical people and the barely know how to deal with a webmail (this is a sad reality)

[Braintelligence]

You can sell the Mailcow UI as an entrance to SOGo, since it is available as app there. This could prove advantageous in the future when Mailcow starts to incorporate other apps there.

[reinistihovs]

Easy way to limit acces to mailcow UI only from one IP:

add this in mailcow-dockerized/data/web/index.php
after "

if ($_SERVER['REMOTE_ADDR'] != "Your.Public.IP.Address"){
header("Location: ./SOGo/");
exit();
}

This way everyone will be redirected to SOGo and wont have access to the admin panel at all, and for user password change you can enable it in /mailcow-dockerized/data/conf/sogo/sogo.conf
by setting SOGoPasswordChangeEnabled = yes; ( restart SOGo afterwards)
tested, and works

[mkuron]

Duplicate of #393