I know that there are many other problems at the moment but I can only request this new feature again, among other things present in other mailservers that I manage
In the last few days, an anti-spam server that is part of siteground has started rejecting messages from my users
[2023.05.12] 11:21:30.065  Initiating connection to 126.96.36.199
[2023.05.12] 11:21:30.065  Connecting to 188.8.131.52:25 (Id: 3)
[2023.05.12] 11:21:30.065  Connection to 184.108.40.206:25 from 10.60.0.20:59370 succeeded (Id: 3)
[2023.05.12] 11:21:30.862  RSP: 451-Message rejected due to the low reputation of xxx.xxx.xxx.xxx at mail server
[2023.05.12] 11:21:30.862  RSP: 451-instance-europe-west4-bkh2.prod.antispam.mailspamprotection.com. Try again
[2023.05.12] 11:21:30.862  RSP: 451 later.
here is an example.
he tries it sometimes, on various servers and then
Remote Server returned: '601 Attempted to send the message to the following IPs: 220.127.116.11, 18.104.22.168, 22.214.171.124'
My server has high reputation on sendscore on cisco talos on cyren, it is not the list in any spam list
So the problem is not there, but in a listing by a specific provider
it relates to only one of my users and therefore I simply changed the exit gateway to that domain
But now I'm wondering why the only option for outbound gateways is either fixed or round robin
Why can't I tell it to use this other gateway if sending fails?
Why can't I set a rule that says if the recipient is @xxxx.xxxx use this gateway?
I know that many of you have large installations and already use a non-SM gateway and the rules are made there, but it seems to me that SM works well on its own and introducing some rules in the exit gateways seems very useful to me
I especially don't like round robin, I would prefer secondary gateway to use if primary send fails.