MailEnable Standard is the free edition of the MailEnable mail server for Windows Server. The short answer: it is genuinely free for personal and commercial use, with no limit on domains or users, and it includes SMTP, POP3, IMAP, webmail, a list server and DKIM signing. What it does not include is the part many admins assume comes with a mail server: SPF checking, greylisting, Bayesian filtering, built-in antivirus and Exchange ActiveSync all start at the paid Professional edition. Facts below were checked on 20 November 2026 against the vendor’s download page, edition page, feature matrix, system requirements and Standard release notes. Not tested yet: we have not run this release ourselves.
What was checked and when
| Item | Standard edition, as of 20 November 2026 |
|---|---|
| Current version | 10.62, updated 3 November 2026 (all four editions share the version number) |
| Installer size | 85 MB (Professional is listed at 167 MB) |
| Licence | Free. The vendor describes it as free for both personal and commercial use, with no time or user restrictions |
| Limits | Unlimited domains and users |
| Operating systems | Windows Server 2008 through 2025; Server Core is not supported |
| Minimum hardware | 4 GB RAM (more recommended), 100 MB disk for the program itself, excluding mail data |
| Other requirements | .NET Framework 3.5 or later; the IIS Web Server role for webmail and web administration |
The edition ladder is Standard (free), then Professional, Enterprise and Enterprise Premium, which are commercial. We do not quote prices or evaluation terms for the paid editions here, so check the vendor’s page before planning a budget.
What you get for free
- Mail protocols: SMTP, POP3 and IMAP. IMAP moved into Standard in version 8; before that it was a paid-edition feature. IMAP IDLE is supported.
- Encryption: SSL for POP, SMTP and IMAP, plus TLS for inbound and outbound SMTP.
- Webmail: an AJAX client with calendar, contacts, tasks, appointment invitations, free/busy lookup, autoresponder and a mobile webmail client with calendar and tasks.
- Administration: an MMC console, web administration for mailboxes, domains, lists and groups, and a PowerShell management interface.
- Sender checks: reverse DNS blacklisting, a requirement for a PTR record on unauthenticated inbound connections, MX validation on inbound connections, and automatic banning of IP addresses after repeated failures.
- Signing: DKIM, configurable from PowerShell.
- Delivery: smart hosting for the whole server or per domain, with authentication to the downstream server.
- Directory login: Active Directory / Windows authentication.
- Moving in: a Migration Centre for importing mail from another server.
- Lists: a built-in list server with moderation, headers, footers and subscribe/unsubscribe commands.
Where Standard stops
This is the table that matters before you commit. “Standard” and “Professional” are columns in the vendor’s own feature matrix.
| Capability | Standard | Professional and above |
|---|---|---|
| SPF checking | No | Yes |
| Greylisting | No | Yes |
| Bayesian spam filtering | No | Yes |
| Antivirus (ClamAV included, or a third-party scanner) | No | Yes |
| SpamAssassin integration, URL blacklisting, global message filters | No | Yes |
| Failed-login account lockout, multi-factor authentication | No (IP banning only) | Yes |
| Exchange ActiveSync, CalDAV and CardDAV | No | Yes |
| POP retrieval (pulling mail from other mailboxes) | No | Yes |
| Indexed webmail search | No | Yes |
| Message archiving, global footers and disclaimers | No | Yes |
| Mailbox and calendar sharing, public folders, clustering | No | Enterprise and above |
One thing to double-check if you read third-party summaries: some of them list SPF, greylisting or ClamAV under Standard. The vendor’s matrix puts them in Professional and above, and that is what we follow.
Setting up a domain from PowerShell
The cmdlets ship with MailEnable and work in Standard. Open an elevated PowerShell on the mail server:
Add-PSSnapin MailEnable.Provision.Command
New-MailEnablePostoffice -Domain "example.com" -Postoffice "example.com" -UserName "sales,support" -Password "<pwd1>,<pwd2>"
New-MailEnableMailbox -Mailbox "jane" -Domain "example.com" -Password "<pwd>" -Right "USER"
Get-MailEnablePlatform -Help "*"The last line lists every platform setting you can change from scripts. DKIM cmdlets exist too (for example New-MailEnableDomainDkimSelector and Get-MailEnableDomainDkimDnsRecord); publish the printed TXT record at <selector>._domainkey.example.com before you activate signing. Release 10.61 notes mention fixes and added options to the DKIM PowerShell commands, so use 10.61 or later if you script this.
Webmail needs IIS
The mail services run without a web server, but webmail and web administration require the Web Server (IIS) role. If you plan to expose webmail to the internet, put it behind HTTPS and keep the server patched. The Standard release notes show that this is not hypothetical: version 10.62 (3 November 2026) fixed a cross-site scripting issue in webmail, 10.61 fixed several authentication-related and denial-of-service problems, and 10.60 fixed a webmail import vulnerability. The edition is actively maintained, but it also means an unpatched copy is a risk. Read the release notes when you update rather than only the version number.
Free edition, no spam filtering: what to do about it
Without SPF, greylisting or a content filter, an internet-facing Standard server relies on reverse DNS blacklists, the PTR requirement and MX validation to reject junk. Common ways admins close the gap, all outside MailEnable:
- Put a filtering gateway in front of it so that only clean mail reaches MailEnable. Xeams can play that role, but check its own licence terms for business use first.
- Use a hosted filtering service as the MX record and accept mail on the MailEnable server only from its addresses.
- Run MailEnable for internal and small-volume mailboxes and relay outbound mail through a smart host with good reputation.
- Upgrade to Professional if the filtering features are the reason you are here.
MailEnable Standard compared with hMailServer
| Criterion | MailEnable Standard | hMailServer |
|---|---|---|
| Licence | Free edition of a commercial product | Free, open source |
| Webmail | Included (needs IIS) | Not included |
| SPF, greylisting, antivirus | Paid editions only | SPF checks and greylisting built in; antivirus through an external scanner such as ClamAV |
| Web administration | Yes | Desktop administrator |
| Upgrade path | Paid editions with the same console | None; open-source only |
For a longer three-way comparison that also covers Xeams, see our Windows mail server comparison; for moving to a new box, see the migration guide.
Who should and should not use Standard
Good fit: a small organisation or a lab that already runs Windows Server, wants IMAP and webmail with a calendar, and either filters mail upstream or has low exposure to spam. Also a sensible first step if you might want the paid editions later, because they use the same console and version numbers.
Poor fit: anyone who needs mobile device sync through Exchange ActiveSync, CalDAV or CardDAV; shared mailboxes and public folders; built-in antivirus; or a server that must run on Linux or on Windows Server Core. Also unsuitable if you cannot allow the IIS role on the mail server.
Limitations of this article
We checked vendor documentation, not production behaviour. Performance, mailbox counts that the free edition handles comfortably and deliverability with major providers depend on your setup and were not measured. The version and feature matrix can change with any release, so re-check the vendor’s pages before relying on a specific item.
FAQ
Is MailEnable Standard really free?
Yes. The vendor lists the licence as free and describes it as usable for personal and commercial purposes with no time or user restrictions, and with unlimited domains and users.
Does MailEnable Standard support IMAP?
Yes. IMAP has been part of Standard since version 8, with IDLE support and SSL.
Does MailEnable Standard include webmail?
Yes: an AJAX webmail client with calendar, contacts and tasks, plus a mobile webmail client. It requires the IIS Web Server role.
Can MailEnable Standard run on Linux?
No. The vendor’s requirements list Windows Server 2008 to 2025 only, and Server Core is not supported.
Does MailEnable Standard filter spam?
Only at the connection level: reverse DNS blacklists, PTR checks, MX validation and IP banning. SPF, greylisting, Bayesian filtering and antivirus are in Professional and above.
What is the latest MailEnable version?
10.62, updated 3 November 2026, according to the vendor’s download page on the day this article was written.
Last updated: 20 November 2026 · AdminHub Plus editorial team. Licence, version and platform details are checked against each developer's official documentation.