{"id":3372,"date":"2016-07-14T12:50:12","date_gmt":"2016-07-14T12:50:12","guid":{"rendered":"http:\/\/www.kevinmaschke.com\/en\/?p=3372"},"modified":"2017-03-01T12:30:20","modified_gmt":"2017-03-01T12:30:20","slug":"zimbra-collaboration-8-6-prerequisites","status":"publish","type":"post","link":"https:\/\/www.kevinmaschke.com\/en\/zimbra-collaboration-8-6-prerequisites\/","title":{"rendered":"Zimbra Collaboration 8.6 – Prerequisites"},"content":{"rendered":"

As I explained in my first entry<\/a> about Zimbra Collaboration, I’m going to dedicate a few articles to explain its\u00a0prerequisites, installation and configuration, and to continue with this series, I’m going to dedicate this part to the prerequisites that are necessary to install Zimbra Collaboration 8.6.<\/p>\n

Dependencies for Zimbra Collaboration<\/h2>\n

First we have to install some dependencies that are necessary to be able to run and use Zimbra<\/strong>. To do this, we use the following command:<\/p>\n

sudo apt-get install libgmp10 libperl5.18 libaio1 unzip pax sysstat sqlite3 wget<\/pre>\n
Once the dependencies are installed, we have to configure the servers network.<\/p>\n
Network Configuration<\/h2>\n
As in any server, we will aim for a manual network configuration. It’s preferable to have a static IP<\/strong> instead of it being assigned by DHCP, since we want to avoid the IP from changing\u00a0after some time or any restart and lose connection to the server or the mail to stop working until we fix the issue. It is also possible to configure the DHCP server to always assign the same IP to the server, but the recommended way is to use a manually assigned IP.<\/p>\n
Hostname<\/h3>\n
First we’ll review the \/etc\/hostname<\/code>\u00a0file. This file includes the name of the machine, the name we want the server to have. It does only contain one name with which the server should easily be identified<\/strong> (especially if you have a large number of servers). If the server is only going to be used as a mail server and for one domain or customer, something simple as “Mail<\/em>“, “MailServer<\/em>“, or “mail.domain.com<\/em>” can be used. To review and edit this file we can use either VIM or NANO as text editors. I personally am more used to VIM:<\/p>\n
sudo vim \/etc\/hostname\r\nMailServer<\/pre>\n
Hosts<\/h3>\n
Once we’ve set the name of the server, we’re going to edit the \/etc\/hosts<\/code> file. Do not confuse this file this the previous Hostname. While in the first one we set the name of the server, in this one we set which names (domains) this server will respond to<\/strong>. In this file we’ll put the domains with which the server will be accessible. We’ll open the file with:<\/p>\n
sudo vim \/etc\/hosts<\/pre>\n
And we will find something similar to the following:<\/p>\n
127.0.0.1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 localhost\r\n127.0.1.1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 MailServer.example.com\u00a0\u00a0 MailServer<\/pre>\n
Under this we will probably also find some lines for IPv6, but we will ignore these since they currently do not affect us. Just under the first two lines and before the IPv6 dedicated lines, we will add the IP and the domain names we want the server to respond to:<\/p>\n
192.168.1.2\u00a0\u00a0 mail MailServer mail.MailServer.com mail.dominio.com<\/pre>\n
If the server has multiple IPs, these will be added in individual lines.<\/p>\n
Manual Network \/ IP Configuration<\/h3>\n
Once we have modified the Hosts and Hostname files, we’ll manually set the IP configuration<\/strong>. To do this, we have to edit the \/etc\/network\/interfaces<\/code> file:<\/p>\n
sudo vim \/etc\/network\/interfaces<\/pre>\n
Once we open this file, if we have installed Ubuntu using a DHCP network configuration, we’ll see that there will already be quite some content similar to the following:<\/p>\n
# This file describes the network interfaces available on your system\r\n# and how to activate them. For more information, see interfaces(5).\r\n\r\n# The loopback network interface\r\nauto lo\r\niface lo inet loopback\r\n\r\n# The primary network interface\r\nauto eth0\r\niface eth0 inet dhcp<\/pre>\n
This configuration should be enough for any workstation or test server, but for a server that will be used in a production environment, we will have to set a manual configuration. To do this, we will comment out the following two lines:<\/p>\n
#auto eth0\r\n#iface eth0 inet dhcp<\/pre>\n
And add the following lines at the end making sure that the IPs are correct and part of our network:<\/p>\n
# Static IP\r\nauto eth0\r\niface eth0 inet static\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 address 192.168.1.2\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 netmask 255.255.255.0\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 gateway 192.168.1.1\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 dns-nameservers 8.8.8.8<\/pre>\n
dns-nameservers 8.8.8.8<\/code>\u00a0can be changed to any preferred DNS server. In this case we use Googles’ DNS server.<\/p>\n
Once we’ve finished all the changes, we can apply them. The easiest way to do this is to restart the server. This can be done by using one of the following commands:<\/p>\n
sudo reboot<\/pre>\n
Or<\/p>\n
sudo shutdown \u2013r now<\/pre>\n
IMPORTANT<\/strong><\/span>: It’s important to review the modifications and make sure they are all correct. If there is any mistake, we may lose the connection to the server with the restart and will have to use other ways that SSH (such as vSphere or some kind of KVM) to gain access again and fix the mistake.<\/p>\n
And with this we finish the first part of the prerequisites to install Zimbra Collaboration 8.6. In the next part we will go over how to install and configure DNSMasq and integrate it with our server so that Zimbra can make use of it.<\/p>\n","protected":false},"excerpt":{"rendered":"
As I explained in my first entry about Zimbra Collaboration, I’m going to dedicate a few articles to explain its\u00a0prerequisites, installation and configuration, and to continue with this series, I’m going to dedicate this part …<\/p>\n","protected":false},"author":1,"featured_media":3477,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[207,410],"tags":[639,641,643,657,645,659,647],"class_list":["post-3372","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-linux-en","category-guides","tag-email","tag-ews-en","tag-imapsync-en","tag-installation","tag-open-source-en","tag-prerequisites","tag-zimbra-en"],"acf":{"book_cover":null,"special_featured_image":null},"_links":{"self":[{"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/posts\/3372","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/comments?post=3372"}],"version-history":[{"count":0,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/posts\/3372\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/media\/3477"}],"wp:attachment":[{"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/media?parent=3372"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/categories?post=3372"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kevinmaschke.com\/en\/wp-json\/wp\/v2\/tags?post=3372"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}