Installing from RPM package

Introduction

You can download AfterLogic MailSuite Pro from download page, or run the following command in command prompt of the system you deploy the package on:

wget http://www.afterlogic.com/download/afterlogic-mailsuite-pro-7-x64.tar.bz2

You will need to extract the package:

tar xvjf ./afterlogic-mailsuite-pro-7-x64.tar.bz2

The file you get from archive will have a name like afterlogic-7.7-8pro.x86_64.rpm, we'll use that name in subsequent examples, it might vary between releases but the instructions still apply.

Checking prerequisites

First of all, make sure you're running 64-bit edition of CentOS Linux 7.*. While the product might run on other Linux distributions, that's not guaranteed, you'll be doing that at your own risk. 32-bit systems are not supported.

Since the product includes mailserver components, it's important to make sure you don't have any other mail server software running. To confirm that standard ports used by SMTP, POP3 and IMAP protocols are not taken, you can run the following commands, in any order:

telnet localhost 25
telnet localhost 110
telnet localhost 143

Getting "Connection refused" message means things are fine and you can proceed. But if you get a response from some mail server (Postfix, Dovecot, Courier, Exim, etc.) you will need to uninstall it first. For example, if you get response from Postfix on port 25, remove it as follows:

yum remove postfix

Note that even though MailSuite Pro has its own web server, presense of Apache listening to port 80 is not an issue, as MailSuite Pro also uses a different port 8100.

Installing the package

Before setting up the product, you might want to install its dependencies:

yum install wget spamassassin lsof bzip2 libjpeg-turbo libpng ntpdate compat-db47 libXpm libXrender libXext pcre2

Then you can install the package itself:

rpm -ivh afterlogic-7.7-8pro.x86_64.rpm

There is an alternative way, which doesn't require installing dependencies manually, and the installation can be done using a single command:

yum install afterlogic-7.7-8pro.x86_64.rpm

In this case, output is less verbose though.

Administration

Once the installation is completed, you might want to check that mail services are actually running, by checking access with telnet on ports 25, 110 and 143 as shown previously. If services couldn't start for some reason, e.g. due to some port blocked, you can restart services using the following command:

/etc/init.d/afterlogic.rc restart

To log into adminpanel, use your system IP address or domain name, with 8100 port specified and adminpanel directory name appended, for example http://123.45.67.89:8100/adminpanel and use mailadm/12345 credentials. Standard port 80 should work as well, for example http://123.45.67.89/adminpanel

The first thing to do once you log into adminpanel is to enter your license key. Until that's done, no other features will be unlocked in adminpanel.

Once the license key is in place, you should be able to add domains, create user accounts, modify interface settings and configuration options, etc.

Firewall setup

If you encounter issues when trying to access the installation from web browser, make sure the firewall is disabled.

Running the following commands should help (in CentOS Linux 7.*):

systemctl stop firewalld
systemctl disable firewalld

Antivirus update

During the installation process, ClamAV antivirus database update is retrieved. Updates also will be performed automatically from time to time.

If you may need to update antivirus database manually, that's done by running the following command:

/opt/afterlogic/bin/freshclam

Hostname setup

By default, Exim SMTP server has localhost set for hostname and 127.0.0.1 for IP address, be sure to set actual hostname there to prevent from treating outgoing mail as spam by recipients' servers, actual IP needs to be supplied as well for server to work.

To do that, set primary_hostname and interface parameters in /opt/afterlogic/etc/exim.cnf file. You can find detailed information on this here.

After modifying the configuration files, restart services as shown above.