We have an attribute in our ldap that I'd like to use to determine the "next hop" for mail transport. The attribute is not itself the name of the next transport.
Is there a way to set up a mapping for this? ie: dn: xxx... routingattribute: foo route messages with this attribute to smtp:bar.com:25 dn: yyy... routingattribute: baz route messages with this attribute to smtp:qux.com:25
