System Requirements and Compatibility
•List of Supported Operating System Versions
•Additional Packages and Components
•Compatibility with Security Subsystems
You can use Dr.Web for UNIX Mail Servers on a computer that meets the following requirements:
To ensure the correct operation Dr.Web for UNIX Mail Servers, open the following ports:
List of Supported Operating System Versions
For other GNU/Linux versions that meet the abovementioned requirements full compatibility with Dr.Web for UNIX Mail Servers is not guaranteed. If a compatibility issue occurs, contact technical support.
Additional Packages and Components
Python3.6+ package is required for integration with the CommuniGate Pro mail server.
•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, Red Hat 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.
•If the used OS includes the version of NetFilter less than 1.4.15, SpIDer Gate can 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 “Known errors”.
Dr.Web for UNIX Mail Servers requires a mail server (MTA) to be installed.
•For the integration of Dr.Web for UNIX Mail Servers with MTA in the mode of the plug-in filter, the mail server must support interfaces of integration with external spam and anti-virus filters (Milter, Spamd, Rspamd). For example, MTA from the following list can be used: Sendmail, Postfix, Exim, CommuniGate Pro.
•MTA that do not support the integration interfaces Milter, Spamd, and Rspamd can be integrated with Dr.Web for UNIX Mail Servers 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 Dr.Web for UNIX Mail Servers 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 requires MTA and Dr.Web for UNIX Mail Servers to be installed on the same host.
•The SMTP proxy mode is a particular case of Dr.Web for UNIX Mail Servers integration with MTA in the mode of the plug-in filter (for example, Postfix) where MTA is set to routing of the received messages (works like a mail relay).
•The Dr.Web Anti-Spam component is not supported for ARM64 and E2K architectures.
Compatibility with Security Subsystems
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.