Release candidate for Lightmeter 1.7

Lightmeter May 14 2021 Share

This is an early release of the upcoming Lightmeter Control Center 1.7.0. It provides an opportunity to test the latest changes before the final release scheduled for next week.

Please check old issues that affect you and are reported as fixed, as well as any new features, and also existing features for regressions.

Changes for testing

Message detective: conveniently determine the fate of a given email using the web-ui.
- Search using “Sender address”, “Recepient address” and “Time interval”.
- Key information shown is whether the message was delivered successfully, when, and if not, why not.
- Lightmeter admin can choose to make this page available for unauthenticated users, by enabling the it on the “Settings” page and make this info retrievable by users independently.
- If delivery for a message has failed, users can choose to escalate the problem and generate an Insight for the admin to investigate further.
- The number of consecutive accesses to unauthenticated endpoints is limited and only one insight will be generated per search result.
Make workspace volume part of the Dockerfile, making discoverability easier (as required by Plesk for instance)
Add env variable LIGHTMETER_LOG_FILE_PATTERNS=mail.log:mail.warn to allow user to pass custom postfix log filename patterns
Further improvements to postfix log parsing, fixing crash on handling some log files
Update go-sqlite3 to latest version

The full list of merge requests and commits is on GitLab.

How to test

The best way to test this Release Candidate is to use it as you normally use Control Center, in a non-critical environment. Known issues with this release are documented in the README.

Upgrading

Upgrading to an RC release is the same as for any other Control Center release.

Downgrading is also supported, but because downgrading depends upon features which may not yet be stable, successful downgrading should not be relied upon.

Testing specific features

Features which are user-facing can be easily tested using the Web-UI — see the associated GitLab issues for the expected behaviour and screenshots (sometimes) of how they are intended to look.

Where back-end changes affect a particular component (such as Internationalisation, parsing, etc.), deliberately using functionality which depends on those components provides good opportunities to test for regressions.