I'm building an IT support home lab to practice networking, ticketing systems, Microsoft 365 administration, Active Directory, and Group Policy. My lab has two simulated branch offices with several departments in each, and I recently tried setting up hMailServer as a free Windows-based mail server.
I created two accounts, [email protected] and [email protected], but messages sent between them fail. I configured IMAP on port 143 for incoming mail and SMTP on port 25 for outgoing mail. I'm still learning mail-server configuration and would like to understand what might be wrong with my setup. Could the problem be related to the IP bindings, firewall, SMTP authentication, or the use of the .local domain? Also, are there any better free mail-server applications for practicing in a home lab?
3 Answers
Review the IP ranges under hMailServer’s SMTP settings. If the server is only configured for 127.0.0.1 or localhost, other devices on your lab network won’t be able to connect. Add the correct lab subnet and make sure the server’s network adapter has the expected address. For local testing, SMTP authentication and the account credentials also need to be configured consistently in the mail client.
Start by confirming that hMailServer is actually listening on the expected address and port. From another Windows machine, run `Test-NetConnection -ComputerName 192.168.56.10 -Port 25`. If that fails, check the server IP, Windows Firewall, and hMailServer’s IP binding settings. On the mail-server computer, `netstat -ano` can show whether anything is listening on port 25. Also check the hMailServer logs for the exact SMTP error instead of relying only on the client message.
The `.local` domain can work for an isolated lab, but it isn’t a normal public mail domain and can cause confusion because it’s commonly used for local name resolution. For practice, use a reserved internal domain such as `lab.test` or a subdomain of a domain you control. hMailServer is still useful for learning SMTP, IMAP, DNS, and mail flow, though it’s fairly old. MailEnable Standard or a Linux-based option such as Mail-in-a-Box could be alternatives, but hMailServer is probably simpler if your lab is Windows-focused.
Changing the domain alone won’t fix a connection failure. I’d first verify the port test, firewall rules, bindings, and hMailServer logs, then switch away from `.local` if name resolution or client configuration remains troublesome.