Addresses used in E-mail messages, in client "login names", and in Signals can contain unknown names. If the Server cannot find an Object (an Account, a Mailing List, an Alias, a Group, or a Forwarder) with the specified name, the Domain Unknown Names settings are used.
Consult External for Unknown: When an unknown name is supplied and this option is enabled, the CommuniGate Pro Server sends a command to the External Authentication Helper application. That application can check an external database (or any other data source) and optionally create a new object (an Account, an Alias, etc.) with the specified name. If the program returns a positive response, the Server makes one more attempt to find a Domain object.
Mail to Unknown: This setting specifies what the Server should do when unknown account/object names are encountered in E-mail message addresses.
Note: you specify an E-mail address, not an account name there. So, if you specify Rerouted To: Postmaster for the client1.com Domain, messages sent to unknown names will be routed to the Postmaster account in the Main Domain, not to the postmaster Account in that client1.com Secondary Domain. Specify email@example.com to direct those messages to the postmaster Account in the client1.com Domain.
Note: you can use the asterisk (*) symbol in the E-mail address field. This symbol will be replaced with the original (unknown) name.
The Domain client1.com Mail to Unknown Name option is set to Rerouted to: Badfirstname.lastname@example.org A message comes addressed to email@example.com, and the Account jjones does not exist in the client1.com Domain. The message is rerouted to firstname.lastname@example.org
Calls to Unknown: This setting specifies what the Server should do when unknown account/object names are encountered in Signal addresses. This setting is set in the same way as the Mail to Unknown setting.
Access to Unknown: This setting specifies what the Server should do when unknown account/object names are encountered in Access opera