EmailArchitect Email Server supports multiple domains. The maximum number of domain it can support is restricted by the license agreement. All domains can be managed via Web Administration. Both local and remote domain support domain filters for customized tasks.
Basically, EmailArchitect Email Server supports 2 types of domain settings.
All users and emails are stored in local machine. Local domain supports nobody alias, users count limitation, message size limitation and quota size limitation.
Local domain also supports user alias. User alias doesn't have real mailbox on the server. Instead, it is an email list. Every email to this user alias will be forwarded to every email addresses in this alias. For company, the administrator can create user alias for every department, and add all the email addresses of the deparment's staffs to this alias. Other people can send email to this alias to deliver the message to every staff mailbox in this department instead of send email one by one.
User alias can also act as a newsletter, for more detial, please refer to LIST Service.
Remote domain doesn't have users, you can set email to this domain to be forwarded to a local domain, email address or a remote host.
For most email servers, every email to the remote domain will be accepted no matter the recipient is. For example, there is a remote domain named "testdomain" in the server, it will forward all email to (*@testdomain) this domain to another remote server, even the user doesn't exist on the remote server. That will consume a lot of networking resource. In the contrast, the administrator can set the valid recipients list in remote domain of EmailArchitect Email Server, any email to invalid recipients of remote domain will be rejected by EmailArchitect SMTP Service directly.