I’m trying to apply an automation rule specifically for a source IP when sending to qq.com. Here’s the TOML snippet I used:
[[ “qq.com”.sources.“ip-217-156-55-216”.automation ]]
regex = “550 Connection frequency limited.*”
trigger = {Threshold=“1/hr”}
action = “Suspend”
duration = “1 hour”
The idea is to suspend delivery from this specific source when we see that particular error. However, when I run --validate, it throws an error related to interpreting the domain and source structure.
Could anyone help me confirm whether this is the correct syntax for applying automation under a specific source? Or should it be structured differently?
I don’t believe we support that. The idea is that you automate based on responses from the ISP. If they say too fast it’s too fast, so the appropriate response would apply regardless of source.
For the ISP qq.com, the connection frequency is restricted based on the IP. In a multi-IP setup, if one IP is identified as being limited, do I need to write an automation script to switch to a new IP to continue connecting with the ISP, or does KumoMTA have this functionality natively?
Based on my understanding, when sending emails to qq.com, I only need to set the automation for qq.com. If during the sending process, a rule like 550 Connection frequency limited.* is triggered, the duration = “1 hour” in the rule applies to the specific IP and not to all IPs. The KumoMTA program will automatically handle this and use another available IP to continue sending, correct?
As long as there is a non-suspended IP in the pool, it will use an available IP instead of the suspended one. And a suspend rule only applies to the IP that triggered it.
The above is the error log. I have a pool of 32 IPs, and some of them have already triggered rate limits. However, when I send emails to qq.com via SMTP, KumoMTA does not use the other available IPs for sending. Instead, it keeps using the rate-limited IPs, resulting in these errors. What could be the reason for this? message.txt (7.61 KB)