>> Another option would be to use the DNS resolver (Bind, unbound, etc) >> support to manipulate zone lookups. > > But the OP wants a dedicated transport (for concurrency control and > scheduling), not a change of destination IP, though in a multi-stage MTA > setup that IP could point at a dedicated Postfix instance.
The OP mentioned mailjet(.com?) which is a service provider. It sounds like all emails to domains hosted via *.outlook.com should be routed via mailjet. That way concurrency control/scheduling is handed off to them. Another solution would be to implement a small daemon that is queried via tcp_table. It could check a destination mx name via dns and if it matches *.protection.outlook.com returns a mailjet server as nexthop. https://www.postfix.org/tcp_table.5.html Best regards Gerald _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
