Maddy
A one-binary mail server learning to behave like production infrastructure.
A side-by-side editorial comparison of Roundcube and Element iOS — release velocity, themes, recent moves, and the top alternatives to consider.
After four years, Roundcube 1.7 lands — and the release stream is otherwise all CVEs
Roundcube maintains two lines in lockstep: 1.6 as LTS and 1.7 as stable, with security fixes released to both on the same day. The vulnerability stream is heavy and varied — stored XSS via an unescaped attachment MIME type (CVE-2026-54432), a pre-auth SQL injection in the virtuser_query plugin, CSS injection through SVG animate, SSRF bypasses via local address URLs, an infinite loop in the TNEF decoder. Version 1.7.0, released in May after almost four years of development, is the only feature release in the window.
Renamed Element Classic, this client now ships one small fix every few months
Element iOS was renamed Element Classic in v1.11.32, and the release log since then reads like a maintenance branch: single-PR releases spaced weeks to months apart, mostly dependency bumps, build-tooling changes and one user-visible change at a time. The one substantive thread is device verification — a permanent disclaimer banner for unverified sessions arrived in 1.11.35, was temporarily disabled in 1.11.37 because users had no way to reset from the verification screen, got the Reset flow wired up in 1.11.38, and was reinstated as mandatory in 1.11.39.
Roundcube maintains two lines in lockstep: 1.6 as LTS and 1.7 as stable, with security fixes released to both on the same day. The vulnerability stream is heavy and varied — stored XSS via an unescaped attachment MIME type (CVE-2026-54432), a pre-auth SQL injection in the virtuser_query plugin, CSS injection through SVG animate, SSRF bypasses via local address URLs, an infinite loop in the TNEF decoder. Version 1.7.0, released in May after almost four years of development, is the only feature release in the window.
The arc is a long-lived webmail codebase paying down structural risk. 1.7.0's headline changes are defensive rather than user-facing: a mandatory public_html/ entry point so installations aren't exposed by default, improved OAuth2/OIDC support including discovery and logout, removed code bloat and automated code style and quality checks. Everything since has been paired security releases across both lines, several of them reporting classes of bug — sanitizer bypasses, injection through plugin queries — that the 1.7 hardening work is aimed at. Expect the security cadence to stay high while the 1.6 LTS remains supported.
Expect continued same-day paired security releases on 1.6 and 1.7, with 1.7.x accruing incremental OIDC and sanitizer hardening before any 1.8 work becomes visible.
Element iOS was renamed Element Classic in v1.11.32, and the release log since then reads like a maintenance branch: single-PR releases spaced weeks to months apart, mostly dependency bumps, build-tooling changes and one user-visible change at a time. The one substantive thread is device verification — a permanent disclaimer banner for unverified sessions arrived in 1.11.35, was temporarily disabled in 1.11.37 because users had no way to reset from the verification screen, got the Reset flow wired up in 1.11.38, and was reinstated as mandatory in 1.11.39.
The rename is the clearest signal of direction: this is the legacy client, kept working rather than extended. Recent releases raise the minimum supported OS to satisfy a Jitsi dependency, keep the Xcode toolchain current, and adjust CI — the work of a codebase being maintained, not developed. The verification arc is the exception, and even that is about closing an encryption-hygiene gap rather than adding capability.
With mandatory verification now reinstated and its reset path in place, the remaining work in this branch looks like dependency and toolchain upkeep plus security patches. The entries give no indication of new feature work, so the cadence should stay sparse and single-item.
Other Comms products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Roundcube or Element iOS.
A one-binary mail server learning to behave like production infrastructure.
Friendica keeps betting on being the fediverse node that speaks everyone else's protocols.
The original federated social network now ships roughly once every two years.
Six releases, and every one of them is a security update in some form.
Twilio is selling trust: branded calls, scoped keys, and stricter sender vetting.
Notion is turning Custom Agents into event-driven workers with their own runtime and billing.
See all Roundcube alternatives → · See all Element iOS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Roundcube is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Roundcube is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Comms products to evaluate alongside.
Top Roundcube alternatives in Comms are ranked by recent ship velocity. Browse the "Roundcube alternatives" section above for the current picks, or visit /alternatives/roundcube for the full list with editorial commentary on each.
Top Element iOS alternatives in Comms are ranked by recent ship velocity. Browse the "Element iOS alternatives" section above for the current picks, or visit /alternatives/element-ios for the full list with editorial commentary on each.