Hello.
We need cluster system for all services (web, mail, dns...).
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
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
Phase two (78)
Phase three (80?) & four (82?)
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.
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
Phase two (78)
Phase three (80?) & four (82?)
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.
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.
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.
I'd be happy with the creation of "email only" accounts, that allowed no FTP/File access at all.
I'd be happy with the creation of "email only" accounts, that allowed no FTP/File access at all.
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.
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.
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.
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.
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?
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?
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! =)
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! =)
This would be great, now we can separate mysql and dns services, it would be great if we can separate also mail services!
This would be great, now we can separate mysql and dns services, it would be great if we can separate also mail services!
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.
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.
This can be solved with the "Centralized Server Management" or "cPanel Cloud Engine"
http://features.cpanel.net/responses/as-a-hosting-provider-i-want-centralized-server-management-so-that-i-can-control-many-servers-from-one-main-server
This can be solved with the "Centralized Server Management" or "cPanel Cloud Engine"
http://features.cpanel.net/responses/as-a-hosting-provider-i-want-centralized-server-management-so-that-i-can-control-many-servers-from-one-main-server
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.
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.
I will love this feature, with this i will able to offer to my client reliable email server
I will love this feature, with this i will able to offer to my client reliable email server
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.
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.
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).
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).
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.
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.
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.
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.
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.
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.
I would love to see this option even if it where only available as a separate service on an additional server.
I would love to see this option even if it where only available as a separate service on an additional server.
Any updates on this request? cPanel please update now!
Any updates on this request? cPanel please update now!
Yes, it would be nice for sure!
Please cPanel, what about doing it?
Yes, it would be nice for sure!
Please cPanel, what about doing it?
This would allow us to open up an entirely new niche hosting business (and service).
This would allow us to open up an entirely new niche hosting business (and service).
I was thinking about this a few years ago. Glad to see I'm not the only one thinking this is a MUST HAVE
I was thinking about this a few years ago. Glad to see I'm not the only one thinking this is a MUST HAVE
Hello, any news? We've dns servers basically unused, and it's great if we can add email service to dns only servers
Hello, any news? We've dns servers basically unused, and it's great if we can add email service to dns only servers
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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
This will be a very good feature to have .. Save a lot of time and support requests ...
This will be a very good feature to have .. Save a lot of time and support requests ...
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.
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.
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 :)
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 :)
I actually agree with this.
Having another mail server would be great for people who rely on e-mails in their daily productive lives.
I actually agree with this.
Having another mail server would be great for people who rely on e-mails in their daily productive lives.
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.
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.
This feature would be really important! Make us happy cPanel! ;]
This feature would be really important! Make us happy cPanel! ;]
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?
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?
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.
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.
Yes please.
Heck, even ask a small fee for it ($5 seems reasonable) if required. :)
Yes please.
Heck, even ask a small fee for it ($5 seems reasonable) if required. :)
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.
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.
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.
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.
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.
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.
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
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
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.
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.
pleases have this feature you can charge me 5$ each license both dedicated or vps server.
pleases have this feature you can charge me 5$ each license both dedicated or vps server.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
cPanel doesn't do anything with the MySQL.. It's just an external MySQL server they require.. Not a specific "MySQL Only" version :-)
cPanel doesn't do anything with the MySQL.. It's just an external MySQL server they require.. Not a specific "MySQL Only" version :-)
only email accounts migration without emails, for minimum time
only email accounts migration without emails, for minimum time
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
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
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.
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.
I would prefer to keep mail server separate from DNS server from a security standpoint.
I would prefer to keep mail server separate from DNS server from a security standpoint.
I also need cluster system for httpd and mysql load balance. As I know, cpanel has already provided DNS cluster.
I also need cluster system for httpd and mysql load balance. As I know, cpanel has already provided DNS cluster.
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.
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.
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.
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.
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.
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.
I am actually all for this idea. Running a Zimbra or MSEX infrastructure can be rather costly.
I am actually all for this idea. Running a Zimbra or MSEX infrastructure can be rather costly.
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 !
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 !
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.
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.
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.
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.
This would be good! Also should have support for multiple MX so you can create a email server cluster for redundancy.
This would be good! Also should have support for multiple MX so you can create a email server cluster for redundancy.
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
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
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.
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.
@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?
@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?
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.
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.
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.
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.
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
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
We are plan to migrate to cPanel and a central mailserver cluster is an must have for us
We are plan to migrate to cPanel and a central mailserver cluster is an must have for us
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.
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.
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.
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.
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
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
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.
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.
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.
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.
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.
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.
I hope to see a reply from @cpanelbenny :)
I hope to see a reply from @cpanelbenny :)
We're definitely discussing this feature internally, and I'll get more information here soon!
We're definitely discussing this feature internally, and I'll get more information here soon!
@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.
@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.
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.
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.
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
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
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.
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.
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.
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.
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.
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.
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:
We also use 2 backup servers for email now with SMX plugin in case we reboot or have maintenance on webhosting servers.
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:
We also use 2 backup servers for email now with SMX plugin in case we reboot or have maintenance on webhosting servers.
Any update ?
Any update ?
I've read all the comments on here and I have my own to share. I'm basing my response on the following requirements...
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.
I've read all the comments on here and I have my own to share. I'm basing my response on the following requirements...
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.
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?
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?
My 2 cents. Some are already mentioned before but to create a full list.
Advantage:
@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.
My 2 cents. Some are already mentioned before but to create a full list.
Advantage:
@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.
@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.
@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.
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.
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.
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...
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...
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.
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.
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.
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.
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!
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!
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
Phase two (78)
Phase three (80?) & four (82?)
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.
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
Phase two (78)
Phase three (80?) & four (82?)
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.
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.
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.
Replies have been locked on this page!