Why if we set this to UNLIMITED the block kicks in the same?
Any real solution to this issue?
Thanks
Any real solution to this issue?
Thanks
Hello 
Could you verify where you have configured this value to unlimited? Did you modify it globally or for the individual account?
Thank you.
Could you verify where you have configured this value to unlimited? Did you modify it globally or for the individual account?
Thank you.
Hallo MIchael! Thank you for your quick reply much appreciated.
In WHM Server > TWEAK SETTINGS so I guess this is globally. Where should I look for "account specific"?
Anyway in our WHM Server > TWEAK SETTINGS we have
Max hourly emails per domain [?]
Unlimited default
The percentage of email messages (above the account’s hourly maximum) to queue and retry for delivery. (Minimum: 100; Maximum: 10,000) [?]
125 % default
Count mailman deliveries towards a domain’s Max hourly emails. [?]
Off
default
Maximum percentage of failed or deferred messages a domain may send per hour [?]
Unlimited default
But reading some topics on this forum I found everyone saying that setting "Maximum percentage of failed or deferred messages.." to unlimited won't avoid the block to kick in and this is exactly what we experienced so far
In WHM Server > TWEAK SETTINGS so I guess this is globally. Where should I look for "account specific"?
Anyway in our WHM Server > TWEAK SETTINGS we have
Max hourly emails per domain [?]
Unlimited default
The percentage of email messages (above the account’s hourly maximum) to queue and retry for delivery. (Minimum: 100; Maximum: 10,000) [?]
125 % default
Count mailman deliveries towards a domain’s Max hourly emails. [?]
Off
default
Maximum percentage of failed or deferred messages a domain may send per hour [?]
Unlimited default
But reading some topics on this forum I found everyone saying that setting "Maximum percentage of failed or deferred messages.." to unlimited won't avoid the block to kick in and this is exactly what we experienced so far
Browse to:
"WHM Home » Account Functions » Modify an Account"
Check to make sure there is not a value assigned to the individual account per it's package, as this has higher priority than the global value.
Thank you.
"WHM Home » Account Functions » Modify an Account"
Check to make sure there is not a value assigned to the individual account per it's package, as this has higher priority than the global value.
Thank you.
Thank you boss! Infact we had a limited setting there!
So you are quite confident there is no bug on this setting like many reported here on the forum right? If we both set unlimited for global and single accounts the block should never kick in?
So you are quite confident there is no bug on this setting like many reported here on the forum right? If we both set unlimited for global and single accounts the block should never kick in?
I am not aware of any bugs that would prevent this option from working as intended if you set it to an unlimited value. Could you provide the links to the posts where a bug has been reported with this feature?
Thank you.
Sure! At the moment all the threads I found on the subject pointed to the functionality not working as intended (maybe they had my same problem and didn't check into account specific settings!)
http://forums.cpanel.net/f43/domain-example-com-has-exceeded-max-defers-failures-per-hour-5-5-a-296962.html
http://forums.cpanel.net/f43/domain-has-exceeded-max-defers-failures-per-hour-5-5-100-a-316011.html
http://forums.cpanel.net/f43/domain-example-com-has-exceeded-max-defers-failures-per-hour-5-5-a-296962.html
http://forums.cpanel.net/f43/domain-has-exceeded-max-defers-failures-per-hour-5-5-100-a-316011.html
I do not see references to the individual account limits in those threads. Due to the age of those threads, it's hard to say exactly what may have caused those issues beyond the individual account limit. Feel free to let us know if you experience any additional problems.
Thank you.
Thank you.
Thank you for your support. You've been very kind and helpful (and blazing fast!!).
I think what we have done so far has solved the issue!
I think what we have done so far has solved the issue!