Domain Management

EmailArchitect Email Server supports multiple domains. The maximum number of domain it can support is restricted by the license agreement.

To configure domain settings, you have to logon as "system" user. Then click "Domains".

EmailArchitect Email Server supports 2 types of domain settings: 

Local Domain

All users' settings and emails are stored in current local machine.

Max Users

Max Users limits the maximum number of users under this domain.

Each mailbox quota

Quota Size limits the maximum size of mailbox of a single user.

Catch-All Alias

Catch-All Alias can be used to create a Catch-All account. E.g. you can create a user named "default" in domain "adminsystem.com", and input default@adminsystem.com into Catch-All Alias field. Any email sent to non-existent user of adminsystem.com will then be forwarded to "default@adminsystem.com".

Default Domain

When users send/receive email by mail server, they need to provide the user name and password for authentication. In Emailarchitect server, the user name is the full email address of the user such as test@testdomain.com; But if the domain is set to default domain, then the user in this domain can logon the mail server without domain name. E.g. test@testdomain.com -> test

General Settings for domain hosted by ISP

E.g. company A hosts its domain "adminsystem.com" at ISP B. Company A needs 20 email accounts under the domain, each email account requires 100M storage. The administrator of ISP B should do the following settings:

Logon As system user, create a local domain named "adminsystem.com". Create a user named "admin" in this domain and set this account as domain administrator. Set Max Users to 20, Quota Size to 100M and Catch-Al Alias to "admin@adminsystem.com" in domain setting.

Staff of Company A can use this account admin@adminsystem.com to logon Web Access and create other user accounts.

Only "system" user has the right to edit above options; domain administrator can only read these options.

Remote Domain

There is no user account in remote domain, all email sent to this domain will be forwarded to a local domain, email address or a remote host if forwarding function is activated.

Forward to a local domain

All email sent to this domain will be forwarded to the same user (username) of specified local domain.

E.g. company A owns two domains: "adminsystem.com" and "adminsystem.net". They want all incoming emails to both [user]@adminsystem.com and [user]@adminsystem.net to be stored in one mailbox. In this case, server administrator should do the following steps:

Create a local domain named "adminsystem.com", and create users for this domain.
Create a remote domain named "adminsystem.net", and set "Forward to a local domain: adminsystem.com".

All emails to [user]@adminsystem.net will then be forwarded to [user]@adminsystem.com. E.g. email to admin@adminsystem.net will be forwarded to admin@adminsystem.com. After this setting is activated, you can no longer use admin@adminsystem.net to logon Web Access or POP3 service. You must use admin@adminsystem.com to logon EmailArchitect Email Server.

Forward to an email address

All email sent to this domain will be forwarded to the specified email address.

E.g. A SOHO businessman named C hosts a domain "adminsystem.com" at ISP B. As requested ISP B created sales@adminsystem.com, info@adminsystem.com and support@adminsystem.com. He finds troublesome to manage too many email account so he want to forward all emails under *@adminsystem.com to his frequently used email account myemail@hotmail.com. In this case, the server administrator should do the following steps:

Create a remote domain named "adminsystem.com".
Set "Forward to an email address: myemail@hotmail.com." in the domain setting.

Then all emails to *@adminsystem.com will be forwarded to myemail@hotmail.com.

Forward to a remote host

All email sent to this domain will be relayed to the specified remote host. If no host is specified, the emails will be relayed to MX record of the domain.

If you set a remote domain to forward to "Forward to a remote host" and the remote host doesn't listen on 25 port, then you can specify the port like this host[space]port, e.g. mail.remotehost.com 587. If the remost host requires the user authentication, you can specify user and password like this: host[space]port/user/password. E.g. mail.remotehost.com 25/tx@adminsystem.com/testpass

Recipients Control in Remote Domain

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.

Delete Domain

Caution: Once a domain is deleted, all configuration files and user folders can't be restored. If you just want to disable current domain temporarily, you can uncheck "Active" in domain setting.

Default Domain

when the user logon to SMTP/POP3/IMAP4 service, the user need to use his email address(user@domain) as the user name.
E.g.
myemail@mydomain.com

But if the domain is set to default domain, then the user can logon SMTP/POP3/IMAP4 service without domain.
E.g.
just use myemail as the username to logon SMTP/POP3/IMAP4 service is ok.

See Also

Quick Tutorial  User Permissions  Domain Administration  User Administration  Services Administration  SMTP Service  POP3 Service  IMAP4 Service  Remote Object Call Service  Webmail Service  SSL Configuration  Realtime Black List  Anti-Spam  Anti-Virus  List Administration  Traffic Control  DBConnector  Mail Archive  DomainKeys and DKIM signature  Storage and User Mailbox  Incoming/outgoing Filters  Advanced Functions in Filter  Templates 

EmailArchitect Server Website
EmailArchitect Server Community