Version 4.1.3
| Release date | Scope |
|---|---|
| Aug 30th, 2024 | MetaDefender Cloud Email Security 4.1.3 contains enhancements (for SPF check and Syslog functionality) and the ability to scan with MetaDefender Cloud using sandbox |
New Features
Enhanced SPF check
From now on, CES can not only perform SPF checks based on the direct IP address, but also processes the Received entries in the mail header to determine the real sending IP. In the configuration you can list the hosts you want to exclude from SPF processing, for example, the IP address of the MTA in front. MetaDefender Cloud Email Security will then performs SPF checks on the host after the excluded hosts.
This configuration can be done in the IP allowlist section of the Setting/General tab.
SPF lookups are now turned off for customers for MS365 integrations, as Microsoft already handles these checks, simplifying the configuration process.
Show original SMTP server on Email History and Quarantine
Based on the above, the original sender SMTP server will also appear under Email details in the Quarantine and Audit/Email History lists.
Syslog over TLS
Syslog functionality has been extended with the option to encrypt. From this version onwards, it is possible to configure the product to send log data to Syslog using TLS encryption, using the TLS Certificate of the Syslog server, or to use client-side SSL authentication to access the Syslog server.
Please get in touch with OPSWAT to configure syslog features.
Sandbox integration with MetaDefender Cloud
Sandbox technology is also available when scanning with MetaDefender Cloud
Removed Features
MetaDefender Core server profile option removed
From this version MetaDefender Core server profile - as an underlying scanning subsystem - is no longer available in MetaDefender Cloud Email Security. This will be configured - and further maintained - by OPSWAT technical support.
