KeyHelp Community

Hello,

Is it possible to use client own domain webmail like client.com/webmail instead using my main vps webmail vps.com/webmail
Im using ubuntu 24


Thank you

Solution 1: Just install a separate webmail for your client
Solution 2: use Apache Reverse Proxy
Solution 3: Make a redirect 302 to your VPS webmail.

Let's hope this feature will be "built in" soon. Matter of fact webmail.clientdomain.com makes more sense. All these workarounds are "ugly hacks" and one panel like Keyhelp should not be without this feature.

So there is no solution for this... Because keyhelp use same login panel for admin and client, right?

bryan372 wrote: ↑Mon 30. Dec 2024, 00:16 So there is no solution for this... Because keyhelp use same login panel for admin and client, right?

I had understood your initial question to be about webmail - now you are talking about the panel?!?

So yes - Keyhelp uses the same page for the login to the panel, and it depends which username and corresponding password you use - accordingly you will end up in the Admin page or a User page version of the panel. The latter can be restricted by the Admin.

For the Webmail, Keyhelp offers 2 clients - Roundcube and SnappyMail. You can select one of them in the configuration settings, and this choice of client will be applied for all users of that server. At least when using the standard login URL (https://your.serverdomain.xyz/webmail/). @Tobi has pointed out alternatives to this standard.

I agree with @amarc though that it would be a great Keyhelp feature, if a login to the Webmail would be possible through https://webmail/userdomain.xyz by default (and keep that URL also in the browser addressbar). But this would require the creation of this subdomain by default when adding a new domain to the server (for the LE certificates). Maybe it could be made an option during the procedure of adding of a domain ... that would be my wish.

What exactly is wrong with simply typing webmail.maildomain.tld? This works out of the box without any changes. Is the problem, that it's redirected to paneldomain.tld/webmail? Or what else is the problem?

tab-kh wrote: ↑Mon 30. Dec 2024, 11:07 Is the problem, that it's redirected to paneldomain.tld/webmail?

Yeah exactly. Looks ugly - the user would like to handle mail under own domain.

Got it, Thank you all for the answer and suggestion...

technotravel wrote: ↑Mon 30. Dec 2024, 16:13

tab-kh wrote: ↑Mon 30. Dec 2024, 11:07 Is the problem, that it's redirected to paneldomain.tld/webmail?

Yeah exactly. Looks ugly - the user would like to handle mail under own domain.

As a hosting provider, I want my customers always to use my company website. My customers need to know that email works best through us.

If a customer explicitly wants their own webmail, this is an additional service for a fee. After all, there is a separate instance to administer. This security-conscious clientele prefers its own company server anyway for reasons of data sovereignty and privacy.



Translated with DeepL.com (free version)

Tobi wrote: ↑Tue 31. Dec 2024, 12:21

technotravel wrote: ↑Mon 30. Dec 2024, 16:13

tab-kh wrote: ↑Mon 30. Dec 2024, 11:07 Is the problem, that it's redirected to paneldomain.tld/webmail?

Yeah exactly. Looks ugly - the user would like to handle mail under own domain.

As a hosting provider, I want my customers always to use my company website. My customers need to know that email works best through us.

If a customer explicitly wants their own webmail, this is an additional service for a fee. After all, there is a separate instance to administer. This security-conscious clientele prefers its own company server anyway for reasons of data sovereignty and privacy.



Translated with DeepL.com (free version)

I am not sure where you do business or who your clients are but I guarantee you 99% of clients want webmail.theirowndomain.tld. Why would anyone want their company email on webmail.someothercompany.com ? Fact that all other, "top players" (cPanel, Plesk...) do this "by default" tells you something no ?

Also suggestion that I should create webmail as separate app for each makes no sense.. Does this mean I need to take care of updates, 0-days etc.. on each ? How do I do this if I have 100 clients/domains/webmails ?


And this is probably as simple as creating symbolic link (or similar) from "Keyhelp's Webmail location" to "User's domain vhost location" and pointing webmail subdomain there

As I sad earlier:

Solution 2: use Apache Reverse Proxy

Quick, fast, reliable.
I use some Proxies for webmail and other services.
Set it and forget it…

Tobi wrote: ↑Tue 31. Dec 2024, 17:59 Set it and forget it…

Problem is you have to set it for every domain ... would be nice if it could be done (semi-)automatically during domain intallation. Through a tickbox, for example.

technotravel wrote: ↑Tue 31. Dec 2024, 18:51

Tobi wrote: ↑Tue 31. Dec 2024, 17:59 Set it and forget it…

Problem is you have to set it for every domain ... would be nice if it could be done (semi-)automatically during domain intallation. Through a tickbox, for example.

I totally agree with that way to look at the things.

Someone who has a decent knowledge of Linux and all services required could run a similar setup like with KeyHelp manually.
But that is not convenient.

IMHO there are at least two valid reasons to use a panel like KeyHelp:
1) The user simply has not that know how to get all the stuff running on it's own.
2) The user wants to get rid of error prone and tedious workflows.

Making https://webmail.customer.com available just by a mouse click would definitely fall under 2).

As I personally don't use webmail at all I didn't spend much time in it, but I think some of my users would love such a feature.

Tobi wrote: ↑Tue 31. Dec 2024, 17:59 As I sad earlier:

Solution 2: use Apache Reverse Proxy

Quick, fast, reliable.
I use some Proxies for webmail and other services.
Set it and forget it…

You mean solution where URL actually ends up with "uggly" https://webmail.sometld.com/webmail/

I don‘t get the point why the path „webmail“ should be ugly. It is just a domainpath?

You don‘t use phpMyAdmin either because of „db-administration“ in the domainpath?

But if you want to get rid of the „webmail“ path, just add „substitute“ to your proxy directives.
https://httpd.apache.org/docs/2.4/mod/m ... itute.html

But this is very tricky and not very easy to handle. Anyway feel free to try.