Sorry, but I insist again.

I would like SM to become a complete product, without having to use third-party gateways to implement specific functions

I would like is the ability to put routing rules on delivery. It would be a breakthrough and a significant increase in functionality.

Imagine that a series of rules could be inserted into the delivery queue and applied in order of priority, for example:

1) if the recipient is @hotmail.com use the smtp2go gateway - continue with the other rules

2) if the recipient is gmail.com use the outgoing ipv4 xxx.xxx.xxx - continue with the other rules

3) if the recipient is from a forwarder or alias, use the smtp2go gateway - stop further rules

4) if the email is destined for more than 2 recipients, use the outgoing ipv4 xxx.x..xx - continue with the other rules.

I repeat, in my opinion sm would make a significant leap in quality and would significantly reduce the need to use an exit gateway like postfix on which to then apply the rules. That is, it would make sm independent. Furthermore, only SM could apply rules like 3

I hope to generate debate and reflection on what has been said.

Add that the routing rules are present, with various levels of functionality, in icewarp ( https://docs.icewarp.com/Content/IceWarp-Server/Administration-Nodes/Mail%20Service/General/Routing.htm ) - on icewarp it also acts on the input queue, I have used it several times in particular situations

exchange

N.b.

Sometimes it happens that a domain (sometimes entire groups for example: microsoft, gmail...) block in a more or less legitimate way the IP of our server. Sometimes on principle, and then we are forced to chase.

While we solve the problem because diverting all outgoing traffic to smtp2go for example. is a cost.

we could divert only traffic to @hotmail.com for example.

Instead to apply a rule like that I have to divert to another gateway, and then apply the rules from there. It seems sincerely absurd to me.

Another thing that I have repeatedly reported.

It would be appropriate to be able to assign an outgoing gateway to forwards or aliases. They dirty the reputation of our IP.

In this specific case only SM can know if it is a forward or an alias so I have no other way to solve.

I agree that it would be better not to use either forwards or aliases, but they are the needs of the customers.