![]() Our first configuration task will be to add a domain:Īdd a domain with the same name as your DNS domain. Click Connect:Įnter the password that you set during installation and click OK: In my case I only have one so I would check the box “Automatically connect on start-up” to bypass this step in the future. This is useful if you have multiple hMailServer systems to manage. You will be presented with the Connect dialog. ![]() The installation takes just a couple of minutes while the database is initialised. Not much to look at here, but you may want to change your installation folder. Be sure to take note of this as you’ll be needing it to complete the configuration. Select the option to use the built-in database engine and click Next:Ĭhoose a name for the Start Menu folder and click Next:Įnter a password for accessing the administration tool. Click Next.Ĭhoose to select all components, Server and Administrative tools, and click Next: Note that your email database file will be created in this folder so choosing the default shown here would not be a good idea in a production environment but for a lab setup it’s fine. Click Next.Īccept the license agreement and click Next:Ĭhoose an installation folder. Double click on the installer (currently this is hMailServer-5.6.4-B2283.exe) to launch the install wizard. Leave the “Host or child domain” field blank and the “Mailserver priority” value at its default value of 10.Ĭlick OK and check that the record has been created as expected. In my case this is the record for the domain controller. Use the Browse button to select the Host (A) record for the server that hMailServer will run on. Right-click on the domain folder and choose “New Mail Exchanger (MX)…”. In my case I’ve created a domain called test.local. Open the DNS management utility in Windows and navigate to your domain. This isn’t strictly necessary in an isolated single server environment, but it can’t hurt and may help to avoid any unforeseen delivery issues. My first task was to create an MX record for the service. Net Framework 2.0 were installed before I began. In the case of my own system, I needed to ensure that service pack 2 and. Microsoft Windows XP Professional Service Pack 3.The range of Windows versions supported is: However, version 5.6 (the most current) supports a wide range of Windows operating systems so you shouldn’t have any difficulties. Hopefully people will find this simplified guide useful.įor simplicity, in my lab I use a Windows 2003 server as my domain controller, and I use this as my hMailServer system also, so the screenshots below are all from that system. My motivation for writing up this guide was that a lot of other guides I read seemed overly complicated and confused matters with references to using SquirrelMail. I know there are a lot out there but I settled on one that most of you will already be familiar with, Mozilla’s Thunderbird. I was also looking for a free email client. HMailServer is a free, open source, e-mail server for Microsoft Windowsthat supports the common e-mail protocols (IMAP, SMTP and POP3). I was lucky to come across hMailServer, a free, open source, e-mail server for Microsoft Windows. Not being an expert on building MS Exchange systems, I went looking for a simple solution that I could install in my lab quickly with few dependencies. I also need an email system as I start to explore vRealize Automation, with its system of approvals based on emails. In my lab environment I work a lot with systems that use email notifications, such as VMware vCenter, vRealize Operations Manger, Veeam Availability Suite, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |