hMailServer vs MailEnable vs Xeams: Choosing a Windows Mail Server

This comparison is for admins choosing a self-hosted mail server for Windows, or for a Windows-friendly stack. The short answer: pick hMailServer if you want free, open-source mailboxes with built-in spam checks and do not need webmail. Pick MailEnable Standard if users need webmail and a web admin panel on Windows Server and you can live without its anti-spam features. Pick Xeams when the main job is filtering and archiving mail in front of another server, or when you need Linux; for business use it is paid. Facts below were checked on 6 November 2026 against vendor pages and the hMailServer GitHub repository. Not tested yet: we have not benchmarked these servers ourselves.

At a glance

Which one does which job

Mailboxes for a small office on one Windows box

hMailServer and MailEnable Standard both do this for free. The practical split is webmail. MailEnable ships webmail with calendar, contacts and tasks, hosted in IIS, so the IIS role must exist before setup. hMailServer has none; plan on pairing it with a separate webmail client such as Roundcube, which is extra work and a second thing to patch.

The spam side points the other way. hMailServer gives you SPF checks, greylisting and DMARC for nothing. In MailEnable those start at the paid editions, so a Standard install usually needs an external filter. Xeams is a natural fit for that gap, since it can sit in front of an existing server and filter before delivery.

Filtering mail in front of Exchange or Microsoft 365

This is where Xeams is strongest. You move the existing server off port 25 (for example to 2500), install Xeams, choose the email firewall role and point delivery at the old listener. For a hosted target you install Xeams on its own host, point your MX record at it and allow inbound SMTP on the downstream side only from the Xeams address. Neither hMailServer nor MailEnable is designed as a gateway first, though hMailServer can relay.

Automating account setup

Both Windows-native servers script well. hMailServer exposes a COM API; run it from 64-bit PowerShell because 5.7 is 64-bit only:

$app = New-Object -ComObject hMailServer.Application
$null = $app.Authenticate("Administrator", "<admin password>")
$acc = $app.Domains.ItemByName("example.com").Accounts.Add()
$acc.Address = "jane@example.com"; $acc.Password = "<initial password>"; $acc.Active = $true; $acc.Save()

MailEnable uses cmdlets that also work in Standard:

Add-PSSnapin MailEnable.Provision.Command
New-MailEnableMailbox -Mailbox "jane" -Domain "example.com" -Password "<pwd>" -Right "USER"

Both approaches fit onboarding scripts; see our cloud and SaaS administration tools hub for the wider mail and collaboration picture.

Requirements and traps

• hMailServer: the 5.7 line is 64-bit only and lists Windows 7 SP1 to 11 and Server 2008 R2 to 2022; Server 2025 is not on that list. The bundled SQL Server Compact database is limited to 4 GB and to personal, non-commercial use in the documentation, so use MySQL/MariaDB, SQL Server or PostgreSQL in production. The 1 November pre-release changes how SQL Compact writes to disk, a reminder to stage any upgrade first.
• MailEnable: official requirements list 4 GB RAM, about 100 MB of disk for Standard program files and .NET Framework 3.5 or later. Running on non-server Windows is covered only by a knowledge-base article and is unsupported. See the official system requirements.
• Xeams: the installer is the same for Community and Enterprise, so a new install starts with Enterprise features and then falls back to Community unless a licence is bought. Do not install into Program Files, and check the official changelog before upgrading.
• All three: you own IP reputation. Set MX, SPF, DKIM and a PTR record matching the HELO name, and confirm your provider allows outbound port 25 (Test-NetConnection -ComputerName gmail-smtp-in.l.google.com -Port 25).

Limitations

• hMailServer restarted releases in September 2026 after years of quiet. Support is community-based, so test each build on a staging server.
• MailEnable Standard has no ActiveSync, CalDAV/CardDAV, MFA or archiving.
• Xeams Community is not for business use, and its spam filtering stops at five users. It is Java-based, so memory use is higher than a lightweight MTA.
• If you can run Linux, Postfix with Dovecot or a packaged stack such as mailcow is a different category with a larger community; this article does not compare them.

How to choose

1. Need webmail on Windows Server, free: MailEnable Standard, plus an external spam filter.
2. Need strong free spam checks, no webmail: hMailServer.
3. Need a gateway, archiving or Linux: Xeams, and budget for the paid edition if it is a business.
4. Need groupware or mobile sync: look at paid MailEnable editions or another product class.

FAQ

Is hMailServer or MailEnable better?

Neither wins outright. hMailServer has the better free spam toolkit; MailEnable Standard has webmail and a web admin panel.

Is hMailServer still maintained?

Yes. Version 5.7.1 was published on 29 September 2026 and a 5.7.2 pre-release followed on 1 November 2026. Releases had paused before that, so treat updates cautiously.

What is a free alternative to hMailServer?

On Windows, MailEnable Standard is the closest. Xeams Community is free only for personal use. On Linux, Postfix-based stacks are the usual choice.

Can I use MailEnable Standard for a business?

Yes. The vendor states Standard is free for personal and commercial use, with unlimited domains and users.

Is there a free Windows mail server?

Two: hMailServer (open source) and MailEnable Standard. Xeams is free only for personal and hobbyist use.

Last updated: 6 November 2026 · AdminHub Plus editorial team. Licence, version and platform details are checked against each developer's official documentation.