ESET Mail Security for IBM/HCL Domino reaches End of Life on July 31, 2026. ESET says there will be no successor product. There already is one. SpamSentinel is the native, on-server Domino mail security product, running on Domino since 2003. When the major email security vendors walked away from Domino, we walked toward it. We acquired SpamSentinel from Maysoft in September 2024 to keep maintaining it for the customers who still need it. Yours included, if you give us the call.
For more than 20 years SpamSentinel has been the spam, phishing, and malware product on HCL Domino. Running natively. Same architecture as ESET, same architecture as every on-server scanner the category was built around. Customers running it span regulated industries that the big vendors will not engage with at the Domino platform tier: financial services, healthcare, government, multi-decade Notes shops with deep application investments. The kind of operators who need their email security to actually work, run by someone who actually answers the phone.
In September 2024 we acquired SpamSentinel from Maysoft. Maysoft had been the trusted Domino email security shop for over two decades. The handoff was made on one condition: take care of these customers, and do not damage what we built. That is the same condition under which DuoCircle was founded in 2014, when we acquired an email-hosting customer book on the same rule. Twelve years and 50,000+ organizations later, that condition still runs the company.
ESET retiring its Domino product on July 31, 2026 is not surprising. It is the latest example of the industry walking away. We are not making the same decision. We acquired SpamSentinel specifically to keep maintaining it for the customers who still run Domino. The threat work for Domino did not stop in our shop in 2018, or 2020, or 2023, and it is not stopping now. The reason this page exists is to tell ESET shops that the replacement they need is already here, with a vendor that has been on this since 2003 and is staying.
Our claim, straight: we believe SpamSentinel is the only on-server mail security product for HCL Domino still being actively maintained. If you find another, please tell us. We have not seen one.
Two of these (internal Domino mail scanning, NSF-level message scanning) are structurally impossible for any cloud gateway. The others are the day-to-day work of running mail security on Domino, still being shipped here. One product. One install. One expert team behind the support line, the same team that has been on this since the Maysoft handoff and before.
Not a relay. Not a proxy. Not a separate product running alongside Notes. Not a mail template modification. SpamSentinel installs as a native Domino process, the same way email security on Domino has worked since 2003, and is managed from the Domino administrative client your team already uses. No new operational model. No new vendor on the diagram. Supported on HCL Domino 6.5 and newer, with full feature coverage through Domino 14.
SpamSentinel includes the capability to strip Word and Excel macro viruses before they reach a Notes mailbox. CryptoLocker and its descendants remain one of the most persistent delivery patterns in email-borne malware. We are still shipping the Domino-specific work the rest of the industry retired.
Learns from user actions and mailbox patterns to identify the senders each user actually wants to hear from, and routes the rest to Junk. Reduces the false-positive triage burden on the help desk without forcing users to maintain whitelists by hand. The kind of capability the cheap cloud filters do not give Domino shops the time of day to ship.
Phishing and impersonation attempts get blocked before they touch a mailbox database, not after a user has already clicked. The same patterns the major vendors stopped tuning for Domino are still tuned here, because Domino is still where our customers live. Our threat work for Domino did not stop in 2018, or 2020, or 2023.
Mail that flows between Notes mail-in databases, between Domino servers in a cluster, or across NRPC inside your organization never touches the external SMTP path. A cloud gateway in front of Domino never sees a byte of it. SpamSentinel does, because SpamSentinel integrates directly with both nSMTP and nRouter server tasks. Internal Domino traffic gets the same scanning as anything inbound from the outside. This is structurally impossible for any product that is not native on Domino.
Mainly SMTP filtering, the honest way to describe it, but with full access to the Notes object model at scan time. We do not just see the wire envelope. We see the message the way Domino sees it: as an NSF document with structured fields and Base64-encoded attachments. That is how SpamSentinel can reach into a macro-bearing attachment inside an NSF document field, and how the anti-phishing module can score a message body that no SMTP-layer gateway has the schema to read. Scanning is at delivery, not at rest, and not on a schedule.
We tell prospects yes or no quickly so they do not find a gap mid-deployment. These two live on every quote conversation we have. If either of them is a blocker for your environment, we would rather you know now.
Manual or scheduled rescans of existing NSF data. SpamSentinel scans at message arrival on the Domino server. We do not provide an on-demand or scheduled sweep of mail already at rest in your NSF files. If you need that workflow, we are not it.
Built-in SIEM integration or log export. SpamSentinel writes its logs to NSF databases on the Domino server. If you need to ship those logs to a SIEM, a custom LotusScript agent against the log NSF is the documented path. We have customers who have done this and we will share what they did.
Anything else you want a yes-or-no on before you spend more time? Put it in the notes field on the quote form. Same-day answer.
ESET Mail Security for IBM/HCL Domino reaches full End of Life on July 31, 2026. ESET's own documentation says, verbatim: "There will be no successor application." Hotfixes stopped on July 31, 2024, so any defect or vulnerability since then has gone unpatched. Today is May 13, 2026. 79 days remain.
This page exists because every Domino administrator currently running ESET needs a replacement, and the right replacement is the product you are already on the page for. SpamSentinel. Same architecture, same operational model, native on Domino, still maintained.
The full verified ESET timeline is on ESET's own EOL documentation. We are not the source for those dates and we have not editorialized them.
The migration is small because we kept the architecture. ESET ran natively on the Domino server. SpamSentinel runs natively on the Domino server. Same mail flow, same MX records, same operational model. You are not signing up for a six-month gateway project. You are swapping one Domino-integrated application for another, with a quick notes.ini edit and a Domino restart.
Same-day response from an expert who has actually deployed SpamSentinel on Domino. Quote and deployment plan in your inbox, not a discovery-call funnel.
Install SpamSentinel in a disabled state while ESET continues scanning. Configure settings, policies, and rules before cutover.
Swap the EXTMGR_ADDINS entry in notes.ini from ESET to SpamSentinel, restart Domino. No DNS, no MX changes. Swapping back is a quick notes.ini edit and a restart.
Remove the ESET agent, reclaim CPU and memory, update audit documentation. SpamSentinel is now your scanner.
Regulated financial services. Healthcare. Government and government contractors. Multi-decade Notes shops with applications still in production. Organizations with deep Domino investments and integration constraints that make a cloud migration impractical right now, or unnecessary, or both. They run SpamSentinel because we still know how to support it and we will not stop.
Reference calls available on request. Most of these customers will not allow public logo use on a vendor's website, for the same reason they run Domino instead of M365: they are careful about what trails they leave. They will take a phone call from a serious prospect to vouch for what we actually run in their production environments. Ask.
When you request a quote, your reply comes from an expert who has actually deployed SpamSentinel on Domino. Not an SDR. Not a generalist. Not a chatbot. Same-day turnaround. We tell you yes or no quickly. If yes, we get to work. If your environment is not a fit, we say so and you walk away with the time you came in with.
We will tell you yes or no quickly. The "no" answers are real and we would rather you hear them from us than from a sales process six weeks in.
You decided to switch architectures to a cloud gateway. Fine. There are lots of options in that market. See our replacement comparison; we will tell you when one of our competitors is the better choice for your shop.
You are actively migrating off Domino in the next 12 months. SpamSentinel extends the operational life of your Domino deployment. It does not compete with a cloud migration. Talk to us about Tenant Migration instead.
You are on Microsoft 365 or Google Workspace. SpamSentinel is built for Domino. For M365, see Phishing Protection and Spam Filtering. For Workspace, Google's built-in is genuinely strong; do not pay for an add-on you do not need.
Tell us your Domino version, your user count, and your existing setup. We come back the same day with a real number and a deployment plan. ESET EOL is 79 days away. The product that replaces it has been here for 20 years.