Version 5.4.2

New & improved

Core and Cloud hash lookup

To shorten email processing time Email Gateway Security can be configured to perform hash lookups to MetaDefender Core and MetaDefender Cloud (whatever is set as the MetaDefender Core type server profile for the rule).

If the email header, body or attachment is found by the hash, then it won't be sent to MetaDefender Core / Cloud for scanning or processing. This way the scanning and processing time can be saved.

MetaDefender Core / Cloud will return the cached scan results and the cached processed version of the header, body or attachment.

For further details see Hash lookup subsection in Configuration/Policy/Scan and Configuration/Email History/Malware scan details.

More precise date/time format

Processing history blocks show more precise date and time in Audit > Email History, Audit > Refused Emails and Quarantine.

Before it would have been Sep 21, 2021 (1 day ago) in the example below, now it is:

Fixed

SMTP server hanged on SSL on connect

Due to a bug in the SMTP watchdog, under certain circumstances Email Gateway Security's SMTP server was hanging on SMTP over TLS connection attempts (clear text SMTP and StartTLS connection attempts were not affected).

Statistics duplicated on reprocessing

When emails were re-processed or re-scanned due to MetaDefender Core scan timeout, not available, etc., statistics duplicated in certain cases.

Emails grew much larger after processing

Due to a bug in our TNEF parser under certain circumstances emails could grow drastically in size during processing in some cases (when the size of the processed email exceeded the maximum allowed email size) causing failure when sending these emails.

Updated

OpenSSL was updated to 1.1.1l.

Qt was upgraded to 6.1.3.

Known issues

When hash lookup is enabled, the processed file will be served from the cache until the cache expires. This will happen even if the security rule has changed since the caching and the new rule would result in a new processed file.

Example:

1. Hash lookup is enabled for HTML email bodies
2. CDR is configured with HTML -> HTML conversion
3. An email is scanned, CDR applied on the HTML body
4. The end result HTML body file cached for later lookup
5. CDR is configured with HTML -> text conversion
6. An email is scanned with the same body as before
7. Hash lookup finds the previous body file in the cache
8. The HTML body is returned, text conversion is not applied