Chanty
Chanty's feed is an HR statistics content mill, not a product changelog
A side-by-side editorial comparison of Mailu and Salesmsg — release velocity, themes, recent moves, and the top alternatives to consider.
Mailu ships one pinned release per issue, and most of them are Roundcube's.
The 2024.06 branch releases on demand: an issue or PR comes in, a pinned version goes out, and the changelog is one or two lines. Four of the six most recent releases are webmail-driven — three Roundcube bumps in this window alone, the latest to 1.6.18 clearing a TLS-configuration warning, an earlier one to 1.6.17 closing two CVEs. The remainder are Mailu's own code: an X-Forwarded-By header fix tied to a published advisory, sieve field escaping that repaired autoreplies and closed an injection path, and two admin-UI form flow corrections.
Salesmsg keeps widening past outbound texting into the whole customer-feedback loop.
Salesmsg has two threads running. The AI agent work has consolidated — the Unified Agent gives every texting agent one build-and-test surface, agents book and reschedule HubSpot meetings over SMS, and Salesforce Flows can enrol contacts into agents and dialer queues directly. The second thread is newer: Reviews in late July and NPS surveys now put feedback capture inside the same conversation thread, with score-based follow-ups and live analytics. Monthly digests fill in the operational layer — per-automation credit tracking, concurrent call handling, self-serve 10DLC upgrades.
The 2024.06 branch releases on demand: an issue or PR comes in, a pinned version goes out, and the changelog is one or two lines. Four of the six most recent releases are webmail-driven — three Roundcube bumps in this window alone, the latest to 1.6.18 clearing a TLS-configuration warning, an earlier one to 1.6.17 closing two CVEs. The remainder are Mailu's own code: an X-Forwarded-By header fix tied to a published advisory, sieve field escaping that repaired autoreplies and closed an injection path, and two admin-UI form flow corrections.
This is a maintenance branch behaving exactly as a maintenance branch should, and the pinned-version model is the product: operators get upstream security work packaged and tagged without tracking Roundcube themselves. The security items divide cleanly — most arrive from bundled components, a minority from Mailu's own code, and the project patches both on the same cadence. Nothing in this window suggests new capability is being developed on this branch.
Expect the next release to follow the same trigger: a Roundcube advisory or a client compatibility report producing a single-line changelog and a new pinned tag. Any feature work would be happening on the main version, which this feed does not cover.
Salesmsg has two threads running. The AI agent work has consolidated — the Unified Agent gives every texting agent one build-and-test surface, agents book and reschedule HubSpot meetings over SMS, and Salesforce Flows can enrol contacts into agents and dialer queues directly. The second thread is newer: Reviews in late July and NPS surveys now put feedback capture inside the same conversation thread, with score-based follow-ups and live analytics. Monthly digests fill in the operational layer — per-automation credit tracking, concurrent call handling, self-serve 10DLC upgrades.
The platform is expanding along the conversation rather than along the sales funnel. Having won the channel, Salesmsg is adding everything a service business would otherwise buy separately — reputation management, satisfaction measurement, IVR and call routing — on the argument that the SMS thread is where those things actually convert. The credit-tracking and system-health work suggests customers are now running enough automated volume to need cost attribution.
Expect the survey and review data to start feeding the AI agents rather than sitting in their own dashboards — a detractor score is an obvious trigger for an automated follow-up conversation. Further CRM-side parity between the HubSpot and Salesforce integrations is the other consistent pattern in these entries.
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 Mailu or Salesmsg.
Chanty's feed is an HR statistics content mill, not a product changelog
Proton Bridge spends its first release in ten weeks on crashes, memory bounds and dead code
Stalwart is chasing mail RFCs and its own storage layer at the same time
Every manual control Mux ships now arrives with a Robots workflow that does it for you
Netcore's feed remains a demand-generation channel; ten entries, zero product releases.
mailcow's release notes are almost entirely upstream security currency.
See all Mailu alternatives → · See all Salesmsg alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Salesmsg is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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. Salesmsg is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 Mailu alternatives in Comms are ranked by recent ship velocity. Browse the "Mailu alternatives" section above for the current picks, or visit /alternatives/mailu for the full list with editorial commentary on each.
Top Salesmsg alternatives in Comms are ranked by recent ship velocity. Browse the "Salesmsg alternatives" section above for the current picks, or visit /alternatives/salesmsg for the full list with editorial commentary on each.