Trix wrote:

> I was hoping that with transport maps we could specify a
> "next-hop"-type thing where u...@example.com somehow automagically
> knows its mail needs to be delivered to exch1 without having to provide
> a fully qualified u...@exch1 address. Well, it was a nice idea while it
> lasted. :-)

You can do that. The question is how much effort you want to put into it.

You can build and maintain a manual list of users in the transport file, such as:

user1@example.com smtp:[exch1.example.com]
user2@example.com smtp:[exch2.example.com]

What some large companies have done for this same situation, is to deploy an
enterprise directory, and populate it with attributes from the AD, plus
any new attributes they require, such as mailRoutingAddress or mailHost.

It's also pretty easy to build a simple OpenLDAP database, and have Postfix query it,
versus using a transport file.

It all just depends on how you want to do it.

--
Greg