How are you planning on deploying email now that quotas are available?

mendozal

Up until now, there wasn't a way to limit global email usage to the package's disk quota. I always wanted to let customers choose their mailboxes sizes but hard limit them to that value.

But now that this feature has been released:

All mailboxes now belong to the website user. Hard disk quotas configured at a website level will apply to the emails when the application role and email role are placed on the same server.

Are you planning on bringing email to the application servers or just leaving them where they are? Or is this ability not important to your use cases?

XN-Matt

Depends if you keep email on the same server. Just for the record, we're still wanting/needing a way to better police disk usage when the mailboxes and web are not on the same server!

josedieguez

Enhance is loosing what makes it different than other panels.

"when the application role and email role are placed on the same server."

this takes the big advantages of having email role on a different server, forcing you to have email on the same server, or else you won't be able to hard limit (wich is a basic and fundamental feature that Enhance lacks still).

same as the S3 Limited compatibility without incremental. it's a feature that nobody will use since was launched limited as base.

Isaia-Arknet_PTY_LTD

A hard limit was is not a necessity, the bigger problem is that there are no proper actions when reaching a SET limit, regardless if it is Hosting storage or eMail storage.

The more important feature would be the ability to set limits on the hosting or email accounts once the SET limit is reached.

an example would be, limiting the upload function when the hosting storage limit is reached,
limiting email functionality when the email storage limit is reached

It's probably not best to stop email functionality if the HARD limit is reached. (It would work, but the punishment would probably be too great.)

Also, it is important to have the ability to send warnings when storage is 80 90 %, etc., to be able to send an email to upsell the product. And allow the user to upgrade or fix the issue (remove some data)

These is just a few very basic needs, I am sure others would come and want a lot more and with much more detail. 🙂

slimx

Yeah but the POINT of the hard limit is so that the action of STOPPING functionality is taken.

I personally prefer to keep email servers separate from web servers.
For compelx websites i even have the DB separated 🙂 and it works great, this is the whole reason i chose Enhance.

Isaia-Arknet_PTY_LTD Also, it is important to have the ability to send warnings when storage is 80 90 %, etc., to be able to send an email to upsell the product. And allow the user to upgrade or fix the issue (remove some data)
This would be sooooo goood.

8Dweb

I agree with much of what is said. I have no plan to bring email services for a domain back onto the web-hosting server. This is one of the primary reasons we decided to take a chance on Enhance last year. I wanted something similar to what I had with Interworx years ago, or with our customized setup, where mail services/delivery were running on separate hardware/vm. Enhance is the first platform that makes this process simple. We used Plesk Expand many years ago, until they dead-ended and dumped it. We then utilized Interworx until some major changes happened with programmers, and the project nearly stalled for several years. We then moved back to Plesk and used separate SmarterMail servers... but management for that, as well as big-time costs for SmarterMail in excess of 1K email boxes made us move mail back to the Plesk servers... which in turn created new headaches.

The way Enhance allows us to separate services and easily manage it from a centralized control server is exactly what we needed. Now, the mail was barely rudimentary at that time. It is getting better, but eventually we will need queue management (I know, on the roadmap); mail logs in the interface (sorry, I am tired of logging into each mail server over and over), real rock solid mail quota management for mail on remove servers... SIMPLE spam management for end users/resellers.

So, it is going to be important that at some point the Enhance team allow us to set hard limits on mail storage on the dedicated mail servers. Right now, we do a rather manual process each month, but since we are a more boutique offering, we do not have the volume of customers many of your companies may require. I cannot imagine trying to do this with thousands of customers x however many mailboxes each may have.

It is workable at our customer load, but not indefinitely.

Also, side note, we never allow our customers to use mail delivery that is not authenticated for their various web forms/delivery. We stopped that stupidity 20 years ago. Yes, some customers who have used go daddy level hosting complain when they first come on-board, but I am not letting a hacked/improperly setup web form to blindly send email through phpmail without any real checks an balances. I realize not every host wants it that way, but I want a sure-fire log showing authentication, and mail delivery data so we can clamp down or fix problem much more easily.

This also makes it easy to clamp # emails per hour on domains relative to that customer's needs.