>> virtual_alias_maps = proxy:mysql:/etc/postfix/mysql_email_aliases >> @example.com -> [email protected]
> To stop the recursion for a specific user, ADD a 1:1 alias: > > [email protected] -> [email protected] > > This works because the more specific [email protected] has higher > precedence than the less specific @example.com. Am I using the wrong tool for creating a catchall to accept mail for addresses that are not specifically defined? This setup does not accept mail for local linux users, all valid email addresses are defined in virtual_mailbox_maps. If this is the best way to setup a catchall, I have a followup question; Using [email protected] -> [email protected] to break recursion, if i have defined 100 virtual users, ie [email protected] [email protected] [email protected] etc, does that mean I need to add 100 entries ([email protected] -> [email protected], etc) to the virtual_alias_maps table if i want to use a @example.com -> [email protected]? Is there any other way to switch off recursion behavior at a global level? virtual_alias_recursion_limit = 1 Will this give me the behavior I am looking for or will give give me unforeseen consequences? If I am understanding it correctly, if an alias in virtual_alias_maps points to another alias in virtual_alias_maps which then points to an address in virtual_mailbox_maps, having virtual_alias_recursion_limit=1 would break that scenario because it would attempt to deliver to the 2nd alias which doesn't exist generating back scatter. Is that the worst outcome? But then a catchall wouldn't overwrite explicit [email protected] -> [email protected] mappings, correct?
