5.0.2 MetaDefender Email Gateway Security release

August 10, 2020

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

New & Improved

Nginx log rotation option

MetaDefender Email Gateway Security can now be configured to rotate Nginx logs. For details see 4.1. Registry configuration.

Remove attachments option

When Handling of the email in a rule is set to Delete blocked contents or Deliver blocked contents, Email Gateway Security provides customization options what attachments to be removed (regardless of scan result).

For details see 4.4. Policy.

Logging Quarantine events

Logging of the Quarantine actions have been improved to cover the following events:

1. The user visits the Quarantine page,

2. The user selects an email from the list,

3. The user does Pin / Unpin email,

4. The user initiates to Views raw email,

5. The user initiates to Download email,

6. The user initiates to Delete email,

7. The user initiates to Forward email,

8. The user initiates to Release email,

9. The user initiates to Rescan email.

Improved Dashboard Details

The Details views on the Dashboard support two new functions:

1. The list can be ordered by the entry labels (alphabetic) or by the numeric values (numeric) and

2. The number of displayed items can be configured (10-25-50-100).

Product hardening guide

The documentation was appended with the [MAIL4] 4.11. Hardening chapter. In this document you can learn how to reduce the vulnerability surface of the product.

Email processing priority

Email Gateway Security now supports High, Normal and Low priority levels when processing emails.

For details see 4.4. Policy.

Raw HTML disclaimer editor

Email Gateway Security now supports a raw HTML editor for disclaimers. In this view it is possible to edit the HTML markup of the disclaimer.

For details see 4.4.1. Disclaimers.

Fixed

SMTP server could return ‘421 temporary error, please try again later’

In certain scenarios the SMTP server could return a ‘421 temporary error, please try again later’ failure after the DATA command. This has now been resolved.