Resources and their use are focused in the manual.
Kerio Connect services can be handled in :
Service parameters can be changed upon clicking on :
Kerio Connect allows:
automatic startup — the service is started automatically upon each startup of the server,
manual startup — the service is started by hand upon each startup of the server,
By default, Kerio Connect services listen at all default ports at all IP addresses of their hosts. The IP addresses and ports table allows:
to change port on which the service is running (it is recommended not to change it if not necessary for any reason),
to assign a particular IP address for the port on which the service is running.
The methods suggested above help solve situations where, in addition to Kerio Connect, another server providing the same services is run on the same computer (e.g. another LDAP server, webserver or mailserver).
If this situation occurs, the second method is recommended to be used. This means that for example two different web servers may use standard port 80 at two different IP addresses.[1]
Assignment of IP addresses to ports is not recommended if IP addresses are reserved dynamically, e.g. using DHCP.
In addition to port settings and startup of services, Kerio Connect also allows to edit user access rights to individual services. To edit these settings, go to the Access tab under service settings:
Allows access to the service to be limited to certain IP addresses only (defined in the selected group). List of IP address groups is provided in the menu. If you are not sure how to define the groups, refer to section IP Address Groups.
Detailed access policy for the SMTP service can be set in the section.
This option applies only to the NNTP(S) service where it enables unauthenticated access to an NNTP server. This means that everyone can register to a mailing list with anonymous access.
This option limits the number of concurrent connections to the selected service. Too many concurrent connections may cause the server overload which can subsequently lead to its failure. This is the principal of so called DoS (Denial of Service) attack. Setting the limit for the number of connections therefore helps to prevent the DoS attacks against your server.
When you plan to limit the number of connections, consider the number of server users.
[1] Indeed, it is necessary to reserve an IP address for the same service in another application, that is not used by Kerio Connect.