This article revolves around an effort to make Zarafa Server environment much secure and stable. We will discuss upon an important question that Zarafa Server allows user to run WebApp on a different WebServer? However most of our readers must be thinking that why one needs to run a WebApp on an individual WebServer. It is not necessary to explain that an email server is a very crucial application for an organization. It is solely responsible for effective and fast means of communication. Hence it is top priority of an administrator to keep the application safe and in well functioning condition. But there are numerous conditions when server application fails due to following external reasons:
- The DOS attack may hamper the performance of Zarafa Server; it is mostly done by dedicated hacker who launches such type of activity in an organized manner.
- The old and common way of hacking where the hacker hacks the system and get the authority to access vulnerable files and folder.
Now how the creation of separate server will help you to overpower the abovementioned threats. In former situation when user runs a WebApp on an individual server, only that server will be affected by the DOS’ing process. The main Zarafa environment will remain intact and allows you to tackle the issue without halting the normal flow of the work. In the later scenario also the hacker will get access of the server which is situated on different or separate environment completely de-attached from the main Zarafa server. Even though the hacker get the access of the internal ports of the internal server but nothing to worry about, because those servers are already guarded in a safe and secure manner.
How to perform the activity?
The following mentioned step allows user to create a separate server that will enhance the security aspect of the Zarafa server:
Install the Zarafa packages with Apache server:
- Php5-mapi
- zarafa-client
- zarafa-libs
- zarafa-webapp
- zarafa-contacts
Update the /etc/zarafa/webapp/config.php file like define(“DEFAULT_SERVER”,”http://192.154.1.2:236”)
This configuration will allow Zarafa server to connect unencrypted at 192.154.1.2
Enable following apache modules as defined in the zarafa-webapp apache configuration:
- expire_module
- headers_module
- setenvif_module
- deflate_module
Conclusion – The abovementioned is the guide lines which will help the Zarafa Server administrators to ensure the security aspect of the application. However these steps are purely for the skilled technical specialists who are completely aware of every aspect of Zarafa Server.