> > 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
Wietse Venema:
> Jason Lancaster:
> > 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_defa
Jason Lancaster:
> 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
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
