Momentum 5.3.0 Changelog
Last updated July 2026
This section will list all of the major changes that happened with the release of Momentum 5.3.0. Depending on installation type, all changes may not be applicable
| Type | Ticket | Description |
|---|---|---|
| Feature | — | spamassassin module is a supported SpamAssassin client (SPAMC protocol over spamd), replacing the legacy, Sieve-based spamc module. |
| Feature | I-1064 | Added support for license signatures using ECDSA P-256 with SHA-256. |
| Feature | I-1141 | Added an optional limit query parameter to the /stats/queues/mailq HTTP API, controlling how many binding/domain pairs are ranked and returned. |
| Feature | I-1152 | Added new fail all and fail all quiet console commands, plus optional --meta / --header filtering on other fail commands to selectively fail queued messages by metadata or RFC822 header match. |
| Feature | I-1172 | Added the ec_spool_check utility, which performs a read-only scan of a spool directory and reports metadata, body, and orphan-marker failures without driving traffic through Momentum. |
| Feature | I-1214 | Removed msys-nodejs RPM from the Momentum bundle, to be replaced with the 3rd-party nodejs package. Node.js LTS 24+ must be installed separately from the system or a vendor repository. |
| Feature | I-1216 | Added the log_hires_timestamp option to emit microsecond-resolution timestamps in the mainlog, bouncelog, rejectlog, paniclog, custom logs, chunk logs, and message generation logs, preserving event ordering when reading multiple log files together. |
| Feature | I-1225 | Added optional --meta / --header filtering to the reroute queue console command, to selectively move queued messages by metadata or RFC822 header match. |
| Feature | TASK-144964 | The tls_ec_curve_names option now accepts a colon-separated list of curve or TLS group short names in preference order, instead of a single curve. |
| Feature | TASK-198522 | New DNS configuration options to rate-limit MX lookups, preventing query bursts from overwhelming the DNS infrastructure. |
| Fix | TASK-227757 | ha_proxy_client now re-resolves a hostname-based ha_proxy_server during each health check, so backend IP changes are picked up automatically without restart. |
Was this page helpful?