General
Pro was meant for multi-domain hosting i.e. each domain with its own settings and may be managed by separate entity (webmaster) than the one providing the service (provider).
Because the setting up Pro is quite technical, we require that you have a team or have indepth knowledge of your server and hosting (your web server).
This article is a guide on what you need to do. The best thing is to engage SocketMail team to do the work.
1. Install the software
Install the SocketMail Pro software,
2. Define the domain and its associated URL in Provider Admin
You can add domain and its properties (such as the webmail URL of the domain) in Provider Admin.
In Pro, each domain must be associate with its webmail url and need to be point to the virtualhost of which the software was installed.
Example, you have 3 domains, domain1.tld, domain2.tld and domain3.tld
Assuming that you install Pro in domain1.tld account in the /webmail/ folder, therefore the address www.domain1.tld/webmail/ is where public can access the installed Pro.
Therefore, in the Provider Admin, you will add domain . So, for each domain, domain1.tld, domain2.tld and domain3.tld, you need to add to the system via Provider Admin. You can set different limits etc.
The domains and its associated URL to be entered in Provider Admin are as in the matrix below :
|
Domain Name |
Domain's webmail URL |
|
domain1.tld |
www.domain1.tld |
|
domain2.tld |
|
|
domain3.tld |
|
The "domain's webmail URL" can be refered in the form in the Provider Admin as "Client Interface URL" as shown in the image below :

3. Create (A)lias record in the DNS for the domains to be hosted
In this example/case, you don't need to create any Alias record for domain1.tld domain because thats where you installed Pro (i.e. in www.domain1.tld site).
For domain2.tld and domain3.tld domains, in their DNS entry, you created email.domain2.tld and email.domain3.tld as (A)lias record pointing to IP address of whats domain1.tld is, coz thats where you installed Pro.
4. Add ServerAlias directive in Apache's httpd config file
For each url, you have to add as ServerAlias in Apache's virtualhost (of domain1.tld, because thats where you installed Pro). So that email.domain2.tld and email.domain3.tld will point to the same website, i.e.
www.domain1.tld site.
4.1 Apache config file in CPanel based server
If you are using CPanel, most likely that your Apache config file is all in one file i.e. in /etc/httpd/conf/httpd.conf
4.2 Apache config file in Plesk based server
The Apache config file are split by domains. The file normally reside in each domain /conf/httpd.include. So, in this example, the file is in /home/httpd/vhosts/domain1.tld/conf/httpd.include
4.3 Add 'ServerAlias' directive
Once you have identified the config file, edit the file and add in "ServerAlias" directive below the "ServerName" directive or if there are other ServerAlias directives, add below that line. Example :
You need to restart Apache so that the definition will take place.
Now, end user who wants to signup/login for @domain3.tld, need to go to email.domain3.tld/webmail/, as well as for @domain2.tld, go to email.domain2.tld/webmail/. Users for @domain1.tld, need to go to www.domain1.tld/webmail/
5. Do MTA integration
Do the necessary MTA integration with reference to your MTA on the server (Qmail/Sendmail/Postfix/Exim).
6. Set up POP3 and Outgoing-SMTP service via xinetd
Set up the POP3 and Outgoing SMTP service using xinetd to allow sending and receiving emails from/to email clients such as Outlook .
Reference :