Our features site is undergoing a refresh! Be sure to explore the revamped site and discover our latest product roadmap launching here on Monday, March 18th.

Mail sending limits per email account (rather than per domain)

Nathan Lierbo shared this idea 12 years ago
Completed

In a discussion with a cPanel Partner NOC, a suggestion came up that cPanel integrate per e-mail account mail sending limits, similar to the existing limits that can be configured in Tweak Settings that limit how many emails a domain can send per hour.


One goal of such functionality would be to avoid punishing other email users on a domain simply because 1 user decided to be abusive by means of sending bulk email.


Would you find this feature useful? Do you have any suggestions on how we should implement this feature?


Original thread: http://forums.cpanel.net/f145/mail-sending-limits-per-email-account-rather-than-per-domain-case-56138-a-150441.html

Best Answer
photo

Both the letter of this request and the spirit of this request are resolved with cPanel & WHM Version 74, which is currently in the EDGE tier. The combination of the Monitor Recipients for Potential Spammers, and the Action Taken when Spammers Found additions to Tweak Settings will monitor on a per-account basis, and allow webhosts to prevent negative impact from a compromised account.

Replies (13)

photo
1

I agree, this feature is entirely possible and should be integrated into cPanel similar to how per-Domain rate-limiting is provided. This is already supported by Direct Admin, I'd be glad to see this in cPanel as well:

http://help.directadmin.com/item.php?id=514

photo
1

i agree. This feature should be in exim. This is the very basic feature. Zimbra is providing this feature with help of policyd.

photo
3

Please, when this feature can be released?


Imagine a domain with 3000 email accounts, and just one send 1000 emails in one hour, other 2999 users will be restricted because 1!

photo
1

This request isn't on our map yet, but if that changes I'll definitely reach out here. I can definitely see how that would be problematic.

photo
2

I second this one. Two of the servers I deal with provide email services to companies with large amount of accounts, and from time to time, one user send a lot of mailings to enough destinations that trigger the hourly limits, restricting the rest of users to do their normal work. Our solution to this was to isolate those *intense* users into a separate reseller cpanel account with fewer limitations. But it's an administrative pain having them in several accounts being the main domain the master of a reseller one.


Instead, having a custom hourly mail limit by email account could ease these situations.

photo
2

Might I suggest that cPanel put this on their 'to-do list', rather than a "Roadmap".


It is of fairly high importance to find out what account is compromised, in a fast and diligent manner. I believe that this would do the trick. Cutting off access to every mail account is absurd, and could be used as an inside DOS attack.


Thanks.

photo
1

Sure! In this case, though, a roadmap is just our todo list. It's how/where/when we generally plan to answer a request. I can definitely understand what you're looking for, though.

photo
1

I, too, could have used the ability to limit an email account many times. Too often, one email account is the offender and screws it up for everyone on the domain. Please consider making it high on the priority list.

photo
1

i strongly agree. This feature should be in exim. Bcoz once i have set per domain mail sending limit then all a/c suffer due to a single email a/c compromised. This feature should be added as soon as possible.

photo
1

My strong recommendation for mail sending limits per e-mail account feature because it will be a very very useful because with that we can limit user unnecessary sending and also we can mange spam related problem easily that per user can't send mail after his limit per hour. and Also want current feature that is per domain sending per hour . With both feature we strongly manage our mail system like windows . And Cpanel will be more useful then any other system.

photo
1

This will surely also be applicable to SmartHost configs, as they are used per server, domain, and/or email account.

photo
1

This seems to be a great idea, we have several clients wich are company with sales team, imagine just 10 sellers that sends 50 emails in 1 hour each. that's 500 in 1 hour, wich is an above average limit, and that leaves the rest of the workers limited.

photo
1

No news on this topic? We are having huge domains being blocked becouse one mailbox account was sending spam. We really need to block only the mailbox that is sending spam and not the hole domain.

photo
1

This feature has not been added, but we added the Large Amount of Outbound Email feature in Version 68, and then improved it in version 70 by making the threshold configurable. It doesn't resolve this, but has the potential to help you catch problems before the domain is impacted. Read More

photo
1

Yes Benny, we are using that feature and is really helpful to detect spammers accounts individually. But we are detecting them once they have sent those spam mails. We really need some tool so as to stop or limit the spammer account before they send those mails.

Thanks.

photo
1

I'm happy to see I originated this thread and in the following 4 years something has been implemented.

I think the features are all there already, maybe the next improvement, as suggested by Natalio, would be not only to send an alert but maybe the options to send an alert AND block/suspend the suspected email account (not the whole domain of course)

photo
1

I think auto blocking the suspected email, given a threshold, is a great idea!

photo
1

Both the letter of this request and the spirit of this request are resolved with cPanel & WHM Version 74, which is currently in the EDGE tier. The combination of the Monitor Recipients for Potential Spammers, and the Action Taken when Spammers Found additions to Tweak Settings will monitor on a per-account basis, and allow webhosts to prevent negative impact from a compromised account.

photo
1

Great news!!

Thanks Benny.

photo
2

cPanel & WHM Version 74 has reached the CURRENT tier! Update to v74 now to see this change, and give it a quick test-spin!

Replies have been locked on this page!