On Wed, May 31, 2017 at 6:34 AM, Gilles Chehade <[email protected]> wrote:
> It is not that simple because newaliases works when you have one aliases > database (e.g. /etc/mail/aliases). This is the case on the default setup > but smtpd supports per-rule aliases mappings and for example the MX that > I run for poolp.org Sounds like newaliases should check the config for the existence of multiple aliases mappings, And either enumerate and make sure all of them get refreshed, Or return an error listing out possible alias mappings to refresh and ask you to pick newaliases (-a | <which table?>) Either way, requiring some wordy incantation such as "smtpctl update table aliases" to get what newaliases did for standard configurations is not very cool. Or for non-standard configurations that break newaliases list as a documented caveat of using the options for custom tables. -- -JH
