Rspamd
Rspamd 4.3 fixes SPF evaluation order and rejects weak DKIM keys, with results that change.
A side-by-side editorial comparison of mailcow and Slack — release velocity, themes, recent moves, and the top alternatives to consider.
mailcow's November release patches an admin RCE and reworks sync jobs.
mailcow ships named monthly releases with lettered revisions, mostly to pull in upstream security fixes for SOGo, Nginx, Redis, Unbound and Rspamd. The November release goes further: it fixes a remote code execution flaw reachable by admins and domain admins, adds mailbox groups, and reworks imapsync so sync jobs reference a separate source. It also caps request bodies at 64 MB, which breaks large SOGo and ActiveSync mail unless NGINX_MAX_BODY_SIZE is raised.
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.
mailcow ships named monthly releases with lettered revisions, mostly to pull in upstream security fixes for SOGo, Nginx, Redis, Unbound and Rspamd. The November release goes further: it fixes a remote code execution flaw reachable by admins and domain admins, adds mailbox groups, and reworks imapsync so sync jobs reference a separate source. It also caps request bodies at 64 MB, which breaks large SOGo and ActiveSync mail unless NGINX_MAX_BODY_SIZE is raised.
The monthly security cadence holds, but recent releases carry more of mailcow's own features and API changes alongside the upstream bumps. Breaking changes now come with explicit migration steps, which suggests the API is being cleaned up for integrators.
Expect the promised RCE advisory details next week and a lettered revision within weeks to address fallout from the sync job API and body-size changes.
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.
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 mailcow or Slack.
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 mailcow alternatives → · See all Slack 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 mailcow alternatives in Comms are ranked by recent ship velocity. Browse the "mailcow alternatives" section above for the current picks, or visit /alternatives/mailcow for the full list with editorial commentary on each.
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.