DJIGZO Email Encryption Gateway

One Time Password (OTP) PDF encryption was added. The OTP can be generated by the recipient after logging into the portal. Email can be encrypted with additional certificates (aka escrow). The PDF reply page and quarantine viewer now support multiple languages (German, English, and Dutch). Messages with encrypted PDFs can be digitally signed. EJBCA integration was added, and certificates can be requested from an EJBCA server. A login page brute-force filter that blocks access for some time for an IP/user was added.

S/MIME setting: "Always use freshest signing certificate". PDF setting "Only encrypt if mandatory". DLP setting "Quarantine on failed encryption". Quarantined emails can now be "released as-is". Number of rows the grid should show per page can be set. Email in the MTA queue can be filtered. The MTA logs are now by default shown in "raw" format. Support for charsets not supported "out of the box" by Acrobat reader. In S/MIME "strict mode", the message is now always handled by the S/MIME handler.

This fixes a problem related to the DLP quarantine queue. A fix was made for GATEWAY-15 (https://jira.djigzo.com/browse/GATEWAY-15). If a message was placed in quarantine because of a DLP violation and the message-id or from header contained a "%" character, deleting the mail from quarantine resulted in an error. This version is only relevant if you are using the DLP functionality and quarantine messages that violate a DLP policy.

The most notable new feature is the inclusion of a Data Leak Prevention (DLP) module, which can be used to automatically scan outgoing email on keywords and regular expressions for sensitive data. S/MIME strict mode was added. Locally generated notifications are now signed. DSN is supported. A workaround was made for non-RFC-compliant SKI support from Outlook 2010.

The virtual appliance now allows you to specify which IP addresses can access the Web Admin login page. A fix was made for the bug that caused the message, "The PDF reply portal no longer attaches the uploaded attachment." This was a regression of a previous bug fix. A fix was made for the bug that caused the message, "The telephone number in the subject should be detected before removing the encryption trigger." The documentation has been updated and improved.