Rspamd
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
A side-by-side editorial comparison of Slack and Stalwart — release velocity, themes, recent moves, and the top alternatives to consider.
Slack now hosts any A2A agent without Slack-specific code.
Slack's developer channel is almost all agent plumbing. On 10 November Slack became an A2A (Agent2Agent) client: a team hosts its own agent, publishes an Agent Card, and Slack calls it when people talk to it, with no request URL, event handling or Slack-specific logic. This follows Slackbot skills managed through Web API methods, a Slack CLI that points coding agents to the Slack MCP server, and a new requirement that Work Objects embeds allow the slack-mcps.com frame ancestor.
Stalwart's weekly releases have turned from new standards to correctness fixes.
Stalwart's releases since v0.16.20 are dominated by long Fixed lists across IMAP, JMAP, MTA, DMARC and iTIP. Additions have been small: a PowerDNS provider in 0.16.24, sd_notify and JMAP mailbox behavior in 0.16.26. The most consequential repair is a RocksDB bug in 0.16.26 that rewrote every stored blob on each compaction of the blobs column family, about once per 128MB of new mail.
Slack's developer channel is almost all agent plumbing. On 10 November Slack became an A2A (Agent2Agent) client: a team hosts its own agent, publishes an Agent Card, and Slack calls it when people talk to it, with no request URL, event handling or Slack-specific logic. This follows Slackbot skills managed through Web API methods, a Slack CLI that points coding agents to the Slack MCP server, and a new requirement that Work Objects embeds allow the slack-mcps.com frame ancestor.
Slack is lowering the cost of putting outside agents in front of its users: first skills as code, then MCP pointers for coding agents, now a standard protocol in place of the Slack app model for agents. The platform is positioning itself as the place where agents built anywhere meet the people who use them.
Expect more A2A follow-ups, such as agents appearing in Slackbot or skills surfaces and richer Agent Card features, given how fast the agent releases have stacked up since October.
Stalwart's releases since v0.16.20 are dominated by long Fixed lists across IMAP, JMAP, MTA, DMARC and iTIP. Additions have been small: a PowerDNS provider in 0.16.24, sd_notify and JMAP mailbox behavior in 0.16.26. The most consequential repair is a RocksDB bug in 0.16.26 that rewrote every stored blob on each compaction of the blobs column family, about once per 128MB of new mail.
After the SCIM v2 release in August, the project has shifted from extending coverage to making existing coverage hold up under real use. The bug reports now describe specific interoperability cases, such as Apple Calendar duplicates and DMARC report formatting, which suggests production traffic is driving the queue. The weekly cadence itself has not changed.
Expect more weekly fix releases on the same pattern. The entries show no sign of the next major capability, so its timing is unclear.
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 Slack or Stalwart.
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
Twilio's voice AI stops cutting callers off mid-sentence, using its own turn-taking model.
Salesmsg adds call-back requests and a one-click Emergency Stop for all outbound texts.
Element 1.12.35 follows the call picture-in-picture release with one desktop storage fix.
Krisp moves call transcripts and live captions to cloud transcription in KrispCX 2.84.4.
Misskey 2026.11 ships: a leaner start script, and Node.js 22 no longer boots.
See all Slack alternatives → · See all Stalwart alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Slack 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. Slack 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 Slack alternatives in Comms are ranked by recent ship velocity. Browse the "Slack alternatives" section above for the current picks, or visit /alternatives/slack for the full list with editorial commentary on each.
Top Stalwart alternatives in Comms are ranked by recent ship velocity. Browse the "Stalwart alternatives" section above for the current picks, or visit /alternatives/stalwart for the full list with editorial commentary on each.