What is the difference between Metadefender Email Security 3.X vs 4.X?
If you are running a previous version of Metadefender Email Security, OPSWAT recommends upgrading to the latest released version of Metadefender Email Security whenever it is practically possible. For users who may be using Metadefender Email Security 3.X, there are significant architectural differences when upgrading to the latest version. To help with the upgrade, the table below compares the functionality between the two generations of the product and provides links to any relevant documentation.
Feature |
Metadefender Email v3.X |
Metadefender Email Security v4.X |
3.X Documentation |
4.X Documentation |
Metadefender Core compatibility |
CORE V3 |
CORE V4.7.0+ |
|
|
|
|
|
|
|
Licensing |
BUNDLED INTO CORE |
STANDALONE |
|
|
Based on count of recipient email addresses |
NO |
YES |
|
|
|
|
|
|
|
Security |
|
|
|
|
Accountability |
SINGLE ACCOUNT |
PER USER ACCOUNT |
|
|
Human Authentication |
GROUP PASSWORD |
PER USER PASSWORD |
|
|
Machine Authentication |
API KEY |
API KEY |
|
|
TLS version negotiation |
TLS 1.0 ONLY |
NEGOTIABLE |
|
|
TLS version customization |
NO |
PLANNED IN V4.3 |
|
|
TLS cipher customization |
NO |
PLANNED IN V4.3 |
|
|
Inbound SMTP over TLS |
NO |
PLANNED IN V4.3 |
|
|
|
|
|
|
|
Access control |
EXPLICIT |
RBAC |
|
|
Role based access control |
NO |
YES |
|
|
User management |
NO |
YES |
|
|
Active directory integration |
NO |
YES |
|
|
|
|
|
|
|
User interface |
BUNDLED INTO CORE |
STANDALONE |
|
|
Dashboard |
BUNDLED INTO CORE |
OWN |
|
|
Dashboard auto refresh |
NO |
CONFIGURABLE |
|
Dashboard > Overview / Settings
|
Email history |
YES |
YES |
||
Scan details in email history |
NO |
YES |
|
4.1 Dashboard (Email details) |
Email history cleanup |
NO |
YES |
|
Dashboard > Email history / CLEANUP
|
Configuration history |
NO |
YES |
|
4.1 Dashboard (Config history) |
Configuration diffs |
NO |
YES |
|
4.1 Dashboard (Config history) |
History auto cleanup |
YES |
YES |
Configuration From Config File (Metadefender.Engine.History.dll.config |
3.4 General settings (Data retention) |
History custom date filtering |
NO |
YES |
|
Dashboard > Email history / FILTER BY DATE Dashboard > Config history / FILTER BY DATE
|
Search keys |
NAME |
MULTIPLE |
Not documented |
|
Full text search |
NO |
YES |
|
|
Policy |
PARTIAL |
YES |
Single workflow |
|
Inventory |
NO |
YES |
|
|
Web based configuration settings |
PARTIAL |
YES |
Some global settings configurable via UI or REST API, others via config files |
|
|
|
|
|
|
Resource management |
|
|
|
|
Core load balancing |
YES |
YES |
Configuration From Config File (Metadefender.Scanner.dll.config) |
|
Core high availability |
YES |
YES |
Configuration From Config File (Metadefender.Scanner.dll.config) |
|
SMTP relay load balancing |
NO |
YES |
|
|
SMTP relay high availability |
YES |
YES |
Configuration From Config File (Metadefender.Email.Engine.Generic.Agent.dll.config > EmailRelayOutHosts) |
|
|
|
|
|
|
Workflow |
|
|
|
|
Security rules |
IMPLICIT |
YES |
|
|
Workflow |
SINGLE |
PER RULE |
||
Email filtering |
NO |
PER RULE |
|
|
Email routing |
SINGLE |
PER RULE |
|
|
Override Core results |
NO |
PER RULE |
|
|
Bypass Core |
NO |
PER RULE |
|
4.2 Security rules (Advanced scan settings) |
Core rule selection |
SINGLE |
PER RULE |
|
|
|
|
|
|
|
Email processing |
|
|
|
|
Scan emails and attachments |
YES |
YES |
||
Sanitize emails and attachments |
YES |
YES |
|
|
Block emails and attachments |
ATTACHMENTS ONLY |
YES |
|
|
Disclaimers |
SINGLE |
PER RULE |
||
Merge fields |
PARTIAL |
PLANNED IN V4.3 |
|
|
Subject rewriting |
PARTIAL |
PLANNED IN V4.3 |
|
|
Custom email headers |
SINGLE |
PER RULE |
||
Scan information headers |
YES |
PLANNED IN V4.2 |
|
|
Retry mechanism |
YES |
YES |
Requires manual monitoring of notifications and folders |
3.4 General settings (Retry settings) |
Handling permanent failures |
MANUAL |
YES |
Manual reprocessing of failed items |
|
|
|
|
|
|
Quarantine |
|
|
|
|
Quarantine location |
BUNDLED INTO CORE |
OWN |
|
|
Quarantine original copy |
GLOBAL |
PER RULE |
||
Email details |
YES |
YES |
|
|
Operations (Release, Forward, Delete) |
PARTIAL |
YES |
Not documented |
|
Batch operations |
GENERAL |
PLANNED IN V4.2 |
|
|
External quarantine |
YES |
YES |
||
Quarantine reports |
YES |
YES |
||
Quarantine report contents |
GENERAL |
SPECIFIC |
|
3.6 Quarantine configuration (Quarantine reports) |
Custom quarantine report schedule |
NO |
PLANNED IN V4.3 |
|
|
|
|
|
|
|
Notification emails |
|
|
|
|
Email threat alerts |
YES |
YES |
4.2 Security rules (Actions for emails with blocked contents) |
|
Service status alerts |
YES |
PLANNED IN V4.3 |
|
|
|
|
|
|
|
SMTP relay |
BUNDLED INTO CORE |
STANDALONE |
|
|
Email flow direction (per deployment) |
ONE-WAY |
BIDIRECTIONAL |
||
TLS configuration |
EXTERNAL TOOL |
BUILT-IN |
||
SPF lookups |
YES |
YES |
3.4 General settings (Sender Policy Framework lookup) |
|
HELO/EHLO domain customization |
NO |
YES |
|
|
|
|
|
|
|
Integration |
|
|
|
|
Microsoft Exchange plugin |
YES |
YES |
||
Cloud (AppRiver, Google Apps, Office 365) |
YES |
YES |
||
|
|
|
|
|
Operation |
|
|
|
|
Monitoring |
LIMITED |
ADVANCED |
Dashboard / Mail Agent |
|
General audit logs |
YES |
YES |
|
|
Configuration audit logs |
NO |
INTEGRATED |
|
4.1 Dashboard (Config history) |
Syslog integration |
LIMITED |
YES |
||
Multiple log destinations |
YES |
YES |
||
Unique message ID |
NO |
YES |
|
|
This article pertains to Metadefender Email Security v4.0.0 or above
This article was last updated on 2017-12-13
ML