Title
Create new category
Edit page index title
Edit category
Edit link
Prerequisites
Minimum hardware
All feature plans of Email Gateway Security were verified to be able to run on this minimum hardware. The performance may, however, fall ways below the expectations on it.
For details about feature plans see Installation/Licensing.
CPU | RAM | SSD | NIC |
|---|---|---|---|
6 Cores | 32 GB DDR4 | 256 GB | 1 GbE |
Please note that this hard disk space is only enough for installing MetaDefender Email Gateway Security and for very limited operation.
Quarantine and permanently failing emails (especially with large attachments) may consume huge disk volumes.
For performance reasons it is not recommended to use HDD instead of SSD.
Standalone edition
This section applies to Email Gateway Security standalone edition only. For details see Installation/Licensing.
CPU | RAM | SSD | NIC |
|---|---|---|---|
4 Cores | 4 GB DDR4 | 16 GB | 1 GbE |
Networking
Ports
The following ports must be accessible for the product to work properly:
Direction | Service | Default Port |
|---|---|---|
Inbound | SMTP service | 10025 |
Inbound | Web Management Console and REST interface | 8058 |
Outbound | MetaDefender Core (in case of being integrated to MetaDefender Core; for details see Server profiles) | 8008 |
Outbound | MetaDefender Vault (optional; in case of being integrated to MetaDefender Vault; for details see Server profiles) | 8010 |
Outbound | SMTP destinations | 25 or 487 |
Inbound / Outbound | Shared database for Scalable Deployment | 8060 |
When Email Gateway Security is deployed in the scalable mode, then the shared database port must be available inbound on the primary instance, and outbound on all the secondary instances.
For details about the shared database see Scalable deployment, Scalable deployment related registry configuration and Scalable deployment operation.
For details how to change port values see Configuration/Registry configuration and Configuration/Settings.
External services
The following services and URLs must be accessible to the product for it to work properly
Service | Client | Notes |
|---|---|---|
Email Gateway Security | Upgrade service for processing engine (anti-malware, CDR, etc.) updates. | |
Email end client (e.g. Outlook, Thunderbird, etc.) | For the proactive anti-phishing time-of-click analysis feature. | |
Email Gateway Security | Multiscanning, Deep CDR and Proactive DLP services in case of being integrated to MetaDefender Cloud. For details see Server profiles. | |
Email Gateway Security | Only in case if anti-spam feature is licensed. |
Software
Operating system
Distribution | Version | Bitness |
|---|---|---|
Microsoft Windows | 10 | 64 bit |
Microsoft Windows Server | 2012 / 2012 R2 / 2016 / 2019 | 64 bit |
Supported browsers
One of the following desktop browsers is required to use the Web Management Console:
Latest Chrome version
Latest Firefox version
Latest Microsoft Edge version
3rd party frameworks or components
Name | Version | Notes |
|---|---|---|
Microsoft .NET Framework | 4.5 or newer | Required |
Directories
This section contains references to directories used by Email Gateway Security.
In further sections of this user guide the directory reference is used instead of the actual directory to refer to locations on the system disk.
Everything, except logs, is placed under the installation folder.
Directory reference | Directory path |
|---|---|
Installation folder | C:\Program Files\OPSWAT\Metadefender Email Security |
Event log files | C:\Windows\System32\WinEvt\Logs |
Recommended MetaDefender Core and engine versions
Component | Recommended version | |
|---|---|---|
MetaDefender Core | Latest | |
FileType | engine | Latest |
Archive | engine | Latest |
Archive | database | Latest |
Deep CDR | engine | Latest |
Deep CDR | database | Latest |
Proactive DLP | engine | Latest |
Proactive DLP | database | Latest |