Chanty
Chanty's feed is an HR statistics content mill, not a product changelog
A side-by-side editorial comparison of mailcow and SMTP2GO — release velocity, themes, recent moves, and the top alternatives to consider.
mailcow's release notes are almost entirely upstream security currency.
mailcow ships named seasonal releases with lettered revisions, and nearly every revision exists to pull in an upstream security fix - Redis, ClamAV, SOGo, Rspamd, nginx, unbound, Postfix. Revision B of the Mooly 2026 release updates Redis 7.4.10, ClamAV 1.4.6, and SOGo 5.12.10, adds minor web UI and nginx hardening, and removes a legacy DeltaChat sieve rule. The last release with genuinely new features was the March cut, which added forced 2FA, ACME DNS-01 challenges, and a passwordless autodiscover endpoint.
A blog-heavy feed masks the real signal: API upgrades for high-volume senders
SMTP2GO's tracked feed is dominated by marketing and educational blog posts — provider listicles, deliverability guides, and explainers — which makes actual product direction hard to read from this source. The one concrete product move in the recent window is a batch of API enhancements: scheduled sends, higher throughput, and more efficient large-batch sending. The company is investing heavily in deliverability content marketing around its core relay product.
mailcow ships named seasonal releases with lettered revisions, and nearly every revision exists to pull in an upstream security fix - Redis, ClamAV, SOGo, Rspamd, nginx, unbound, Postfix. Revision B of the Mooly 2026 release updates Redis 7.4.10, ClamAV 1.4.6, and SOGo 5.12.10, adds minor web UI and nginx hardening, and removes a legacy DeltaChat sieve rule. The last release with genuinely new features was the March cut, which added forced 2FA, ACME DNS-01 challenges, and a passwordless autodiscover endpoint.
For a self-hosted mail stack that bundles a dozen upstream components, keeping current with their CVEs is the product, and mailcow has organized its release cadence around exactly that. The pattern is consistent: a named release with some feature content every few months, then lettered revisions that are pure security currency plus small web UI escaping and validation fixes. The web interface is where mailcow's own code gets hardened - HTML escaping in quarantine views and sieve editors recurs across several revisions.
Expect the next entry to be another lettered revision carrying upstream updates, with the next named release likely bundling whatever feature work has accumulated since March.
SMTP2GO's tracked feed is dominated by marketing and educational blog posts — provider listicles, deliverability guides, and explainers — which makes actual product direction hard to read from this source. The one concrete product move in the recent window is a batch of API enhancements: scheduled sends, higher throughput, and more efficient large-batch sending. The company is investing heavily in deliverability content marketing around its core relay product.
Stripping out the blog noise, the product itself is trending toward scale — the API work targets high-volume, programmatic senders who need scheduling and throughput headroom. The rest of the feed is positioning and top-of-funnel education, not shipping. Product signal from this source is thin and should be read with caution.
Expect continued API and deliverability tooling aimed at high-volume senders; the blog-dominated feed offers little additional product signal to forecast from.
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 SMTP2GO.
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.
Openfire keeps its XMPP server current without changing what it is.
See all mailcow alternatives → · See all SMTP2GO alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. mailcow and SMTP2GO are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. mailcow and SMTP2GO are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 SMTP2GO alternatives in Comms are ranked by recent ship velocity. Browse the "SMTP2GO alternatives" section above for the current picks, or visit /alternatives/smtp2go for the full list with editorial commentary on each.