Lightmeter 1.9: Seeding the network

Lightmeter Oct 4 2021 Share

Note: Version 1.9.1 is the latest version of this release if you use binaries (not Docker) get them at the Gitlab registry. 1.9.1 includes a fix in the data cleanup process affecting large databases. More details on the issue here.

63 Merge requests went into this release. Check the Roadmap to see what features are coming next.

Skip to ? Download

Note that Lightmeter is still in early development and intended for small scale deployments. Known issues are documented in README (and there’s one fewer thanks to a fix included below ?).

Fixes and conveniences

This release includes is a grab-bag of minor improvements, four of them requested by community members. Thanks a bunch to Oliver, Chris, and Stephen for spotting issues, sharing redacted logs, and testing the fixes. Keep it coming!

Peer network lift-off

Core development this cycle has focused on building an exciting new peer network system into Lightmeter, which is the foundation for upcoming Lightmeter 2.0 and future mailops automation features. We pre-announced these changes last week — go ahead and read that if you didn’t already (opens in a new tab).

As that announcement explains, today’s release introduces the sharing of certain data, and to prevent abuse requires accepting some Terms of Service. To avoid participating in that system (and the features which will use it), you can stay on Lightmeter 1.8.2, or wait until a future release which includes the option to disable it.

Screenshot of About menu,View sent Signals and get involved

What’s new?

  1. Allow admins to change their account e-mail and name via the command line
  2. Allow logs to be compressed by bzip2 (.bz2) — thanks to Oliver Mueller for requesting the feature ?
  3. To make more efficient use of disk space, logs older than 3 months are deleted from the Lightmeter database (no longer a “known issue”! ?).
  4. Fix obtaining the most recent log lines from an existing workspace, which could cause duplicate connection stats
  5. Introduce a filesystem watcher that identifies when a synchronization is finished, and in case the log files do not yet exist (not yet synchronized), controlcenter waits until files are completely synchronized, instead of exiting with an error.
  6. Add monitoring of deliveries by postfix/virtual
  7. Priority of RBL insights was downgraded to “OK”
  8. Remove junkmailfilter yellowlisting and nobl RBL — thanks to Chris for reporting the issue ?
  9. Remove RBLs which were functioning as allowlists (instead of blocklists)
  10. Include inbound messages in the “Mail inactivity” check — thanks to Stephen Sharp for reporting the issue ?
  11. Assign the mail inactivity insight a priority of “OK” and prevent sending notifications — thanks again to Stephen!
  12. Make search fields in the message detective case insensitive
  13. Better success/error messages for the settings page and user insights ratings
  14. Show only “Active” Insights by default, instead of all.
  15. Remove outdated Bintray hosting link from the README page

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

Get involved

Join us in making email peaceful and transparent — request or add what you’re missing to make your own mail server steadfast and efficient:

Go to the GitLab repo, fork it, build it, and submit your first pull request (there are many open issues to choose from if you’d like inspiration, including some quick wins). And if you get stuck at any point, drop by the forum, the Fediverse, Telegram, Twitter, or, of course, email ??

Supported by

This project has received funding from the European Union’s Horizon 2020 research and innovation programme within the framework of the NGI-POINTER Project funded under grant agreement No 871528.

NGI Pointer logo and EU flag symbol

Comments are closed.