System Requirements

You can use Dr.Web for UNIX Mail Servers on a computer that meets the following requirements:

Component

Requirement

Platform

CPU with the Intel/AMD architecture and command system are supported: 32-bit (IA-32, x86); 64-bit (x86_64, x64, amd64).

Hard disk space

At least 1 GB of free disk space on a volume where the Dr.Web for UNIX Mail Servers directories are located.

Operating System

GNU/Linux (kernel 2.6.37 or newer and library glibc 2.13 or newer), FreeBSD or Solaris for Intel x86/amd64 platforms.

For systems operating on 64-bit platforms, support of 32-bit applications must be enabled (probably, additional libraries must be installed for this, see below).

Operation system must support the PAM authentication mechanism.

For the correct operation of the Dr.Web Firewall for Linux component, OS kernel must be built with inclusion of the following options:

•CONFIG_NETLINK_DIAG, CONFIG_INET_TCP_DIAG;

•CONFIG_NF_CONNTRACK_IPV4, CONFIG_NF_CONNTRACK_IPV6,
CONFIG_NF_CONNTRACK_EVENTS;

•CONFIG_NETFILTER_NETLINK_QUEUE,
CONFIG_NETFILTER_NETLINK_QUEUE_CT, CONFIG_NETFILTER_XT_MARK.

The set of required options from the specified list can depend on the used OS distribution kit.

Tested operating system distributions are listed below.

Other

The following valid network connections:

•Valid Internet connection to enable updates for virus databases and Dr.Web for UNIX Mail Servers components.

•When operating in central protection mode, connection to the server on the local network is enough; connection to the Internet is not required.

Linux distribution name	Versions	Platforms
Astra Linux Special Edition (Smolensk)	1.5	x86_64
CentOS	6.9, 7.4	x86, x86_64
Debian	7.11, 8.10, 9.3	x86_64
Fedora	27	x86, x86_64
Red Hat Enterprise Linux	7.4	x86_64
SUSE Linux Enterprise Server	11 SP4, 12 SP3	x86_64
Ubuntu	14.04, 16.04	x86_64

Other GNU/Linux distributions that meet the above-mentioned requirements have not been tested for compatibility with Dr.Web for UNIX Mail Servers but may be supported. If a compatibility issue occurs, contact technical support on the official website at https://support.drweb.com/request/.

•For CentOS, Debian, Fedora, Red Hat Enterprise Linux, Ubuntu on the platform x86_64, the package that enables support for 32-bit applications (libc6-i386 or glibc.i686, depending on OS).

•SpIDer Gate can have conflicts with other firewalls installed in your operating system (such as Shorewall and SuseFirewall2 in the SUSE Linux Enterprise Server OS and FirewallD in the Fedora OS, CentOS, RedHat Enterprise Linux). The sign of conflict is message about the error of SpIDer Gate with a code x109 or message about the error of Dr.Web Firewall for Linux with a code x102. Methods to resolve a conflict are described in the section “Known Errors” for errors x109 and x102 respectively.

•In case if the used OS includes the version of NetFilter less than 1.4.15, SpIDer Gate may operate incorrectly. This problem is related to the internal error of NetFilter, and looks like as follows: after disabling SpIDer Gate, the network connections are broken and cannot be re-established. If you face this problem, it is recommended that you upgrade your OS to a version that includes NetFilter 1.4.15 or above. The ways to resolve the problem are described in the section “Description of known errors”.

For the integration of Dr.Web for UNIX Mail Servers with MTA in the mode of the plug-in filter, any mail server that supports interfaces of integration with external spam and anti-virus filters must be installed (Milter, Spamd, Rspamd). For example, MTA from the following list can be used: Sendmail, Postfix, Exim.

MTA that do not support the integration interfaces Milter, Spamd, and Rspamd can be integrated with the product via the interface of anti-virus scanning Clamd, via a direct connection to the Dr.Web ClamD anti-virus scanning component (it is possible that MTA will need an additional integration module to be installed and configured). This integration mode does not use the Dr.Web MailD component, so it does not scan email messages for spam and does not allow to repack email messages if any threats are detected. All actions aimed at processing of an infected email message are transferred over to a mail server, which gets the result of scanning of the email message for threats.

The transparent proxy mode allows to integrate the product for the anti-virus and anti-spam scanning of email messages between MTA and MDA or between MDA and MUA transparently for them (integration into the data exchange channel via the protocols SMTP, POP3, IMAP is performed). This mode does not require anything from MTA, MDA, and MUA.

By default, Dr.Web for UNIX Mail Servers does not support SELinux. In addition, Dr.Web for UNIX Mail Servers operates in reduced functionality mode in the GNU/Linux systems that use mandatory access models (for example, in systems supplied with the PARSEC mandatory access subsystem that appends different privilege levels to users and files).

If installation of Dr.Web for UNIX Mail Servers is required for systems with SELinux (as well as for systems that use mandatory access models). It is necessary to execute additional settings of a security subsystem so that Dr.Web for UNIX Mail Servers operates in full functionality mode. For details, refer to the section Configuring Security Subsystems.