This table allows you to specify aliases that will work for all local Domains.
When the CommuniGate Pro Server detects that a message or a signal should be directed to some name in one of the Server local domains, these records are checked. If the local part of the address matches the Local Address field in one of these records, the address is rerouted to the address specified in the Reroute To field.
If, for example, the abuse and firstname.lastname@example.org addresses are entered into the All-Domain Aliases table (as shown above), then all messages directed to any email@example.com address (where domain.com is one of the CommuniGate Pro Domains) are rerouted to the firstname.lastname@example.org.
Note: it is very easy to create routing loops using these records: if you enter:
postmaster -> email@example.com
into this table, you will create a loop that will make it impossible to connect to the Server as postmaster. If you want E-mails and Signals to all postmaster names in all Domains to go to the postmaster account in the main CommuniGate Pro domain, you should use:
postmaster -> firstname.lastname@example.org
or, if the Direct Mailbox Addressing option is enabled:
postmaster -> mailboxName#postmaster
You can use wildcard (*) symbols in these fields.
For example, you may want to create a "dial plan" for your organization that has 10 different departments, each served with its own Domain:
If Accounts in each Domain have aliases in the 200-299 range, then the users can call other users within the same Domain by dialing the 2xx number.
They dial the 91 prefix (a 912xx number) to reach users in the domain1.com Domain.
They will use the 92 prefix to reach users in the domain2.com Domain, etc.