An implementation similar to how ConfigServer MailManage handles things would be nice to be built in, where it lists all domains and you can specify the emails/hour per domain instead of per account (or optionally one or the other).
An implementation similar to how ConfigServer MailManage handles things would be nice to be built in, where it lists all domains and you can specify the emails/hour per domain instead of per account (or optionally one or the other).
I would like to be able to limit the amount of e-mails relayed hourly, by package, rather than by user.
For example, I have a free trial package, which obviously attracts spammers. So if I could limit the amount of emails that particular package can send per hour (25/50 etc) so that "free" users cannot send 250 emails per hour like the other packages can
+1 for this.
It is an interesting feature to help limit abuse possibilities right from the package itself.
+111
<forums.cpanel.net>
The message you have entered is too short. Please lengthen your message to at least 10 characters.
At the moment we have to manually remember which plans have more e-mails and change their limits manually. I do not understand why this was not implemented when it was added to the 'modify accounts' form. It seems to be the only option in the whole form that cannot be set in the packages.
No matter the amount of email accounts set in a domain, they may abuse even if only one email address is configured. In the other hand restricting sending limits by package might harm users with legitimate mail lists. How to reconcile these two aspects of the restriction?
+1 for this. It would be nice to be able to set that limit in the package configuration.
Thus, forcing those who want to have an even small list with frequent messages to upgrade to a different package... Maybe, I don't know. The restrictions are necessary. Cloning packages to accomodate those account upgrades seems to be the better choice. You will need a second version of every package to allow mailing lists by amount of lists and measured volume (hourly limit).
Thus, forcing those who want to have an even small list with frequent messages to upgrade to a different package... Maybe, I don't know. The restrictions are necessary. Cloning packages to accomodate those account upgrades seems to be the better choice. You will need a second version of every package to allow mailing lists by amount of lists and measured volume (hourly limit).
We already have a server limit value and can set limits on a per account basis. If you have your per address server limit set to unlimited then you won't be concerned by the ability to set per package.
It seems obvious that one of the options should be to allow the default server setting so that we can manage all the main accounts from the same place and just be able to create some "special" accounts by attributing them a specific email package.
The reason why we set e-mail limits is that the more email the server sends the more likely it is to be listed on spam blacklists and the more work hosts have to do to make sure the server is not blacklisted.
I think it is up to each host to choose if they want to include unlimited emails and spread the unblacklisting time between all customers or if customers who do not need this should have to pay for it.
Also, cPanel will soon have email statistics for users, this will hopefully show them exactly how many emails they send so they can see if they need to request an increase or not.
Beginning with 11.31.1.4, you can specify in a package how many emails/hour a domain can send. To see if this version has propagated to your update tier yet, visit Downloads - cPanel Inc.
Would like to see this as a package limit as well.
Would like to be able to mail limits to 0/h (or close to) for free trial accounts.
I'm not sure I have completely understood your request. Is this what you are looking for :
http://forums.cpanel.net/f145/limit-...id=propagating
WHM already has a UI to change account limits and also already has limits per package in the Edge version that will soon propagate to Current then Release and Stable
This is a duplicate of the thread monarobase mentioned, so I am merging the two threads.