On 04 Dec 2019, at 09:52, Viktor Dukhovni <postfix-us...@dukhovni.org> wrote: > $ config_directory=$(postconf config_directory) > $ maps="proxy:mysql:$config_directory/mysql_virtual_alias_maps.cf > hash:$config_directory/virtual" > $ postmap -q ama...@myvirtualdomain.tld $maps
Aha! I was only checking virtual instead of both maps. Of course that shows the issue immediately. *@virtualdomain was mapped to *@covisp.net for inexplicable reasons. > Also, note that virtual alias expansion is recursive. What does > > kreme+ama...@kreme.com I did test that as mail to that addresss was delivered to the “amazon” box on my account. >> So, the issue appears to be limited to a specific virtual domain. > > Nonsense: > > 0. Virtual alias and address extension processing is uniform across all > domains Yes, that’s why this was confusing. But it WAS limited to one domain because of errors in the alias portion of the database. > 1. There is no issue, everything is working exactl as documented, you're > just surprised by the results of the mappings you've configured. Well, the mappings yes. Postfix admin allows domains to be administered by authorized users. Thank you, all is good now.
