On Tue, 2009-12-29 at 17:29 -0500, Victor Duchovni wrote: > > Adding example.com (or remote.domain) to mydestination above should mean > > that ONLY <existing local user>@example.com (or @remote.domain or > > @<address literal> is accepted, right? > No. It means that example.com becomes a local domain. Ok,.. of course,.. but only <existing local user>@<localdomain> should be accepted...
> > But it seems that also <non-existent local user>@example.com domain is > > accepted _if_ it is rewritten to some existing local user with > > virtual_alias_maps (the domains were not part of virtual_alias_domains)! > > And I do not really understand why ;) > Recipient validation existence of virtual mappings into account. Virtual > and canonical mappings apply to all domains, so it would be a mistake > to reject addresses that are rewritten downstream. So the SMTP server > performs an existence test on the lookup key. So this basically means: - When checking the domains (relay control) only normalisation is done? - When validating the recipients, normalisation and all other rewritings (canonical and virtual aliases) are taken into account? Is it here where the probe messages are sent? Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
