Max defers and failures warning messages counts against the limit?
I've had this problem for a while and I never took the time to comment on it on the forum. Could it be that once a domain reaches the max deffers limit, every message that the client tries to send even to a valid email and bounces with the limit warning, does this message count against the same limit? The client does not know when the limit returns to normal so from time to time it continues sending and increasing the treshold.
Infinite loops are created for our clients from which they cannot exit until we lift the limit.
I want to know if this is normal or we are doing something wrong.
Thank you!
-
Hey there! No - when the account is in that temporarily blocked state, and future messages sent are just discarded automatically. You should see a log entry similar to this showing that is happening:
2023-08-02 14:36:26 1qR7oJ-0006NK-0w ** example@external_example.tld R=enforce_mail_permissions: Domain example.tld has exceeded the max defers and failures per hour (5/5 (100%)) allowed. Message discarded.
Because it was discarded and no delivery attempt was made, there is no way for the tools to know if it would have been a deferred or failed message, so it can't add to that limit.
0 -
The truth is I thought they did count. I always analyze the mail delivery report to see what activated the rule and I found few emails that actually bounced due to a problem with the destination box. Those are the ones that actually triggered the rule and then it never recovers.
I dismiss these warning messages as a problem then.
On the other hand, could it be that all these other deferred messages are to blame for triggering the defer rule? I assume they are caused by exceeding the limit of sent per hour.
0 -
Sure - if the messages get reattempted later and they also fail, that would just add to the length of time for the lockout.
0 -
It seems to me that CPanel's counting method is a BUG that needs to be fixed, if I'm understanding this correctly. Instead of counting deferrals, the system should count the number of distinct MESSAGES that get rejected or deferred, consistent with the wording in Tweak Settings: "Number of failed or deferred messages a domain may send before protections can be triggered."
Deferrals cause more problems than bounces, because a bounce is counted only once but a deferred can get counted many times -- especially if the recipient domain is something like gmail or yahoo with multiple MX records. Sometimes a single forwarded message is deferred 20 or more times in the first hour.
If a single message such as 1uys9f-000000080SQ-0yjX is being deferred multiple times, then only the FIRST deferral should be counted, right? It's only ONE message, so it should only count ONCE toward the deferral limit (or possibly once per recipient).
0 -
Dolphyn - it is my understanding that subsequent failures would also be flagged as a deferral - if an account is sending out spam, whether on purpose or accidentally, wouldn't we want to count all the deferrals that happen because of it?
0
Please sign in to leave a comment.
Comments
5 comments