On Tue, Jun 15, 2021 at 04:16:43PM +0200, Mono DHS wrote: > Assuming that I maintain neither local domains nor relay domains, > and only virtual mailbox domains, and that
You need an explicit "mydestination =" (empty) for that. Is that the case? > myorigin = $myhostname That should enable matching of unqualified (local part only) keys. > holds, the first requirement might be accomplished with having > > append_at_myorigin = yes > local_recipient_maps = inline:{ { postmaster = - } } But with "mydestination" empty, local_recipient_maps is not pertinent. > To satisfy the second requirement, I currently have > > virtual_alias_domains = > virtual_alias_maps = > inline:{ { postmaster = postmaster@⟨some virtual mailbox domain⟩ } } > > and this is where the problem starts. You should set virtual_alias_domains explicitly to a list of your desired virtual alias domains, or a separate table with same, unless you really mean to have an empty list of virtual alias domains. Do not rely on the obsolete backwards-compatibility setting: $ postconf -d virtual_alias_domains virtual_alias_domains = $virtual_alias_maps > The manpage to virtual(5) suggests in section TABLE SEARCH ORDER that > it first tries left hand sides of the form ⟨local-part⟩@⟨domain⟩ , > then ⟨local-part⟩ and finally @⟨domain⟩ . It also introduces the > concept of virtual alias domains and that with an empty > virtual_alias_domains, No, not "empty", rather *default*. > However, since only the left hand side of that first line is being > evaluated to decide what that virtual alias domain is, an ambiguity is > introduced w.r.t. non-virtual alias domain rewriting. The ambiguity is avoided by explicitly setting virtual_alias_domains independently of virtual_alias_maps. > So, the question is, how do I tell Postfix to disable its virtual alias > domain machinery, yet have the full power of address rewriting with > virtual(5) at my disposal? By setting an explicit list of virtual_alias_domains (empty if you like). -- Viktor.