Viktor Dukhovni:
> On Tue, Apr 21, 2015 at 04:25:14PM -0400, Wietse Venema wrote:
>
> > > It is sloppy, and unnecessary. If the domain is a virtual alias domain,
> > > each user needs to be aliased to a real domain (u...@mailstore.example.com
> > > where u...@example.com is the original virtual address, and "mailstore"
> > > varies by user to route either to Exchange or local delivery).
> >
> > This may not work when the exchange server expects u...@example.com
> > instead of u...@host.example.com. If we can't come up with a *simple*
> > solution for this, then we lose market share.
>
> It worked just fine in at least one large Exchange environment,
> because the Exchange server had multiple proxyAddresses for the
> user, one matching the canonical email address, and another matching
> the mailbox name.
>
> mail: first.l...@example.com
> proxyAddresses: smtp:first.l...@example.com
> proxyAddresses: smtp:fl...@exchange.example.com
In an ideal world, but this may not always be possible.
> Otherwise, the OP can simply choose to not make the domain a virtual
> alias domain, and route its users to Exchange by default, while
> rewriting only locally delivered users to user@localhost.
Assume two hosts, one providing inbound and outbound mail relay
service for the other, and both responsible for example.com.
1 - Split domain where Postfix is the smarthost. We have
that covered in existing documentation. Recipients are defined
with relay_recipient_maps or virtual_alias_maps depending on
where they are delivered. This is the scenario above.
2 - Split domain where Postfix is not the smarthost. This
is the Google apps scenario. This needs to be worked out.
Wietse
