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 enable the correct operation of 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 our technical support.
Additional Packages and Components The 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 SUSE Linux Enterprise Server and FirewallD in Fedora, CentOS, Red Hat Enterprise Linux). The conflict manifests itself in the SpIDer Gate error message with code x109 or the Dr.Web Firewall for Linux error message with code x102. Methods to resolve the conflict are described in the section Appendix F. Known Errors, see errors x109 and x102. •If the OS includes NetFilter earlier than 1.4.15, SpIDer Gate can operate incorrectly. This issue is related to the internal error of NetFilter, and looks like as follows: after disabling SpIDer Gate, the network becomes unstable. If you encounter this issue, it is recommended that you upgrade your OS to a version that includes NetFilter 1.4.15 or later. The ways to resolve this issue are described in the Appendix F. Known Errors section. Dr.Web for UNIX Mail Servers requires a mail server (MTA) to be installed. •To integrate Dr.Web for UNIX Mail Servers into an MTA in a plug-in filter mode, the mail server must support interfaces for integration with external spam and anti-virus filters (Milter, Spamd, or Rspamd). For example, MTA from the following list can be used: Sendmail, Postfix, Exim, or CommuniGate Pro. •MTA that do not support the Milter, Spamd, and Rspamd integration interfaces can integrate Dr.Web for UNIX Mail Servers via the anti-virus scanning interface of Clamd, via a direct connection to the Dr.Web ClamD anti-virus scanning component (it is possible that the 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 threats are detected. All actions of processing an infected email message are delegated to the mail server, which gets the result of scanning 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 in the data exchange channel via SMTP, POP3 and IMAP protocols 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 in the MTA in the plug-in filter mode (for example, Postfix) where the MTA is set to route the received messages (works like a mail relay). •The Dr.Web Anti-Spam component is not supported for ARM64, E2K and IBM POWER (ppc64el) architectures. Compatibility with Security Subsystems By default, Dr.Web for UNIX Mail Servers does not support the SELinux security subsystem. Moreover, Dr.Web for UNIX Mail Servers operates by default in a reduced functionality mode on the GNU/Linux systems that use mandatory access models (for example, on the systems distributed with the PARSEC mandatory access subsystem, which assigns different privilege levels, so-called mandatory levels, to users and files). In case of installing Dr.Web for UNIX Mail Servers on systems with SELinux (as well as on systems that use mandatory access models), it is necessary to additionally configure the security subsystem, so that Dr.Web for UNIX Mail Servers would operate in a full functionality mode. For details, refer to the Configuring Security Subsystems section. |