> On Sep 18, 2017, at 11:35 AM, Andreas Thienemann <[email protected]> wrote:
>
> As far as I understand, the virtual_alias_maps will only do rewriting to
> local or remote addresses but disregard transport entries.
No, this is not the case. All that happens with virtual_alias_maps
is recursive rewriting of all input recipient addresses to some final
address.
It is virtual_alias_domains that preempts transport selection for
addresses that are NOT rewritten to some real domain. Thus you
can have:
mydestination = local.example.com, ...
relay_domains = real.example.com, ...
virtual_alias_domains = valias.example.com, ...
virtual_mailbox_domains = vmbox.example.com, ...
and the only constraints are:
* Each domain belongs to exactly one address class.
* ONLY domains that contain no real recipients to be
handed off to some transport for delivery may be
listed in virtual_alias_domains.
Therefore you can have in virtual_alias_maps:
# The dreaded catchall applies to all mailboxes that
# are not explicitly mapped to themselves or out of the
# domain
@real.example.com [email protected]
[email protected] [email protected]
and then in transport_maps:
[email protected] uucp
or, conversely
real.example.com uucp
If the majority of users that stay in @real.example.comm use that
transport.
--
Viktor.
