Recommended firewall setup for Ensim Pro for Linux
The following is the list of ports used by Ensim Pro for Linux that need to be open if the server is installed behind a firewall.
TCP Port Service
20 FTP Data
21 FTP
22 SSH
23 Telnet
25 Sendmail SMTP
53 DNS
80 HTTP
110 POP3
143 IMAP
443 SSL
783 Spamassassin
3306 MySQL
19638 Control panel
UDP Port Service
How to Setup CentOS testing repo
Setting up repos
To install the CentOS testing repo, along with the yum-priorities plugin.
# cd /etc/yum.repos.d
# wget http://dev.centos.org/centos/5/CentOS-Testing.repo
# yum install yum-priorities
The priorities plugin can be used to enforce ordered protection of repositories, by associating priorities to repositories. Packages from repositories with a lower priority will never be used to upgrade packages that were installed from a repository with a higher priority.
How to setup DA with an SSL certificate
If you already have your own certificate and key, then paste them into the following files:
certificate: /usr/local/directadmin/conf/cacert.pem
key: /usr/local/directadmin/conf/cakey.pem
Edit the /usr/local/directadmin/conf/directadmin.conf and set SSL=1 (default is 0). This tells DA to load the certificate and key and to use an SSL connection. DirectAdmin needs to be restarted after this change.
If you also have a CA Root Certificate, this can be specified by adding:
carootcert=/usr/local/directadmin/conf/carootcert.pem
into the /usr/local/directadmin/conf/directadmin.conf file and by pasting the contents of the caroot cert into that file.
Source: http://directadmin.com/
Simple Rules to follow to setup a Mail System
Hostname must not match any domain that is being used on the system. Example, if you have a domain called domain.com and you want to recieve mail on user@domain.com, you must *not* set your hostname to domain.com. We recommend using server.domain.com instead. You must make sure that you add the A record for server.domain.com so that it resolves.
For DirectAdmin
- The hostname must be in the /etc/virtual/domains file.
- The hostname must *not* be in the /etc/virtual/domainowners file.
- The hostname must resolve. If not, add the required A records to the dns zone such that it does.
- The directory /etc/virtual/hostname must exist.. (eg: /etc/virtual/server.domain.com). It must not contain any files
- Any domains that you want to use for email (eg: domain.com) must be in both the /etc/virtual/domains file and the /etc/virtual/domainowners file. The directory /etc/virtual/domain.com must exist and the files /etc/virtual/domain.com/passwd and /etc/virtual/domain.com/aliases exist.
- File permissions for virtual pop inboxes should be (not applicable with Dovecot/Maildir):
/var/spool/virtual/domain.com 770 username:mail
/var/spool/virtual/domain.com/* 660 username:mail
- Make sure that your main server IP has a reverse lookup on it.
Simplifying Setup of User Accounts in Plesk
Before you start signing up new users for your services, you should create account configuration presets, referred to as reseller account templates and client account templates. They will simplify setting up user accounts for new customers. The templates cover all resource usage allotments, permissions and limits that you can define for a user account. There are predefined reseller account and client account templates: You can modify them as required and use them, or you can create your own templates. The default templates cannot be removed.
To create a reseller account template:
1. Go to Resellers > Reseller Account Templates > Create Reseller Account Template.
Click OK to complete creation of a template.
During setup of a new reseller account, you will select the required template and the account will be created and allocated the resources you defined.
To create a client account template:
1. Go to Clients > Client Account Templates > Create Client Account Template.
Click OK to complete creation of a template.
During setup of a new user account, you will select the required template and the account will be created and allocated the resources you defined.
