This object is in archive!
Additional email limits (per-domain, per-day, max in queue)
Needs Feedback
Hi,
what if one of the below setting configurable on Cpanel server:
1. number of emails may send as one shoot per domain
2. number of emails can domain send per a day.
3. number of emails allowed to be in queue per domainThanks.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
Could you please explain the use cases/situations in which you find these settings useful to you and that the existing "maximum emails sent per-hour for each domain" does not meet your needs?
The primary purpose for the email limit feature in cPanel & WHM is to try and limit/curb performance issues caused by high rates of email sending. What benefits do the features you've asked for provide over the existing one?
I have some concerns or at least issues I'd like you to consider with the options you've provided.
[1] What do you consider "one shoot"? If it's a time-based limit, please convey the time interval. If this is a matter of maximum recipients per email transaction, then this functionality is already built-in to Exim and editable through the advanced exim editor in WHM. Simply configure the option:
recipients_max
or
recipients_max_reject
depending on your desired behavior (More information in the Exim Documentation). Note that RFC for SMTP indicates at least 100 recipients per message should be accepted. If you go below that, your server is then inconsistent with RFC.
[2] What benefit does a daily limit have over hourly? A 24 hour span allows for a much heavier volume of email to occur before a limit enacts. It also enforces (in my opinion) an extreme penalty to the user. With the hourly limit, the longest the user goes without the ability to send email is 1 hour. With a 24 hour limit, they would have to potentially wait an entire day before sending mail again. I would see this situation as ending up with most customers complaining to their hosting providers who then simply disable/remove the daily limit temporarily anyway upon complaint.
[3] Could you explain the value in this behavior? Preventing mail from entering the queue is equivalent to deleting that mail forever and the customer never knowing it wasn't received or wasn't delivered. This is strongly advised against as it's essentially dishonesty with your customers. If you're doing this to address large queues from spammers, you should be handling those on a per-case basis using the queue search/delete tool provided in WHM. Setting a queue limit per domain is simply too wide of a behavior that would end up punishing legitimate customers.
--
It seems that most of your requests center around trying to deal with spammers on your server. I'd strongly suggest addressing the spammers directly and swiftly on your server in alternative ways (proactively reviewing those who breach the maximum email per-hour limit, checking the mail queue, etc) as opposed to enforcing server-wide rules that, I personally feel, would end up inadvertently punishing your legitimate user base.
I invite further feedback and comments on this to see whether or not these features are desired by the community/hosting providers.
Could you please explain the use cases/situations in which you find these settings useful to you and that the existing "maximum emails sent per-hour for each domain" does not meet your needs?
The primary purpose for the email limit feature in cPanel & WHM is to try and limit/curb performance issues caused by high rates of email sending. What benefits do the features you've asked for provide over the existing one?
I have some concerns or at least issues I'd like you to consider with the options you've provided.
[1] What do you consider "one shoot"? If it's a time-based limit, please convey the time interval. If this is a matter of maximum recipients per email transaction, then this functionality is already built-in to Exim and editable through the advanced exim editor in WHM. Simply configure the option:
recipients_max
or
recipients_max_reject
depending on your desired behavior (More information in the Exim Documentation). Note that RFC for SMTP indicates at least 100 recipients per message should be accepted. If you go below that, your server is then inconsistent with RFC.
[2] What benefit does a daily limit have over hourly? A 24 hour span allows for a much heavier volume of email to occur before a limit enacts. It also enforces (in my opinion) an extreme penalty to the user. With the hourly limit, the longest the user goes without the ability to send email is 1 hour. With a 24 hour limit, they would have to potentially wait an entire day before sending mail again. I would see this situation as ending up with most customers complaining to their hosting providers who then simply disable/remove the daily limit temporarily anyway upon complaint.
[3] Could you explain the value in this behavior? Preventing mail from entering the queue is equivalent to deleting that mail forever and the customer never knowing it wasn't received or wasn't delivered. This is strongly advised against as it's essentially dishonesty with your customers. If you're doing this to address large queues from spammers, you should be handling those on a per-case basis using the queue search/delete tool provided in WHM. Setting a queue limit per domain is simply too wide of a behavior that would end up punishing legitimate customers.
--
It seems that most of your requests center around trying to deal with spammers on your server. I'd strongly suggest addressing the spammers directly and swiftly on your server in alternative ways (proactively reviewing those who breach the maximum email per-hour limit, checking the mail queue, etc) as opposed to enforcing server-wide rules that, I personally feel, would end up inadvertently punishing your legitimate user base.
I invite further feedback and comments on this to see whether or not these features are desired by the community/hosting providers.
Could you please explain the use cases/situations in which you find these settings useful to you and that the existing "maximum emails sent per-hour for each domain" does not meet your needs?
The primary purpose for the email limit feature in cPanel & WHM is to try and limit/curb performance issues caused by high rates of email sending. What benefits do the features you've asked for provide over the existing one?
I have some concerns or at least issues I'd like you to consider with the options you've provided.
[1] What do you consider "one shoot"? If it's a time-based limit, please convey the time interval. If this is a matter of maximum recipients per email transaction, then this functionality is already built-in to Exim and editable through the advanced exim editor in WHM. Simply configure the option:
recipients_max
or
recipients_max_reject
depending on your desired behavior (More information in the Exim Documentation). Note that RFC for SMTP indicates at least 100 recipients per message should be accepted. If you go below that, your server is then inconsistent with RFC.
[2] What benefit does a daily limit have over hourly? A 24 hour span allows for a much heavier volume of email to occur before a limit enacts. It also enforces (in my opinion) an extreme penalty to the user. With the hourly limit, the longest the user goes without the ability to send email is 1 hour. With a 24 hour limit, they would have to potentially wait an entire day before sending mail again. I would see this situation as ending up with most customers complaining to their hosting providers who then simply disable/remove the daily limit temporarily anyway upon complaint.
[3] Could you explain the value in this behavior? Preventing mail from entering the queue is equivalent to deleting that mail forever and the customer never knowing it wasn't received or wasn't delivered. This is strongly advised against as it's essentially dishonesty with your customers. If you're doing this to address large queues from spammers, you should be handling those on a per-case basis using the queue search/delete tool provided in WHM. Setting a queue limit per domain is simply too wide of a behavior that would end up punishing legitimate customers.
--
It seems that most of your requests center around trying to deal with spammers on your server. I'd strongly suggest addressing the spammers directly and swiftly on your server in alternative ways (proactively reviewing those who breach the maximum email per-hour limit, checking the mail queue, etc) as opposed to enforcing server-wide rules that, I personally feel, would end up inadvertently punishing your legitimate user base.
I invite further feedback and comments on this to see whether or not these features are desired by the community/hosting providers.
Could you please explain the use cases/situations in which you find these settings useful to you and that the existing "maximum emails sent per-hour for each domain" does not meet your needs?
The primary purpose for the email limit feature in cPanel & WHM is to try and limit/curb performance issues caused by high rates of email sending. What benefits do the features you've asked for provide over the existing one?
I have some concerns or at least issues I'd like you to consider with the options you've provided.
[1] What do you consider "one shoot"? If it's a time-based limit, please convey the time interval. If this is a matter of maximum recipients per email transaction, then this functionality is already built-in to Exim and editable through the advanced exim editor in WHM. Simply configure the option:
recipients_max
or
recipients_max_reject
depending on your desired behavior (More information in the Exim Documentation). Note that RFC for SMTP indicates at least 100 recipients per message should be accepted. If you go below that, your server is then inconsistent with RFC.
[2] What benefit does a daily limit have over hourly? A 24 hour span allows for a much heavier volume of email to occur before a limit enacts. It also enforces (in my opinion) an extreme penalty to the user. With the hourly limit, the longest the user goes without the ability to send email is 1 hour. With a 24 hour limit, they would have to potentially wait an entire day before sending mail again. I would see this situation as ending up with most customers complaining to their hosting providers who then simply disable/remove the daily limit temporarily anyway upon complaint.
[3] Could you explain the value in this behavior? Preventing mail from entering the queue is equivalent to deleting that mail forever and the customer never knowing it wasn't received or wasn't delivered. This is strongly advised against as it's essentially dishonesty with your customers. If you're doing this to address large queues from spammers, you should be handling those on a per-case basis using the queue search/delete tool provided in WHM. Setting a queue limit per domain is simply too wide of a behavior that would end up punishing legitimate customers.
--
It seems that most of your requests center around trying to deal with spammers on your server. I'd strongly suggest addressing the spammers directly and swiftly on your server in alternative ways (proactively reviewing those who breach the maximum email per-hour limit, checking the mail queue, etc) as opposed to enforcing server-wide rules that, I personally feel, would end up inadvertently punishing your legitimate user base.
I invite further feedback and comments on this to see whether or not these features are desired by the community/hosting providers.
The 3rd recommendation would be good.
Providers should know wich is a normal queue limit per-account, you can set it to a large number like 5.000 or even more (you know better how your clients uses your mail system), but there are spammer cases where they are able to send and put on the queue about 20-50 thousand e-mails on it, so, would be good to get it limited, instead of start a long task of cleaning the queue.
The 3rd recommendation would be good.
Providers should know wich is a normal queue limit per-account, you can set it to a large number like 5.000 or even more (you know better how your clients uses your mail system), but there are spammer cases where they are able to send and put on the queue about 20-50 thousand e-mails on it, so, would be good to get it limited, instead of start a long task of cleaning the queue.
Replies have been locked on this page!