Different Hostnames for MX, POP, IMAP, SMTP, and Webmail (RoundCube) URL

Shaijee

I hope this message finds you well. I am writing to propose a feature request that I believe would greatly enhance the security and flexibility of email services.

Currently, within the Enhance system, the MX, POP, IMAP, SMTP, and Webmail URL (RoundCube) all are same hostname, such as mail.example.com. While this setup serves its purpose, it presents a significant challenge when it comes to implementing security measures, particularly with services like Cloudflare.

As we are all aware, utilizing Cloudflare for DNS and DDoS protection is a common practice. However, with the current configuration, we are unable to fully leverage Cloudflare's capabilities to protect our webmail login due to the same hostname.

To address this issue, I propose the implementation of separate hostnames for each protocol, namely:

MX -> mx.example.com
POP -> pop.example.com
IMAP -> imap.example.com
SMTP -> smtp.example.com
Webmail (RoundCube) -> mail.example.com

By adopting this approach, we can not only enhance the security of the email services but also provide users with more granular control over DNS configurations, optimizing performance and reliability.

I believe that separating the hostnames for these protocols would be a valuable addition to the Enhance Panel system, offering improved security posture and flexibility for both administrators and end-users alike.

Thank you for considering this feature request. I look forward to hearing feedback from the Enhance Team & community and discussing potential implementations further.

DracoBlue

It doesn't make sense, I would just change the RoundCube access address.
MX -> mail.example.com
POP -> mail.example.com
IMAP -> mail.example.com
SMTP -> mail.example.com
Webmail (RoundCube) -> webmail.example.com

Shaijee

DracoBlue It doesn't make sense, I would just change the RoundCube access address.
MX -> mail.example.com
POP -> mail.example.com
IMAP -> mail.example.com
SMTP -> mail.example.com
Webmail (RoundCube) -> webmail.example.com

You can change for a few domains and the central webmail (webmail_1), but how can you do it for lots of clients and domains?

It's always better if this comes by default. Think practically, mate.

alenguav

Shaijee cPanel uses webmail.domain.xx subdomain for webmail so why don't use the same?

Nickske00

I'm not sure what problem you are looking to solve here? The url's you use don't really matter, I myself always configure the server hostname everywhere in my email applications... I never use the subdomains the mailbox belongs to. And it always works.

Isaia-Arknet_PTY_LTD

Nickske00

Enhance allows you to move email servers with ease, and advertise this as a problem fix for when a server is overloaded or storage is getting to its limits, with a few clicks, move, let's say, 50% of email clients on a new server.

The problem is that if clients set up email services (servers with Server hostnames), the moment you move 50% of clients, they all need to change the server hostname in their settings.

Nothing needs changing; they continue using the service like nothing happened. If all of them use mail.their-domain.com
All you need to do is a short TTL on snd for mai.their-domain.com

Should you have imap and pop3 and so on separate A values? I am not sure if it helps, but in specific cases, it can offer a more granular setup.

Shaijee

Nickske00 Let me explain the situation I am trying to fix.

Let's say I added a domain called "example.net," and the DNS is set like this:

Webmail login: mail.example.net -> IP (0.1.2.3)
POP -> mail.example.net
SMTP -> mail.example.net
IMAP -> mail.example.net
MX -> 0 mail.meclbd.net

Now, if I protect the Webmail login (mail.example.net) with CloudFlare, then all MX, POP, IMAP, SMTP will be proxied, and the email will not work. I hope you understand my point.

That's why I requested to update the email hostnames as follows:

Webmail Login -> mail.DomainName
POP -> pop.DomainName
IMAP -> imap.DomainName
SMTP -> smtp.DomainName
MX -> mx.DomainName

In this case, we can easily use CloudFlare to protect the Webmail Login. Moreover, all the hostnames will be user-friendly and meaningful.

Shaijee

alenguav cPanel uses webmail.domain.xx subdomain for webmail so why don't use the same?

Enhance panel uses the "webmail" subdomain for the global mail domain webmail.YourCompanyDomain. If you prefer not to use the global domain, it will default to mail.ClientDomain, this setup is user-friendly, concise, and ideal for non-technical clients.