I think that the subscription should make sure that the client has the data limit, i.e. clients emails, databases, application, etc. As mike has mentioned, the subscription should cover the entire quota, and not different quotas for different roles.

As providers, it will be impossible for us to keep an eye on everything.

For those who are hosting email on a separate server, they can limit the mailboxes to a limited size.

    the package or suscription space limit should be web files, database and mail data, all under the one single limit.

    In my opinion, not the limiting is the issue but the reporting and actioning of the outcome (going over quota on all services)

    In order I think what is needed is:

    1. Counting total storage - files (all folders from "/of account, not just public_html) + Mysql + Emails
      (this needs to be done in a reliable way) can not be too hard, a little corn to collect this data going in the background few times a day.
    2. A page where we can see (the aggregated data) and filter all accounts accordingly (be able to see) what's over etc.
      3 . Ability for punishment (in settings, we should be able to setup automation like (if the account is over quota: Stop email service, block uploads, or whatever is suitable to make the client clean up the account or upgrade))
      Google does it for emails, and others do it. It must work!
    3. Ability to easily upgrade the account (as a client) (this is already working)

    Maybe I missed something 🙂 But I guess, as a minimum, if the above is implemented, to some extent, we all would have a lot less work.

      Isaia-Arknet_PTY_LTD I agree with you.

      I'd like to be able to sell 20, 30 gigs and give clients free reign over that storage space for anything they want to do (emails, databases, files), and have enhance enforce that.

        a month later

        I have a client with a three gb Website size and 185gb e-mails. (around ten mailboxes).
        I am charging him for the total size. (Website + emails)
        It's important to count mailbox size and website(account size) even if they are not on the same server. (even without active hard limits for the mail but showing notification or the total size) Or, in the future, to count the total size if we have all of them on the same server.

        +1 to a lonnnnng term roadmap of cross server subsciption sync of size limits. Nice to have, but difficult to implement.

        22 days later

        I spoke to Adam about this recently via ticket. It was mentioned that if you use a fixed mailbox size the space isn't included in the website quota however if you use "dynamic" instead it would be counted towards the quota, so it would include emails, files and the database.

        Maybe @Adam can confirm that's correct?

        Write a Reply...
        Follow @enhancecp