> > Possible avenues: allow transport::port and :port,
> A domain-less next-hop destination (:port) would break the scheduler,
> which schedules deliveries by the next-hop destination. Note that
> the scheduler does not know about host:port syntax, nor does it
> know which delivery agents support
Hello,
I'm looking for a way to map senders with different sending reputation
to specific destination ports (that will eventually be mapped to
different sending IPs by the firewall) without hardcoding the nexthop.
sender_dependent_default_transport_maps are working great for setting
the transport
Hello,
I'm trying to select a transport to use based on the recipient domain
in a transport_map hash file, but a lower priority regexp that matches
the full recipient address is overriding the higher priority
domain-level match. Based on the postconf transport_maps
documentation, "Tables will be
