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
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.
I think that not all Postfix users realize the virtual alias
rewriting applies to all envelope recipients, not just those in
virtual alias domains. And so users needlessly configure virtual
alias domains where the domains also have real mailboxes.
Finally, any virtual mapping can be "reversed" with smtp_generic_maps,
so that the Exchange server sees the primary address in the envelope,
but *that* is not the *simple* solution you were after.
--
Viktor.
