Roman Medina-Heigl Hernandez a écrit :
> Noel Jones escribió:
>> [snip]
>> Use 1-1 mappings. Use a little script and a Makefile to let the
>> computer build the aliased domain from the real domain list you already
>> maintain. Size of the table is not an issue.
>>
>> Your postconf output looks OK.
>
> Yes, all tasks can usually be automatized but sometimes it's good to
> simplify things.
> [snip]
Here's an (I hope, illustrative) example of a mysql setup where this is
not a problem:
- table User contains "user" and "domain" columns.
- table DomainAlias contains "alias" and "destination" columns.
query = select User.domain from User, DomainAlias where
alias = '%s' and destination = domain
(the user column must never be empty).
The limitation is that you can't use "recursive" domain aliases, so you
can't implement this:
@example.com @example.org
@example.org @example.net
but such recursive aliases would be expensive anyway, and one can
resolve them ahead of time (in the UI that adds them, for instance).
Of course, you can also use a policy service to "fix" the problem.
