Max defers and failures per hour cPanel exceeded error troubling you?
At Bobcares, we come with solutions for every query, big and small, as a part of our Server Management Service.
Let’s take a look at how our skilled Support Team helped a customer recently when they faced the “exceeded the max defers and failures per hour” error.
What is the “ Max defers and failures per hour cPanel exceeded” error?
Have you gotten stuck with the “exceeded the max defers and failures per hour” error? Well, you are in luck! Our Support Team has an easy solution for this specific issue.
This cPanel message indicates that the outgoing email has been put on hold on the server until the number of failed or deferred emails are below the email threshold.
How to view the current threshold for ‘max defers and failures per hour’ server-wide?
We can view the current threshold for “max defers and failures per hour” in the WHM interface.
Here, we navigate to Tweak Settings under Server Configuration in the interface and select the Mail tab. Then, we will come across the following two options as seen in the image:
- Maximum percentage of failed or deferred messages a domain may send per hour.
- Number of failed or deferred messages a domain may send before protections can be triggered.
Furthermore, this is a server-wide setting. Increasing the value has an effect on all email accounts.
How to view the current threshold for ‘max defers and failures per hour’ per account?
We can view the current threshold for “max defers and failures per hour” in the cPanel interface.
Moreover, we can access the “Maximum percentage of failed or deferred messages a domain may send per hour” option for each account. This option is available under Edit a Package in the Packages section as seen below:
Then, we will head to Modify an Account in the Account Functions section in WHM as seen below:
Possible reasons behind the “exceeded the max defers and failures per hour” message
- The domain may have bad Email Deliverability. In other words, it results in emails remaining in the Email queue and resending themselves at regular intervals.
Furthermore, Exim relies on the following rule by default when retrying email:
# This single retry rule applies to all domains and all errors. It specifies retries every 15 minutes for 2 hours, then increasing retry intervals, starting at 1 hour and increasing each time by a factor of 1.5, up to 16 hours, then retries every 8 hours until four days have passed since the first failed delivery.
In this scenario, our Support Engineers will ensure the Email Deliverability is apt for the domain with this documentation.
- The Contact Information for the domain may be using an outside email address for notifications. We can configure account notification emails in the Contact Information section.
Although we can use an external email address, in some scenarios it may be perceived as spam by the recipient mail server. This may be due to the structure and volume of the notifications.
[Looking for further assistance? We are just a click away.]
In conclusion, our Support Engineers demonstrated why we face the “exceeded the max defers and failures per hour” and how to deal with it.