The State of HCL Domino: A Critical Examination

If you’re like me, and continue to work in the Notes Domino bubble, you’ve probably noticed the cracks showing in the HCL Domino foundation. The latest issue, a massive mail routing failure, just highlights how deep the issues run.

The Mail Routing Bug: A Problem Decades in the Making

On December 13, 2024, a long-hidden flaw in Domino’s code finally came to light. If you restarted your server, mail routing went haywire. Messages got stuck in loops, mail rules stopped working, and Domino defaulted to using just one mail.box no matter your configuration. It’s like finding out your car’s airbag has never worked, but you’ve been driving it for 30 years without a crash.

What’s surprising is that this bug has been around for over three decades. It wasn’t caused by a recent update; it’s been baked into the system since the Lotus days. Neither IBM nor Lotus caught it, and now HCL is left scrambling to clean it up. They did release a fix quickly, but only if your server is running the latest patches. If you’re behind on updates or not on extended support, you’re out of luck.

Why does this bug matter you ask?  This bug isn’t just a glitch—it’s a warning sign. Domino’s been running on fumes for a while now, and this is just the latest example of its technical debt catching up. Over the years, there’s been a lot of duct tape applied to it, but the core problems haven’t been addressed. It’s like trying to keep an old house livable without fixing the foundation.

When HCL bought Domino, there was hope they’d breathe new life into it. And sure, they’ve added some shiny new features and tools like Nomad and Volt MX. But underneath, the platform still has a lot of the same issues that have been there for years. This latest bug shows how those issues can come back to bite us when we least expect it.

Domino’s place in the market is shrinking fast. It’s hard to compete with platforms that are faster, more modern, and better integrated. The perception, and let’s be honest, the reality, is that Domino is clunky and outdated. This bug doesn’t help. It’s another black eye for a platform that can’t afford any more hits.  

I’ve also seen a lot of frustration from other users. The support process can feel like pulling teeth, and the upgrade path is anything but smooth. For companies still relying on Domino, it’s becoming harder to justify sticking around. More and more businesses are planning their exit strategies, looking at alternatives that don’t come with this kind of baggage.

I’ll be watching to see what HCL does next. Will they tackle the hard work needed to make Domino relevant again? Or will this be another nail in the coffin for a platform that’s already on its last legs? Time will tell, but for now, I’m not holding my breath.

Rob Salerno/Rivit Technology Partners