Universal Messenger 7.57.4 (EN)

Installer

The installation is now possible on Windows without administrator permissions.

In the interactive installation, obtaining administrator permissions can easily be skipped. In an automated installation, it can be skipped by setting the response file variable skip_admin_permissions:

This variable can also be passed as an argument when calling the installer:

Backoffice

In the newsletter detail view of the newsletter archive, the missing button to hide bot interactions has been added in the Link & Click Overview section.

The warning message when deleting a newsletter has been expanded to make the consequences of the deletion clearer.

Bounce Processing

When using SendGrid, "dropped" type bounces are now treated as hard bounces.

Core Scripting Engine

A race condition related to OAuth in the HTTP client has been fixed.

An email in the form of a MimeMail object can now be sent directly without tracking the sending process.

Device-Detector App

The Device-Detector app for identifying email clients and browser types has been updated.

Documentation

The installation of UM in Tomcat 10 on a Debian installation has now been described in the installation manual.

CSP Compatibility Improvements for UM Forms

CSP (Content Security Policy) is a security mechanism that defines loading and execution policies for a website via specific HTTP headers. Modern web servers and CMSs often apply strict CSP rules by default. The loading logic of UM forms, which is embedded via JavaScript snippets, has been revised to fully support the use of CSP headers.

• Structure without Inline Scripts: The new structure of the loader snippets fully avoids inline scripts, complying with modern CSP policies and enhancing the security of the forms.

• Internal Adjustments without Inline Styles: Internal adjustments have been made to avoid inline styles as well. This especially applies to HTML elements that should initially be hidden, such as the error message box.

• Improvements in Form-Specific JavaScript Code: The logic for form-specific JavaScript code has been revised to completely eliminate the use of eval or the new Function construction.

Backward Compatibility

The old snippets remain functional and provide a transition solution for existing implementations.

New DatePicker in UM Forms

For date fields, the HTML5 standard date picker of browsers is now used, replacing the previous proprietary jQuery date picker.

If the previous jQuery date picker should still be used, this can be defined in a properties file:

Updates of Various Libraries

• Log4J 2.24.3

Discontinuation of Support for Tomcat 7, 8, and 9 Starting from Release UM 7.59

Event Management App