cPanel & WHM Version 80 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!
 

Mail Only version of cPanel & WHM

Eduardo G. shared this idea 6 years ago
In Progress

As a Server Administrator, I want a WHM/cPanel Mail Only version of cPanel & WHM, so that I can ease the load on my main server.


As a servers and datacenter administrator, I'd like to separate email servers from hosting servers, so that I can have a hosting farm and an email farm.

I see many advantages here:

- less hosting server load

- less bandwidth usage in web servers

- faster web rendering

- change/move hosting not affecting email service

- more specific firewall and security policies for each cluster

Best Answer
photo

As we mentioned on the blog last week, this feature is now in progress. The team has merged Phase one in to cPanel & WHM Version 76, which is just standalone Nodes. The current timeline with this one (with the normal "there are still lots of moving parts" caveats):

Phase one (76)

Introduce MailNode


  • allow brand new "MailNode" servers to be built, not conversions, and no connections to other servers.

Phase two (78)

  • Add the ability to link two servers, only when building the servers brand new

Phase three (80?) & four (82?)

  • Various iterations of migrations

To avoid spamming all 800 subscribers with followup comments, I'm going to keep them locked here, but if you have questions not answered here or on the blog, feel free to reach out to me directly or to the community team.

After the cPanel conference (which is just 8 days away!) we'll have more information coming out on the blog to discuss our plans, and what feedback we need from our users. For now, feel free to install the EDGE version of cPanel & WHM 76. If you are interested in testing MailNode in a production environment (as a brand new server) as Version 76 moves to the production tiers next month, and need a development license, feel free to reach out to your account manager (if you're a partner) or to me! Expect another update from me here in early 2019, if not before.

Comments (118)

photo
4

Completely agree - we often sell servers specifically for the purpose of email hosting - and it's a pain in the behind having to separate from existing cPanel hosting. It would avoid clients using third party services like Google Apps, etc. for email.

photo
12

I'd be happy with the creation of "email only" accounts, that allowed no FTP/File access at all.

photo
2

So far as i am aware you do not need anything extra to do this you just need to know how to set it up, so long as the mail server is running you can configure that it is the backup mail server.


If you wanted to be absolutely technical, you could actually use them as the primary mail servers. How cpanel feels about this i would not know. but it is entirely possible.

photo
6

Very good feature request - this could essentially be topped off with it being in a cluster as to allow for multiple mx records - and ultimately a redundant set-up.

photo
4

Why cannot this be performed by tuning the service manager and limiting the features in the packages? That is what I'm doing right now. What advantages could be obtained? A lower licensing cost like in DNS only?

photo
4

Kent Brockman wrote:

Why cannot this be performed by tuning the service manager and limiting the features in the packages? That is what I'm doing right now. What advantages could be obtained? A lower licensing cost like in DNS only?
It can, but everything has to then be managed separately. You can't have a client log into one CPanel account and manage both their email and web hosting if they are on separate servers. Also, the email DNS settings have to manually maintained.


Licensing cost isn't an issue as far as I'm concerned. I'd gladly pay for another license for a separate mail server.

photo
2

Agree with Ken, Licensing is not a issue.


In addition, I hope cPanel can consider a MXONLY server. MX is playing a very important role. It can perform easier control over the entire Mail Service. It also ensure that no mail lost even when the actual mail service is down.


Hope cPanel can consider implementing soon! =)

photo
4

This would be great, now we can separate mysql and dns services, it would be great if we can separate also mail services!

photo
1

I feel like this would be a great addition to cPanel DNSOnly servers. I have many DNSOnly servers and I like to be able to configure the server directly from WHM and not from SSH commands. I do not know how to configure them as a mail exchanger or holder but if cPanel were to add that functionality, it'd be using it for sure.

photo
3

We would love this to actually be a mail gateway for both sending and receiving, a gateway with a good antispam for both incomming and outgoing e-mail. This would solve quite a few issues like outgoing antispam not currently usable as well as being able to close port 25.

photo
3

I will love this feature, with this i will able to offer to my client reliable email server

photo
2

This would be fantastic. Especially if you could create some type of relationship with the hosting server so that email accounts could be created by users on the web hosting server and created on the email hosting server. Basically what jmginer said above.

photo
8

I'ld love to see this feature as well. A lot of competitors are seperating web hosting disk space from e-mail hosting disk space, but unfortunately we can't.


We have our cPanel servers in a VMWare HA cluster with expensive SAN storage (15k rpm disks). For e-mail we could easily use slower disks and thus less expensive. It would allow us to offer our customers greater disk space for their mailboxes at the same or a (much) lower cost.


By limiting the web hosting disk space, we can better control the resources that are being used by the accounts. For example, if we now offer 1GB disk space, one could use it for a 900MB MySQL database, while someone else uses it for a 900MB mailbox. Of course there is a great difference on the impact this could have regarding CPU/memory/IO resources.


Other advantages, apart from what has been mentioned before:

- Create more competitive packages

- Being able to use different back-up policies

- Possibly less licenses for AV or spam filtering

- Easier monitoring (i.e. abuse)

- Less single points of failure

- Users accounts won't be suspended because of a mailbox filling up the total quota and users will still be able to login to cPanel/Webmail to clean up the mailbox.


Of course, (for me) this is only interesting if the mailboxes can be managed from the same CP as it is now, but knowing that they reside on other server(s).

photo
2

I currently offer my clients webmail ONLY packages, via a standard cpanel server.


I would like this new cPanel mail only to have a feature to transfer accounts / packages from another cpanel server to the mail only server, so it would save time.

photo
3

I have a few servers and most of my clients choose to use SSL for mail (as suggested by the email config screen). This makes it a pain to migrate these customers to new servers as they have used the server hostname in the settings. I would love to have a setup where the email was hosted on one server and web on another, so I could shunt accounts around without having to tell clients to reconfigure their mail accounts.

photo
2

There's no way to sync calendars, contacts, emails, notes with Outlook and mobile devices and this causes us a great imbalance to compete with large companies , since the vast majority of our clients are companies that use the service much. Cpanel is delayed in helping medium-sized enterprises or simply not in your market benefits. Which we should have a solution to the issue, and we paid a membership for customers.

photo
2

I would love to see this option even if it where only available as a separate service on an additional server.

photo
1

Any updates on this request? cPanel please update now!

photo
1

Yes, it would be nice for sure!

Please cPanel, what about doing it?

photo
1

This would allow us to open up an entirely new niche hosting business (and service).

photo
2

I was thinking about this a few years ago. Glad to see I'm not the only one thinking this is a MUST HAVE

photo
2

Hello, any news? We've dns servers basically unused, and it's great if we can add email service to dns only servers

photo
1

A first step would be a support for using the customer domains as mailserver names when using a (wildcard) cert . The new normal with SSL always on mean you cannot transfer an account from one server to another without forcing the customer to change hostnames in every client.

photo
1

This would be better for email marketers who need to deliver high volume email each day. We really want a email version only of cPanel/WHM Server focusing on more sophisticated email stats tools.

photo
2

This does make alot of sense. Webhosts could go 100% ssd for webhosting files, and use normal 3 or 4 tb drives for email. For supplying high availabily seperating e-mails from web files makes sense too. On an e-mail server you would probably create small block sizes as there will be alot of small files. For backups e-mails should be seperate too. A customer with 10gb of e-mails and 200mb of website, doesn't want to download a full backup over 10gb to restore his website.


From a selling perspective, we find customers need to have the simpelest offer to understand. Offering 50 x 2gb accounts, is much easier to understand than explaining to customers that they have to share webspace with e-mail accounts. Should a website stop working if a large number of e-mails are recieved ?


For e-mail, we want to have different server specs, different backup settings, have a single server between multiple web servers thus allowing to move a website without affecting e-mail account client configuration.


We basicaly need a cpanel server without the possibilty of creating apache virtualhosts, we want users to be able to create and manage e-mail accounts from inside their main cpanel interface but for everything to be done via the cpanel/whm api on the e-mail only server.


We defenetly want an e-mail only version of cpanel.

photo
1

Would really like to see this coming, it would be good for larger hosts, that wants to separate web, mysql, mail, DNS etc, which IMO is quite normal to do, this is why it would be beneficial for cPanel as well.

photo
1

The concept of having different SMTP servers is good to prevent longtime blocking by freemailers like Hotmail/Outlook.com or Yahoo. With different SMTP servers it should be possible to reroute the flow of mails to different exit IPs. Since it needs 24-48 hours to get a block lifted the other users didn't get their email blocked too.

photo
1

Hello, i've created a feature request for a mysql only version of cpanel and whm.

If you think can be usefull (maybe with the mail only), you find the request here http://features.cpanel.net/responses/mysql-only-version-of-cpanel-whm

photo
1

This will be a very good feature to have .. Save a lot of time and support requests ...

photo
2

We've seen mail starting to increasingly become an issue (IOWait in the 60% range due to mail spikes on a server with RAID-10). Would love to be able to offload mail to a different server so that website speed is not affected.

photo
1

Another point we have for doing this is we use an external gateway for filtering e-mail but still get automated brute force attempts on the main server.


With an external e-mail server, automatic bots wouldn't be able to guess were the pop3 access goes as there would be no external link to it.


For backups this is important too. It's much quicker to restore websites then e-mails, and for most customers so long as new e-mails can be recieved the duration to restore their old e-mails can be much longer that the duration required to restore their website. Obviously for this we would also need a way to quickly restore all e-mail accounts without their contents but that could be another feature request once this one is done :)

photo
1

I actually agree with this.


Having another mail server would be great for people who rely on e-mails in their daily productive lives.

photo
2

Just to add... We would like to not only have mailonly servers but be able to associate multiple mailonly servers to a signe coandl server and also have multiple cpanel servers using a single mailonly server.


This should have been done from the beginning with Mysql servers, so I thought it might be good to add taht here for the email only version of cPanel.


Mail only server should also allow to either have the quota included with the main cpanel quota like with mysql, or should be allowed to be seperate so we could market for example a 5MB hosting account with 10x5GB email accounts and a sort of e-mail only + static webpage account.


If this feature is accepted, we will be setting up a high storage server with for example 12x6TB drives with low CPU (6x2GHz), all incomming and outgoing mail will be scanned by our email gateway removing need for CPU and we could all much larger e-mail accounts.


Our webservers could then be ssd only as without imap e-mail accounts accounts will use much less space.

photo
1

This feature would be really important! Make us happy cPanel! ;]

photo
2

We can already use remote mysql servers. This feature is a must-have. I was going to post a similar request to this one because with CDN services like CloudFlare if your email server is on your web server then your IP(s) can be discovered, nullifying any firewall protection a CDN offers because all an attacker has to do to find your webserver's real IP is query for your mail/mx records.


We already have remote mail available to end-users. Why not allow us to setup a remote email server for all users managed by our WHM?

photo
1

There are many strong arguments and feature elements in this thread. We +1 them all. But it's obviously a significant rebuild - is cPanel silent? I read an external comment saying it was planned for v12. Indeed, this page says 'parent version 12 of cPanel & WHM will include support for multiple cPanel instances.'


cPanel clearly has the vantage position, but if cPanel doesn't do it (and clearly commit to it from now), I foresee a very serious competitor quickly winning over flocks of cPanel customers... simply by collecting some of the excellent ideas in this thread and others that would well become the next (better) cPanel.


I for one hope it's cPanel who moves with the industry needs, because what they've contributed to the community cannot be ignored. Well, shouldn't be ignored, but will gladly be ignored (read: stolen) by a competitor.


I'm convinced that using their experience and setting hosts up for rock solid services (and therefore growth) is what will ensure cPanel's business stability and growth.

photo
1

Yes please.

Heck, even ask a small fee for it ($5 seems reasonable) if required. :)

photo
1

What I find a bit strange is that this feature request now has been open for two years, but is still in open discussion. Wouldn't a fair expectation be that someone from cPanel stepped up and let us know what they plan to do? Surely, after two years I would have thought that the feature request would be either already implemented, definitely on a road-map, or definitely rejected.

photo
1

200 votes, 2 year of discussion with great ideas, and not a single word from cPanel.

I don't expect an ETA, but what cPanel think about this feature request is highly appreciated. We're moving in a world of High Availability and decentralized servers: one for web server, one for emails and one for DB. cPanel is a limit for now, and we can't be competitive.

photo
1

I am a cpanel dns only user and that so far has worked wonders for me.


Having a cpanel MAILONLY server would be an EXCELLENT addition.

photo
1

We use separate web and mailservers. It's not too hard to set up a remote email exchange on a second cPanel server and the benefits are mentioned all the way through these posts.


Having a dedicated system from cPanel to allow this would just make what is already a simple task into an even easier task.


With regard to the comments about adding the email server to the DNS-Only servers, we'd like to see the ability to run the RBL's straight from the DNS servers as a feature within cPanel DNS-Only

photo
1

Blicka, How do you do this without creating confusion ? I guess you would set number of e-mail accounts to 0 on the webserver and block ports to FTP and web on e-mail sever ? Or just use cPanel API ?

I suppose you could then create a plugin that redirects you to the mail server (and maybe even logs you in ?).I didn't think that this was already mostly possible. I'm going to look into it a bit more and try creating a package with e-mail only and a package with everything except e-mail and maybe look into creating a plugin that allows you to log into the other server without entering your login details again or maybe just control the e-mail server with cPanel's API.


It makes a huge amount of sense not to store e-mail on the same server as the websites, I think I might try this for our next setup.

photo
1

pleases have this feature you can charge me 5$ each license both dedicated or vps server.

photo
1

They're not going to work for free :)


Offloading main system means the main servers can host more sites and there will probably be just as much support requests for e-mail related issues as for hosting issues.


So please charge what cPanel thinks best. A full cPanel licence is OK for us.

photo
1

I agree and would be happy to pay a cpanel license for that if it meant that I could basically create a standalone mailserver(s) and cluster them together.


I spend around $750 a month on rackspace mail and I could be paying less than half of that on 2 or 3 2TB mail servers.

photo
2

DNS Only is free, so I think a Mail Only and MySQL Only (or DB Only) will be free. We're in 2015, and other panels are moving in opposite direction: spread services on multiple servers, in order to reach an high availability. There are no balancing of resources, no replication, nothing. I can't believe that. And the worse thing, is that cPanel never post an opinion or a simply reply in 2 years and in a Feature Request with 215 votes.

photo
1

DNS Only hardly requires any support and offloading DNS generally comes with buying more cPanel licences.

MySQL only, is only a way of using an external database server, not a full cPanel server.


Mail Only servers will generate almost as much support requests as a full cPanel serveur so they will require in our oppinion licences set at more than $5.


Our servers are currently restricted by backup times. Offloading e-mail to a server with large disks would mean that we could host more websites on each cPanel server.


What we want is to be able to define server roles but keep a single login for our customers.


What we need is cPanel to communicate with the other cPanel server via the API instead of creating e-mail accounts on that server.


Thinks like the webmail would be moved to the mail only server but creating e-mail accounts would still be done from the main cPanel server.


If cPanel want's to charge less (because maybe they get less support requets) then fine, but we are defenetly prepared to pay the full price as it will allow us to host more customers on the main webservers.

photo
1

You can deliver high quality services, by using normal failover setups - even by separating stuff, you still need to make it redundant.


And there's multiple ways you can make quality services, and great uptime, even with the current 'limitations' of cPanel.

photo
1

Monarobase has a great point and I hadn't considered using a full CPanel install for email only. An API makes a lot more sense both for CPanel and us customers.

photo
1

Hi,


Also RBL like SpamCop blacklist IP of shared server because one client have cryptoPHP or Phissing .... For me those kind of infiltrations don't send email and don't have consequence for email reputation ...


cPanel do it for MySQL and DNS, now it's must be for Mail sended. :-)


Best regards.

photo
1

cPanel doesn't do anything with the MySQL.. It's just an external MySQL server they require.. Not a specific "MySQL Only" version :-)

photo
1

only email accounts migration without emails, for minimum time

photo
1

If they are to migrate existing e-mail accounts to a mail only server e-mails do need to be migrated too.


The migration process should first recreate the accounts then set the account to backup mx mode so all e-mails are forwarded and then rsync the existing e-ails

photo
1

For us it would be enough if the DNS-only version would support secondary MX functions, so only relay for the domains configured in cPanel.


In fact, the DNS-only version is used as a backup system for DNS. From that viewpoint email could be included.


In this case there is no need to sync user accounts, just rsync the secondarymx domain file. And of course the ability to install ASSP for cPanel so that the SPAM filtering will be done immediately on the secondary mx server.


And yes a Mail-only version would be nice also.

photo
1

I would prefer to keep mail server separate from DNS server from a security standpoint.

photo
1

I don't see any (new) security issues for combining the two. If so, they are are already existent in the main WHM product as that combines even more technology. And if there are issues, they can be addressed as long as they are openly discussed.


Can you please elaborate your security standpoint not to combine these two?

photo
1

I cant say if it is a security issue or not but I run 4 x dns only servers scattered throughout the world. These are small vps servers as they are dns only so dont need much power.


A mail server would need MUCH more power to handle all the complex tasks associated with email.


I think for simplicities sake, having a mail only server which handles only email, would keep things simple.

photo
1

I understand, but this FR is for a Mail-only server. So the feature in it self is prone to needing more CPU then DNS.


As far as I see it there are two uses for a Mail-only version:

A) Offloading Mail from primary cPanel server

B) creating a secondary/backup MX (similar to creating a secondary NS with DNS-only)

Usage case A) will take loads of extra effort not only developing but it will also take extra hardware. However the later should not be such a big issue as the reason to separate in this case will probably be due to performance issues anyway. WHM will have to interface with the Mail-only server regularly to sync domain and account information. And even mail itself if a cluster type of setup is possible/chosen.

Also in this case cPanel will have to think how licensing and/or support has to be fitted in their company structure for this product.

I think it would me most simple if in this case cPanel builds a modular install and makes a remote (internal) API to update all modules within a cluster. During install you chose if that server is going to be WHM master for a cluster, and what software modules you want installed (MySQL, Apache, NGIX, Dovecot, whatever...). For the first version each module only 1 can exist in the cluster as is now the case on a single server. For each major module you would have to pay a full license.


Usage case B) will take minimal effort to develop and maintain. The mailserver only needs to sync the domains to the secondary MX and maybe the accountnames to support ASSP or other anti-SPAM software to check if an account exists before accepting an email. No complex configuration is needed in this case. There will also be less serverload compared to case A). In most situations you will probably not need to upgrade your server if you combine it with DNS-only in this case as it will not process email the same way. Only accept and forward for existing domains/accounts.

photo
1

We would like to keep them seperate to keep them as stable as possible.

If a user starts sending Spam or a very large amount of e-mails or if the e-mail servers are brute forced it shouldn't impact the DNS servers.

Honestly if cost is an issue here, put DNS only servers on small VPS's with a small amount of disk space. ( a $5 VPS could be enough for each DNS only server).

For us seperating each service to individual servers is to increase stability and allow to setup backup and hardware solutions based on requirements of that functionality. E-mail is the usage that requires the most disk space and doesn't have frequent access to all of the files.

E-mail is the current reason why it's not yet viable for us to move to SSD only servers.

photo
1

It has been touched on by other responses already, but in short this is why I would make them separate services (not just security related):


1. For scaling I would like to separate services. I have mariaDB separate from WHM and standalone DNS servers. I'd like to have separate Email services as well.


2. Email requires more disk space than DNS.


3. Email by nature accepts files from outside users and stores them on the server. I'd prefer not to have those files accumulating on DNS only server. Some of the files may be malicious by nature, and while it would be difficult to act on those files, it is an unnecessary risk.


4. DNS can impact all clients within WHM clustering therefore it's crucial to stay online.


5. CPU/Memory/Storage requirements are different for the two services, as are the backup procedures. Easy to backup and replicate DNS only server with small footprint in virtual world than a big, bloated Email server.


6. Ports and firewall (hardware level) Keep them closed if not needed. Better to only allow DNS ports. Intrusion prevention is different for EMail vs. DNS packets, better to run specific algorithms for security and efficiency on the appropriate devices.

photo
1

@Andrew, your scaling reasons are clear and I totally agree. However on the security point you make, I think you are incorrect. Wether you combine the service on 1 server or not, you will still need security measures tailored for both specific services. Furthermore you introduce new risk if you say it should be done on a separate device separating it from the application. If security is an important issue for you, you should apply it on multiple levels and step away from the classic security in a box approach.

photo
1

But is there harm in applying security on multiple levels (which we do) and also segmenting the services on different virtual devices? I think by default, a separate vm with dns vs. email is more secure because if one is compromised it can be restored separately from the other without interruption of multiple services. Not sure that you have a full grasp of our approach, but I agree with your concept of thinking outside the classical approach.

photo
1

Although a lot of people forget, DNS is one of the most crucial services there is. Without DNS, your MX servers will not be found. With a failing DNS for whatever reason, your customers may not be found for days. So in that case other services will also be compromised.


Each service you run should be evaluated and risk should be mitigated according to your needed level. Segmentation of services will not change that.


Also backups nowadays don't prevent you from restoring just the files you need. So as long as you carefully think how you restore things, unaffected services will not have to be interrupted.


And last but not least, combining several services on a single server and keeping them manageable and safe has been the sole purpose of cPanel. I'm not saying that you do, but if someone in general questions the cPanel architecture for their purpose/situation, always re-evaluate if a different setup might be better for you.


If I had customers so big I needed to split services, I'd probably make enough money to built my own scripts and use Puppet and Chef replicate the mailserver config to a separate server.

photo
1

Although a lot of people forget, DNS is one of the most crucial services there is. Without DNS, your MX servers will not be found. With a failing DNS for whatever reason, your customers may not be found for days. So in that case other services will likely also be compromised. And for that to happen they don't even have to reside on the same server.


Each service you run should be evaluated and risk should be mitigated according to your needed level. Segmentation of services will not change that. Only in a select set of situations will the segregation provide added security.


Also backups nowadays don't prevent you from restoring just the files you need. So as long as you carefully think how you restore things, unaffected services will not have to be interrupted.


And last but not least, combining several services on a single server and keeping them manageable and safe has been the sole purpose of cPanel. I'm not saying that you do, but if someone in general questions the cPanel architecture for their purpose/situation, always re-evaluate if a different setup might be better for you.


If I had customers so big I needed to split services and if I still wanted cPanel to function as a customer controlpanel, I'd probably make enough money to build my own scripts and use tools such as Puppet and Chef to replicate the mailserver config to a (new) separate server.

photo
1

I also need cluster system for httpd and mysql load balance. As I know, cpanel has already provided DNS cluster.

photo
1

I think that there are already seperate feature requests for these. cPanel mail only for the mail part and there are multiple requests for httpd (load balancing and multiple httpd servers.


We want all of this too and are in the progress of doing the mailonly part manually with a full cPanel licence.

photo
2

We're in the process of testing a cPanel server that only does email.


The main issue we came accross was with DKIM as DKIM needs to edit the dns zone and we left the dns management on the web server.


As we use spamexperts we are going to test with their system signing the e-mails and adding the DKIM record to the dns template. We already do spf with an include in the dns template.


If this works we will have a working E-mail Only setup.


The issues that remain are :


You have to provide a seperate disk quota for e-mail uf cpanel could manage a total soft quota adding both servers it would be nice.

Dkim and spf require uncludes in the dns template and yoy can't have automatic dkim per domain.

Users have to have a seperate cPanel login, users should be able to login automaticaly to the email only server.


If we manage to make spamexperts sign all outgoing e-mails automaticaly we will move this setup to production.

photo
1

I think this would be very usefull. Fetching info over secure channel using Remote Access Key's would work pulling accounts BUT xfer when opening email account/webmail needs to be changed. If you setup WHM EmailOnly you could easily put in details into DNS because MX should be mail.domain.tld and that should point to your EmailOnly IP address. With DNS Cluster feature you could pull DNS record from WHM/cPanel server update it with DNS settings and sync back to WHM/cPanel server. After that you could use DNS Cluster to sync to the nameservers.

photo
1

I am actually all for this idea. Running a Zimbra or MSEX infrastructure can be rather costly.

photo
2

We're currently investingating Sogo.nu to see if it meets our needs while we're waiting for cPanel mail only and for cPanel to be more compatible with Outlook. We looked into Zimbra (non opensource) and OpenExchange and they were too expensive, we have a supplier that offers high availability 50GB exchange accounts for €2.99/month so we can't compete if we're paying $2 per user in software licence. Sogo uses standard software (dovecot, exim or postfix, apache or nginx) that needs to be configured before installing sogo. Sogo then sits on top and provides native exchange compatibility and a webmail that looks and acts like thunderbird with lightening.


We haven't had time to get all features running yet but we are prepared to pay for software like this but on a per server basis and no more than a full cPanel licences per year per server.


If sogo works out for us we'll be providing a per mail account pricing and not included in webhosting pricing. However with cPanel Mail only I presume both would become possible so we could choose between including XX mailboxs of XXGB each with a hosting account or say the XXGB if the hosting account includes e-mail space.


I was told by support that cPanel will soon be working on making e-mail more robust and looking into adding features like activesync. Fingers crossed !

photo
2

We've just had a customer request for hosting 200 mailboxes, each with 3 to 5 GB capacity requirement. It would be mad to host theses mailboxes on the same quota as the website but as we are using DNS Cluster on all of our cPanel servers we cannot create the e-mails on one server and the website on another.


In this situation we would rearly love to have an e-mail only server with the ability to set a limit for e-mails and a seperate limit for the website.

photo
1

I am in similar situation.


Currently I offer my clients external email service for 15eur per mailbox per year. They get 25GB email space for each email account. Its worked fine till now but if I could cluster some mail servers together I could offer similar service without having to rely on a thrid party provider.

photo
1

This would be good! Also should have support for multiple MX so you can create a email server cluster for redundancy.

photo
1

I have been trying to work out how to do this myself. Be great if it can be done. There are plugins for dns only that allow some of the functionaility already

photo
1

We treid but decided to wait.


You can do it with a normal cPanel licence by disabeling DKIM and having a the SPF record included in the dns template on the webserver.


We had a go at setting this up and got it working using spamexperts to add the DKIM for outgoing e-mail.

photo
2

@keith - I'm tempted to merge your feature request with https://features.cpanel.net/topic/mail-only-version-of-cpanel-whm - would that be reasonable?

photo
1

Sorry for the late response, Adam. That would be alright - but I would like to add that the webserver's cPanel should still be able to control the e-mail accounts for that domain on the seperated mail server.

photo
1

Wow. This is a solution I would pay extra for gladly. I don't operate a commercial hosting business but handle web and email for a small group of family, professionals / small businesses. Because I can't seem to adsorb all the good information about how to achieve the two server solution (I just can't get the reverse dns to work for luvnermuney), I ended up buying separate email services from a dedicated email provider. Adding this would complete the cPanel Universe of Web server, Email server and DNS server. Right now, one leg is missing from the stool and I keep falling over.

photo
2

This would be very nice, we use cPanel/WHM and cPanel DNSonly but also have the SMX plugin for backup MX on the DNS servers to give redundantie. It would be nice to have a cPanel MailOnly to extend redundantie and the SMX plugin is a good base for that server to connect to the main cPanel servers. See topic:


https://features.cpanel.net/topic/backup-mx-service-on-cpanel-dns-only


Perhaps cPanel DBonly version to make it even better? We are currently looking at a MySQL cluster setup to provide even more redundantie.


https://features.cpanel.net/topic/backup-mx-service-on-cpanel-dns-only

photo
2

We are plan to migrate to cPanel and a central mailserver cluster is an must have for us

photo
1

Our next cPanel server will be SSD only. We hope that we will be able to migrate email off this server to a mail only server at a later date.

photo
1

Having tried to get this working, here is what is currently missing :


DKIM and SPF need to be aware of the email only server and set their dns values accordingly.


Email needs to be managed in cPanel's user's account using cPanel api to create accounts on the remote server.


In packages we need to be able to set quota for email accounts and web accounts seperatly


We also need to be able to set the maximum size of an email account so webhosts can choose between limiting total disk space or just number of accounts.


Webmail redirects need to redirect to the email only server


And also please make this work so you can have one email only server used by multiple cpanel servers but also have multiple email only servers on a single cPanel server.

photo
1

In Repsonse to "monarobase" re the post starting with comments about DKIM and SPF need to be aware....


We are achieving all the things you are wanting inclding several web servers utilising the resources of one mail server.


It requires a bit of manual labour to set up the accounts and you need to make sure the DKIM signatures on the email server match the DKIM signatures in the DNS for each domain. Also you need to make sure you edit your zone templates correctly.


You can already set the maximum size of an email account. As far as quotas are concerned, we run one Package on the mailserver for a domain and a different Package on the Web server for the same domain.


Cheers

photo
1

For maximum'size of email account it would need to be per package.


We don't want to have a seperate control panel for email but for users to mange their accounts from their main cpanel account.


We also don't want to manually copy dkim data between servers. Users need to be able to create their own email accounts.


When we tried to set up what you did, we were unable to have both the ability to add new domains to an account while not having thing slike URL redirects.


We managed to set up a global DKIM record using spamexperts for outgoing email.


It almost worked for us but we still came to the conclusion it was too complicated for end users.


We'll soon be starting our next server configuration and hope that a mailonly version will be available within a year or so, so that we can move the e-mails to a server that only does this.

photo
1

Hmmm... over 3 years old idea, with obvious advantages, not actually hard to implement (specially if you have all the code)... and still nothing... I don't understand what's so much to discuss anymore about this request... Feels like no one from cPanel actually really cares or have any intention to make this request come real... Sorry, but I feel a big disappointment.

photo
2

I think they are defenetly interested in it as a member of their support told me to vote for this specific feature when I asked about adding more features to the cPanel e-mail system.


cPanel up to now only says a feature is planned when it's likely to appear in the next two or three versions.


Now 11.56 will soon make it to current, I do hope this feature will make it to the planned status.


This is our most important feature request.

photo
1

I hope to see a reply from @cpanelbenny :)

photo
3

We're definitely discussing this feature internally, and I'll get more information here soon!

photo
1

@cpanelbenny - That's great news. Is this similar to the Backup MX feature here? https://features.cpanel.net/topic/backup-mx-service-on-cpanel-dns-only


I would really like to add more redundancy to our cPanel servers and although the MX has been the first step with this we need more.

photo
1

No it's not the same. The idea here is to have a server for your e-mails and another server for your website, where as the backup mx server is just to store e-mails when your main server goes down so you can deliver them faster.


In other words you might want to have both, one mail only server and one backup mx server so that if the mail only server goes down, the mx backup server stores the e-mail while waiting for the mail only serveur to come back on line.

photo
1

It would quite nice if it would possible to build a server or cluster with cpanel to define 1 outgoing/incoming mailserver.


Example:


Company "Example" has 3 Server:


-srv1.example.com


-srv2.example.com


-srv3.example.com


I want use MAIL.EXAMPLE.COM for IMAP/POP3/SMTP (SSL and non SSL) for all our customers.


That would be nice

photo
2

We've said for a long time that this is a good idea. Mail servers have very different tuning requirements to Web servers. Being able to build a couple of decent mail servers (primary and backup) to serve multiple web servers would be perfect and provide a much more robust mail solution to end users.

photo
1

Not sure if cPanel really should do something like this... Are people thinking of this more of a central mail gateway, or just off-loading mail to a cluster? It really seems like it would depend on how many cPanel servers would be served,


A central cPanel mail cluster could be used to offload and centralize SpamAssasin filtering, and then deliver it to the cPanel servers. Outgoing mail could then be sent to the gateway cluster as a Smart Relay, and outgoing filtering would be done there.


One IMPORTANT thing to remember... No matter how this is implemented, it will add additional time and points of failure to email. If your clients are anything like ours, anything email not sent and received instantly is a problem on the server, and "You need to fix this ASAP, as I am loosing millions of dollars per second." *shakes head*


I'd be more worried about email blacklisting of IPs om such a mail cluster... I'd think we'd also need to implement an internal RBL to help try to prevent external blacklisting.

photo
1

I think what is being left out of this conversation is the fact that processing emails costs cpu, storage and bandwidth. The spam filtering, in and out is a little expensive at times and it can slow down other applications on the server. HOWEVER, the integrated management of email addresses/passwords and quotas and such is something we don't want to loose. I am currently running two cpanels, one for websites and one for emails and I have seen improvements in site performance. I have been playing around with some rsyncing but in the end it is still a lot of management for when you manage a hundred or more accounts.

photo
2

Hi Acenetgeorge,


That's not completely true what your stating. The maintenance of accounts of email can be done on the cPanel server which sends the commands to create/delete/edit/suspend the accounts. The DNS will handle all traffic so no change in that, RBL's can still be used. For outgoing email same server can be used and for outgoing email you can assign IP as current release supports dedicated IP's so on EmailOnly should be possible to.

Few advantages other other than OP are:

  1. Improve performance, use SSD's for webhosting and HDD's for email server (HDD is still cheaper).
  2. Attack platform minimizing.
  3. When rebooting a server email/web stays online.


We also use 2 backup servers for email now with SMX plugin in case we reboot or have maintenance on webhosting servers.

photo
1

Any update ?

photo
1

No update yet, but I'll definitely post one here as soon as we have one!

photo
1

I've read all the comments on here and I have my own to share. I'm basing my response on the following requirements...


  • Offload processing of inbound mail and anti spam.
  • Provide an "Email Only" service to customers.
  • Separate storage for Emails away from the /home partition.

The

first requirement is most often achieved with the use of an External MTA. We use SpamExperts as an inbound mail cluster and this takes all the load off the cpanel server for all inbound mail processing. There are already plenty of solutions for this. It seems what some people are asking for is a separate cpanel developed MTA. There really is no need to do this when there are open source and commercial options available already.

Providing an "Email Only" service is as simple as developing a new type of cpanel package that doesn't set up the vhost / FTP accounts etc, in order to prevent the customer from using the plan to host a website. You don't need a separate server for this. If such a package existed, if you really wanted, you could specify servers specifically for this purpose and not mix the Email only accounts with other servers. However, mixing them in with your main shared accounts also gives you an easier upgrade path for those who start out with email only and then want to upgrade their plan.

Separating storage for Emails away from the /home partition. This would be very useful, however, instead of creating a whole new server, wouldn't it be much easier to develop the current cpanel account creation to specify a different partition for email storage on a per user / package / server basis? That way you could add storage to a server specifically for mail, or use a network based storage type. This way you could make sure your high usage mail users were using a destination suitable to their requirements without filling up the /home partitions on your cpanel servers or using up your SSD storage. You could share this storage between servers, making it easier to move accounts around.

I think it would be a major advantage to be able to choose the mount point used for Email and the users home directory on a per user or package basis. In a virtualized environment, this would allow you to make a choice as to the type or quality of storage used for different levels of resilience on different packages.

If you create a new cpanel "mail only" server, you're not going to use an individual mail server for every cpanel server you have - that would be very expensive - so you'd end up bunching up hundreds, or thousands of customers email accounts from multiple shared servers into a small number of servers which you'd use for both inbound and outbound processing. This could result in the same storage difficulties you had in the first place and cause bottlenecks, blacklisting issues and other problems. Integrating it all with cpanel seamlessly? That's a huge undertaking. And you'd still need to keep a mail server running on each shared server for sending mail from scripts.

Having lots of shared servers performing their own outbound mail processing is a good thing. You share the load over all your servers and you're not putting all your eggs in one basket. The sending of mail from cpanel servers rarely causes any load issues or other resource problems, so why change this? For inbound clustering, you'd need to replicate all the "Email Only" servers to provide redundancy, which as mentioned at the start of my comments is already achievable with other products.

photo
2

Here are some advantages that you missed :


  • Ability to move a website to another server without moving e-mail
  • Ability to fill all disk slots on webserver with SSD's and fill all disk slots on email server with large hd's
  • Ability to have more visibility on what is using ressources
  • Ability to reduce backup window and restore times for websites
  • You don't use the same backup procedures with e-mail as with websites.


Our servers have 12 SSD's and we are unable to use more than 1/4 of CPU or ram ressources and can't add more ssd's.


Moving e-mail to seperate servers is one step further towards having all services on seperate servers and setting up a high availability solution.

photo
1

Let's have a look at your other "advantages"...

Ability to move a website to another server without moving e-mail.


This is already not an issue when using any external Email service. There are plenty of enterprise Email systems out there and plenty of free alternatives to using the cpanel server for Email. When you're using an external mail server, cpanel isn't handling the messaging, so when you move an account there isn't any Email to move. Why are you insisting that cpanel create a whole new external mail system for this? Why does your external mail server need to be made by cpanel? What you're asking for here can already be achieved by using any one of dozens or products that are already available.


I appreciate that it's a good idea in some situations to have all mail handled outside of the web server environment, but there are also plenty of situations where you'd want to keep things the way they are now. There are tons of people (not necessarily web hosts) using dedicated servers and VPS servers for running single websites, or small numbers of websites via cpanel and it would be unnecessary for them to set up a whole external mail environment. There are also lots of web hosts who already use external MTA' for inbound mail and would not want to change this. So if you are suggesting that cpanel move to separating out the Email functionality of their product to an external appliance, without also allowing an option to keep things the way they are currently, this would cause some problems for a large number of cpanel customers. Also, for pre-existing large scale shared hosting environments, the disruption caused by making such drastic changes would be significant and expensive.


I think it would be a really good idea to have the ability to store messages on a separate file system, but that doesn't mean it needs to be a completely separate mail system. If the cpanel infrastructure was modified slightly to allow for mail to be stored on a different location other than in the /home partition, you could then set the /mail location on a per user basis, so when backing up an account or transferring an account, you could choose not to backup or move mail, but keep the location intact. For example, Instead of having /home/username/mail/domain/cur you could have /mail/username/domain/cur and in a virtualised environment or with shared storage, this location would be available to a number of servers within which you could move your accounts around without having to move mail. I'm thinking small groups of servers sharing storage pools in a high availability setup. You could specify a fast SSD array for /home and a large, slower one for /mail. Makes sense to me.


Ability to fill all disk slots on webserver with SSD's and fill all disk slots on email server with large hd's


These requirements are personal to you and seem to be quite immediate. You're suggesting that the future of web hosting is a static situation where you are running a large number of low capacity SSD's on your single web servers without any virtualisation or other types of storage in the environment. While this might be your situation right now, this is not the way things are heading my friend.


For a start, SSD pricing will come down and capacity will go up - possibly well before cpanel could develop a whole new fully featured and integrated mail appliance. But you're living in the dark ages here. The trend is towards separating processing from storage and using virtualisation to achieve the kind of scalability and mixed storage you're looking for. Most major hosting businesses are already running their cpanel servers from some form of cloud based platform, where different types of storage are available. I agree that it would be a huge advantage to store Email away from the /home partition and that's really just a case of changing the file structure slightly to create a /mail partition that you can store anywhere you like, as mentioned above.


It also must be said that in a single server setup it's pretty easy to mix 2.5 and 3.5 inch drives as long as you choose the right chassis and use adapters in your 3.5 inch bays for the smaller drives. We do this in some of our servers. If cpanel developed their product so that you could specify the location for mail to be stored, in a single server setup, you could easily run your /home partition from one set of drives and your /mail partition from another. That would solve your storage problem.


Ability to have more visibility on what is using ressources


I'm not sure what you're getting at here. It isn't difficult on a Linux server to determine resource usage. I think you may be having a problem with your servers being overloaded, due to mail processing, which might indicate that you're putting large numbers of users on your servers and using each server to process inbound messaging. This really just means that you're not balancing your servers correctly. You should either reduce the number of accounts on your servers, or use external MTA's to process your mail before sending it to your cpanel servers.


Ability to reduce backup window and restore times for websites. You don't use the same backup procedures with e-mail as with websites.


I'm sorry to criticise, but this again is just down to the way in which you are running your servers. If you have too many accounts on your servers with a large amount or stored mail, then you should be reducing the number of accounts and using a good incremental backup solution, where only new mail is backed up. If you are doing a full cpanel backup that is taking hours and hours, you should consider changing your backup strategy. Do you think that backing up a very large external MTA with terabytes of messages will be easier?


Our servers have 12 SSD's and we are unable to use more than 1/4 of CPU or ram ressources and can't add more ssd


That's not really cpanel's problem. You can't ask them to change their whole Email infrastructure just because you don't know how to properly configure and balance your servers.


Moving e-mail to seperate servers is one step further towards having all

services on seperate servers and setting up a high availability

solution.


I wouldn't suggest that it's a good idea to have all services on separate servers. High availability would not be achieved by shoving all your Email processing and Email accounts onto a smaller number of standalone servers.


This is all about the environment you choose, how you configure that environment and the types of storage you choose. In it's most basic form, using external mail servers to support your single server web servers will not provide you with better resiliency / availability. It would solve your storage problem, but that's about it. As I've said, there are already plenty of external email solutions available, should you choose not to use the Email system provided on a cpanel server.


I think if cpanel really want to create an Email Only solution, they should consider very carefully keeping the current functionality available to those who need it.

photo
3

Hello,


Most of your points seem to be based on the fact that you don't want to have to do this. Don't worry cPanel will never remove the ability to have e-mail on the same server as the website. Most of their VPS users and alot of their dedicated server users need this.


This feature request isn't to remove the ability to have e-mail on the same server as the website hosting server but just like with DNSOnly you will be able to choose if e-mail accounts are to be created on a local server or on a remote server.


With our current setup about 60% of files are e-mails. E-mails require alot of disk space and very little server resssources while websites tend to require little web space and alot of server ressources. For hosts with large, custom servers it doesn't make sense to have e-mail and websites on the same server.


It's also not a matter of putting too many accounts on a server but of having the fastest possible backup windows and restore times. If you have 5 GB of websites on a server and 100 GB of e-mail on that server, it's not overloaded my most webhost's point of view, but restoring 5GB will be much faster than restoring 105 GB so a webhost could achive a much better uptime with only 5GB than with 105GB to restore.


E-mail restores can be managed differently than website restores, you could for instance restore all the e-mail accounts without the e-mails and then restore the e-mails, most users worry most about recieving new e-mails and and won't mind waiting a few extra hours to get their old e-mails back.

photo
3

keeping the current functionality available to those who need it

Agreed: There's nothing to say this feature is at the expense of the current all-in-one setup.

Chris, what existing systems are you referring to that allow a hosting customer to open one cPanel and administer both website and mail across several domains with the same hosting provider? And with the reliability, support and price-point that cPanel offers?

photo
1

"With our current setup about 60% of files are e-mails. E-mails

require alot of disk space and very little server resssources while

websites tend to require little web space and alot of server ressources.

For hosts with large, custom servers it doesn't make sense to have

e-mail and websites on the same server."


The way you are talking about your current situation in this feature request is as though you are stuck in a problem that can only be resolved by cpanel producing an Email only solution. It's as if you are saying you have reached the limitations of the cpanel software and you need them to help you resolve that.

Unfortunately, you've caused your own problem here. If you are mainly providing email services and the majority of your storage is used for email - why did you set up your servers in a way that isn't appropriate for that kind of usage? Perhaps you shouldn't be using cpanel at all?

You said before that you are using 12 SSD drives in a server and you're running out of space because of the volume of Email. This means you didn't build your server correctly for the way you intended to use it. If you built a powerful multi processor server with lots of RAM, then added only a small amount of storage, it's pretty obvious that you wasted your money. If you're going to use single servers with local storage, you'd have been better with a larger volume of less powerful servers and spreading your storage over those. After all, you didn't plan for using an external MTA - or to use a cpanel Email only solution before you built your servers, so the predicament you are in is your own doing due to poor planning. You seem to be suggesting that you need an "Email only" option to resolve these "problems" - but you wouldn't have any problems if you'd designed your infrastructure correctly in the first place.

"It's also not a matter of

putting too many accounts on a server but of having the fastest

possible backup windows and restore times. If you have 5 GB of websites

on a server and 100 GB of e-mail on that server, it's not overloaded my

most webhost's point of view, but restoring 5GB will be much faster than

restoring 105 GB so a webhost could achive a much better uptime with

only 5GB than with 105GB to restore"

This simply means that you've made a bad decision in choosing your backup strategy. There are dozens of ways to backup a cpanel server and even more ways to backup individual websites. Again, this is the result of poor planning. The limitations of cpanel's backup system are well known and well discussed. If you choose to use a solution that is inadequate for your needs, there's no point complaining about it here.

"E-mail restores can be

managed differently than website restores, you could for instance

restore all the e-mail accounts without the e-mails and then restore the

e-mails, most users worry most about recieving new e-mails and and

won't mind waiting a few extra hours to get their old e-mails back."

Again, this is related to your choice of backup solution. If you want cpanel to change their backup process to handle Emails differently, then you'd need to raise a new feature request for that.

It's like you are saying you didn't know what you were getting yourself into before you started using cpanel and now it doesn't work for you the way you want it to. Creating an "Email Only" cpanel server would likely take years to develop - so that isn't going to help you in the short term.

It's clear that I don't like the idea of an "Email Only" solution, but until now I've mainly been directly criticising "monarobase" 's reasons for justifying it due to his own needs. I appreciate that there is a general issue with storage, but you've made that much worse for yourself than it needs to be and "the storage issue" won't necessarily be resolved by moving messages to an external, cut down cpanel server that contains bigger hd's.

Here are my other comments on why I think it's a bad idea...

From my point of view, the two main issues facing a web host when it comes to email are firstly resource usage relating to inbound processing / anti spam - and secondly IMAP storage, which is becoming an increasing requirement.

As a provider, once you reach a certain number of customers, there becomes the need to handle inbound messaging differently. I'd say most medium sized web hosts are now using a number of external MTA's to process inbound messages and to offload their spam and virus checking. It should be said that most (but not all) of these services are at a premium, but the cost is easily justified. Using SpamExperts as an example, their service is so good that you see a very low number of false positives. This is down to their attention to detail and constant updates and analysis of trends etc. When you are paying for a service like that, you are getting a fully featured and well developed, mature service. That's something I guarantee you won't get with a cpanel developed "Email Only" server.

What you are most likely to get is another cpanel server that has been modified to just handle messaging. Personally, that wouldn't be good enough. 80% of all Email is spam. Another reason for us moving inbound mail processing away from the cpanel server was the poor quality of SpamAssassin and other free anti spam solutions. With cpanel's Email only solution, you would need to spend considerable time modifying it and updating and dealing with false positives and support tickets.

I think if cpanel were to develop this, most hosts that are already using external appliances or services for inbound processing would be likely to stick with their current solution for that - so an Email Only server would require the option to configure it in different "modes".

The system would also need to be clustered (esay to achieve with round robin DNS) and if it is storing all your customers email too, it would need to be replicated. If you lost a whole server, restoring such a large amount of data would take too long, so you'd need to add a degree of redundancy and failover. That's again a huge undertaking outside of a cloud infrastructure and it would need to be done right. Then there's the issue of backups. It has already been mentioned that backing up a single server with a large volume of Email is a costly and time consuming process. If you intend to host large numbers of Email accounts on an external MTA that will handle inbound processing, POP/ IMAP mail collection, SMTP and dozens of terabytes of storage, then also replicate it and back it up, outside of a virtualised infrastructure, then you're going to need a very large and heavy backup solution that will allow for the restore of messages for your clients. All these things start to make this financially very costly too. We are also talking about a massive amount of development time here to do what in reality has only the effect of simply to moving your IMAP storage to an external server. It's not worth it.

So I think we reach an impass there. The issue of storage is really a question about whether or not you choose to virtualise and use network storage. All of this discussion ignores the fact that "the storage problem" doesn't really exist if you have the ability to expand your capacity whenever you want to and to mix different types of storage for different needs.

The question isn't really about whether to spend thousands of development hours on an external cpanel Email only solution - it is whether or not to introduce a high availability, clustered environment into your hosting infrastructure. It would be great if cpanel could develop that - instead of continuing down this "standalone" server route that is going nowhere.

More points... Personally, I don't like the idea of bunching up all my clients into a smaller number of mail servers. I'm happy with the way outbound processing works with cpanel currently and I like the fact that my clients outbound messaging is spread over a large number if IP's. It only takes one compromised Email password to get an Email server blocked for several days. That's fine for Hotmail and Gmail - they have hundreds of mail servers to get around problems like that, but if you are only using a couple of servers for the outbound processing of thousands of domains, you're asking for trouble. In general, shared hosting is about high volume, so you want to maintain a high level of service to a large number of clients. Spreading those clients widely over lots of servers that are processing smaller volumes of mail is better

With the current setup, it's easy to monitor mail queues, authrelay trends and outbound volumes - you get to know and understand your servers and the types of users that are on them. It makes log analysis easy and helps to balance servers and serve the clients better. If you move all your clients to a small number of servers that are processing large volumes of email, you lose that ability and I can guarantee you would have more problems. One small issue could easily result in very large numbers of phone calls and support tickets. I believe that using individual cpanel servers for messaging is an advantage, not a disadvantage. The only issue, as described above is storage.

Everyone is moving towards a more resilient, scaleable architecture and this doesn't need to be a large and expensive cloud deployment. Small clusters of web servers that can share load, storage and failover to each other is the way to go in my opinion. This can already be achieved - but cpanel needs to move with the times and make their product more friendly towards that kind of infrastructure, or develop their own.

The ability to cluster cpanel servers and separate out the storage of databases, Email and home directories is the key to solving the storage issue described in this feature request. In particular, as I've suggested - moving the storage of mail outside of the /home directory would be an important start for both local and cloud infrastructures . I think developing an "Email Only" server would be a wasteful distraction for the cpanel developers when there are more important features to consider.

photo
1

So the Solution is "buy something else"? We're in 2016, panels and hosting industry are moving in a decentrated reality; a server for files, one for emails, one for webserver, etc. If a server fail only that service will stop.


all services in one server is an old and obsolete vision of hosting. The solution is not say "ehi, this is the situation. Accept that or go somewhere else". You pay others for some services and we want to use cpanel.

Tell me: if your idea is the right way, why they spent money to create and maintain a DNS ONLY edition? There are a lot of services for dns, right?

Developing more versions will make the software light, more flexible, scalable.

photo
3

Chris,

This is getting completly off topic. Your assumptions about us are wrong and have nothing to do in the feature request section. Repeating myself here, this feature is not to remove any existing functionality so should be of no concern to those who don't need it. As of the importance of this request , that's what the voting system is for.

photo
2

Hi, I know what we we're looking for, and possibly other users are in the same boat.


So, currently you are running WHM and sell cPanel accounts to customers. The customer goes to their cPanel account and adds an email address. That email is currently stored on the same server as the hosted web data.


It'd be great if you could apportion the email accounts to a seperate server which could offer a much larger storage capacity at a cheaper price than the main, faster, web server.


If there was some kind of "email only" software facility, or additional WHM configuration option, that would allow the email addresses created inside the customer's one and only cPanel account to be automatically facilitated onto the remote mail server that would really serve our purpose.


What do you reckon?

photo
2

My 2 cents. Some are already mentioned before but to create a full list.


Advantage:

  1. No 3rt-party email service and ability to create email-only account away from main webhost server.
  2. Faster backups and restore processes. Email accounts are most of the time very big (we host mainly for businesses).
  3. Email keeps running when in event of rebooting webhost server. Asside from Secondary MX we already use people can't actually access their email.
  4. Option to use HDD's with large storage for Email-Only server which is cheaper, and smaller storage amount with SSD's for webhost server which is faster.
  5. Better redundancy when server crashes. Recover of only email or only webhost is faster than both.
  6. Seperated servers for web, email, database and dns would almost be an high-available setup. Only need to do MySQL-Cluster yourself, high-available webserver is also another feature request which is worked on/in the pipeline, Email high availability is harder. What more would you like on hosting platform.


@Chris: Everybody has it's own reasons to have a request. Everybody is entitled to do so. Instead of bashing somebody please give good arguments to support this feature request or just ignore this one. We are a small webhost but don't want to rely on 3rth-party like SpamExperts (we are an reseller) or other. This feature request is intended to see how many people would like an Email-Only and from our point of view (and apperantly other too) it would be a huge contribution how to extend and improve the cPanel hosting community.

photo
1

4. Is already possible as you can determine the home location per user, even from within WHM. Though an option to set the default per package would be useful in this case.

5. I don't believe recovery times would differ as it depends on the home directory size.

6. Separate servers are nowhere near HA as you have multiple SPOF's (web relies on dns and database, email relies on dns). For a small set-up it would be useless and cost a bunch. Real HA would be even more expensive.


Al this aside what's the problem with running a second server with full-blown WHM/cPanel and slim it down? You can just disable Apache / MySQL and modify the features for your packages to only include e-mail related things. This is essentially what a e-mail only cPanel would ook like right?

photo
1

@chris, do you represent cpanel? I sure hope not. I would hate to think an organization as firmly planted in the industry would be making arguments against providing features that are in line with the direction the idustry in general is heading. If you dont hurry with a feature like this, so.wine else is going to build a webhost manager that will support diversified resources. I know I have already started to develop as much of storage a possible with s3, I have also set up a second server for a second whm for email only. It is necessary to provide proper resources to my sites. It also is cumbersome and inspires improvement. I'd love for cpanel to be the software to provide it.

photo
2

If you dont hurry with a feature like this, some one else is going to build a webhost manager that will support diversified resources. I know I have already started to develop as much of storage a possible with s3, I have also set up a second server for a second whm for email only. It is necessary to provide proper resources to my sites. It also is cumbersome and inspires improvement. I'd love for cpanel to be the software to provide it.

photo
2

This already exists but doesn't come close to cPanel on other aspects :)

photo
2

DDoS is a very real threat this year, and has been increasingly so for the last few years.


As soon as a mail-only verison of cPanel is available and works within cPanel for customers managing their own mail accounts, etc, we'll be able to move web server IPs 100% behind DDoS protected proxy servers, at a very low cost and with other benefits as well (including globalisation and SSL).


We'll be a lot more comfortable with no web server IPs exposed, only mail IPs exposed. It's not anywhere near as much fun (no notoriety) for a DDoS attack to take a mail server offline...

photo
2

Hey folks! This is definitely more chatter than we've seen here in quite a while. While I do want to allow debate, I'd much rather not have this much conversation on such a highly-voted feature, in the interest of it becoming too noisy. If you'd like to continue this conversation, definitely do take it to the forums! I'll go ahead and close the comments here for a bit, just to make sure.

photo
7

Hey all! Just a quick update here: We're moving incrementally closer to being able to build a MailOnly version of cPanel & WHM that we would be willing to put out into the world. The biggest hinderance has been doing this in a way that was maintainable and practical. The hurdle that we're hoping to get over in version 68 is adding permissions to the new API Tokens that were introduced in version 64. As we get closer, I'll be back with more information. In the meantime, feel free to reach out if you have questions: benny@cpanel.net.

photo
6

Hey folks! This request has moved from the discussion stage into the research stage. One of our development teams is doing research on the various ways that this might work, how it could be delivered, and distilling those ideas into what a beta or first version might look like. Thanks for your continued patience, and let me know if you have questions!

photo
5

As we mentioned on the blog last week, this feature is now in progress. The team has merged Phase one in to cPanel & WHM Version 76, which is just standalone Nodes. The current timeline with this one (with the normal "there are still lots of moving parts" caveats):

Phase one (76)

Introduce MailNode


  • allow brand new "MailNode" servers to be built, not conversions, and no connections to other servers.

Phase two (78)

  • Add the ability to link two servers, only when building the servers brand new

Phase three (80?) & four (82?)

  • Various iterations of migrations

To avoid spamming all 800 subscribers with followup comments, I'm going to keep them locked here, but if you have questions not answered here or on the blog, feel free to reach out to me directly or to the community team.

After the cPanel conference (which is just 8 days away!) we'll have more information coming out on the blog to discuss our plans, and what feedback we need from our users. For now, feel free to install the EDGE version of cPanel & WHM 76. If you are interested in testing MailNode in a production environment (as a brand new server) as Version 76 moves to the production tiers next month, and need a development license, feel free to reach out to your account manager (if you're a partner) or to me! Expect another update from me here in early 2019, if not before.

photo
4

Back with an update! Version 76 has just hit the CURRENT tier, which includes the new Server Roles features. One adjustment does need to be made to our expected schedule: Version 78 for this project has pivoted to be nearly entirely about improving email deliverability and consistency. Linking two servers is expected to be pushed to version 80.

If you have any questions in the meantime, you know how to find me.

Comments have been locked on this page!