5.2.2 MetaDefender Email Gateway Security release

March 3, 2021

MetaDefender Email Gateway Security 5.2.2 is a maintenance release focusing on minor improvements and fixes.

New & improved

Improved password protected rescan

When Handling of the email is set to Delete blocked contents under Security Rules / rule / ADVANCED THREAT PREVENTION, password protected attachments are delivered after a successful rescan even if other blocked (e.g. infected) attachments were still there in the email.

For details see 4.4. Policy, 5.3. Quarantine and 5.6. Password protected attachments.

Submit files email by email for scanning

By default Email Gateway Security submits emails to MetaDefender Core on several concurrent threads for scanning. This may cause different components of different emails to mix in the Core queue. Also, this way there may be multiple emails in progress on Core in the same time.

With the new Registry option concurrency_threshold, the number of concurrent threads submitting emails for scanning can be limited.

For details see 4.1. Registry configuration.

New, better editor for HTML disclaimers

Email Gateway Security now has a new disclaimer editor with better capabilities.

For details see 4.4. Policy and 4.4.1. Disclaimers.

Fixed

DLP redaction sometimes was not applied

Even when Send redacted version of blocked files was enabled under Security Rules / rule / DATA LOSS PREVENTION (and the redaction was successful on the MetaDefender Core side), not the redacted version of the HTML email body was delivered under certain circumstances.

For details see 4.4. Policy.

False SMTP server not responding alarm

When Email Gateway Security was not listening on port 25, after enabling the alert for SMTP server not responding under Settings > Alerts & Reports / Email Alerts, logs and email alerts with the message MetaDefender Email Gateway Security SMTP server is not responding were sent.

For details see 4.8. Alert, notification and quarantine report emails.

Raw HTML disclaimer customization problems

The raw HTML version of disclaimers may have been deliberately overridden (tags replaced) by the HTML disclaimer editor.

For details see 4.4. Policy and 4.4.1. Disclaimers.