On Tue, Nov 07, 2023 at 08:14:04AM -0500, Wietse Venema via Postfix-users wrote:
> 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. We don't have a mechanism to schedule by MX host (IP). And there are at least conceptual difficulties when the lists of IPs for various domains overlap, but don't coincide. Is the destination the same or not? Which IP address will be actually used for the delivery? ... This is a non-trivial problem. The best thing to do when sending at volume is to negotiate sufficiently high concurrency caps with the high volume receiving systems. The Postfix queue manager simply does not have enough information to consolidate and schedule deliveries by MX IP. -- Viktor. _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org