hMailServer is an open source email server for Microsoft Windows.

This page describes how to compile and run hMailServer in debug.

For other information about hMailServer, please go to https://www.hmailserver.com

• The master branch contains the latest development version of hMailServer. This version is typically not yet released for production usage. If you want to add new features to hMailServer, use this branch.

• The x.y.z (for exampel 5.6.2) contains the code for the version with the same name as the branch. For example, branch 5.6.1 contains hMailServer version 5.6.1. These branches are typically only used for bugfixes or minor features.

Required software

• An installed version of hMailServer 5.7 (configured with a database)
• Visual Studio 2019 Community edition
• InnoSetup 5.5.4a (non-unicode version)
• Perl ActiveState ActivePerl Community Edition 32 bit works fine

NOTE

You should not be compiling hMailServer on a computer which already runs a production version of hMailServer. When compiling hMailServer, the compilation will stop any already running version of hMailServer, and will register the compiled version as the hMailServer version on the machine (configuring the Windows service). This means that if you are running a production version of hMailServer on the machine, this version will stop running if you compile hMailServer. If this happens, the easiest path is to reinstall the production version.

1. Downlod Visual Studio 2019 and launch the installation.
2. Select the following Workloads

• .NET desktop development
• Desktop development with C++

3. Select the following Individual components

• C++ ATL for latest v142 build tools (x86 & x64)
• Windows 10 SDK (10.0.18362.0)

Some 3rd party libraries which hMailServer relies on are large and updated frequently. Rather than including these large libraries into the hMailServer git repository, they have to be downloaded and built, currently manually. When you build hMailServer, Visual Studio will use a system environment variable, named hMailServerLibs, to locate these libraries.

Create an environment variable named hMailServerLibs pointing at a folder where you will store hMailServer libraries, such as C:\Dev\hMailLibs.

1. Download OpenSSL 1.1.1* from https://www.openssl.org/source/ and put it into %hMailServerLibs%<OpenSSL-Version>. You should now have a folder named %hMailServerLibs%<OpenSSL-version>, for example C:\Dev\hMailLibs\openssl-1.1.1s

2. Start a x64 Native Tools Command Prompt for VS2019.

3. Change dir to %hMailServerLibs%<OpenSSL-version>.

4. Run the following commands:

   Perl Configure no-asm VC-WIN64A --prefix=%cd%\out64 --openssldir=%cd%\out64 -D_WIN32_WINNT=0x600
   nmake clean   
   nmake install_sw
   

1. Download Boost 1.72.0 from https://www.boost.org/ and put it into %hMailServerLibs%<Boost-Version>.
   You should now have a folder named %hMailServerLibs%<Boost-Version>, for example C:\Dev\hMailLibs\boost_1_72_0

2. Start a x64 Native Tools Command Prompt for VS2019.

3. Change dir to %hMailServerLibs%<Boost-Version>.

4. Run the following commands:

   NOTE: Change the -j parameter from 4 to the number of cores on your computer. The parameter specifies the number of parallel compilations will be done.

   bootstrap
   b2 debug release threading=multi --build-type=complete --toolset=msvc address-model=64 stage --build-dir=out64 -j 4
   

Visual Studio 2019 must be started with Run as Administrator.

1. Download the source code from this Git repository.
2. Compile the solution hmailserver\source\Server\hMailServer\hMailServer.sln. This will build the hMailServer server-part (hMailServer.exe)
3. Compile the solution hmailserver\source\Tools\hMailServer Tools.sln. This will build hMailServer related tools, such as hMailServer Administrator and hMailServer DB Setup.
4. Compile hmailserver\installation\hMailServer.iss (using InnoSetup) This will build the hMailServer installation program.

If you want to run hMailServer in debug mode in Visual Studio, add the command argument /debug. You find this setting in the Project properties, under Configuration Properties -> Debugging.

Production builds can be downloaded via hMailServer.com, but if you want to pick up a build based on the latest commit you can download artifacts from GitHub Actions.

Without finding any serious issues:

1. Run all integration tests on supported versions of Windows and the different supported databases.
2. Run all server stress tests
3. Enable Gflags (gflags /p /enable hmailserver.exe) and run all integration tests to check for memory issues
4. Run for at least 1 week in production for hMailServer.com
5. Wait for at least 500 downloads of the beta version