We would really appreciate the ability to add a wildcard pattern match for alias addresses.
Some of destination servers we deliver to utilize dynamic alias addresses, where anything matching the format of username-*@domain.com will be considered a valid recipient, and will forward to username@domain.com. These addresses work without explicitly defining them on the destination server. For example, all of the following are considered valid aliases:
username-foo@domain.com
username-anything@domain.com
username-1234@domain.com
etc.
Would it be possible to allow aliases to contain a wildcard so that adding this:
username-*@domain.com
as an alias to an account would ensure any email matching that pattern was associated with the account, both in terms of processing and allowing the user to view that email in the messages list?
This would be useful for a number of MTA implementations:
We would really appreciate the ability to add a wildcard pattern match for alias addresses.
Some of destination servers we deliver to utilize dynamic alias addresses, where anything matching the format of
username-*@domain.com
will be considered a valid recipient, and will forward tousername@domain.com
. These addresses work without explicitly defining them on the destination server. For example, all of the following are considered valid aliases:Would it be possible to allow aliases to contain a wildcard so that adding this:
as an alias to an account would ensure any email matching that pattern was associated with the account, both in terms of processing and allowing the user to view that email in the messages list?
This would be useful for a number of MTA implementations:
Thanks for considering!