HMailServer

hMailServer is no longer being actively developed or maintained. The latest major version was released several years ago. hMailServer relies on algorithms which are considered insecure by modern standards, such as SHA1 and outdated versions of OpenSSL. For that reason, it's recommended that you migrate to an alternative software or service. 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 example 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. 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. Download 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. SET CFLAGS=-DOPENSSL TLS SECURITY LEVEL=0 Perl Configure no-asm VC-WIN64A --prefix=%cd% out64 --openssldir=%cd% out64 -D WIN32 WINNT=0x600 --api=1.1.1 no-deprecated nmake clean nmake install sw 1. Download PostgreSQL 15.18 source from and put it into %hMailServerLibs% postgresql-15.18. You should now have a folder named %hMailServerLibs% postgresql-15.18, for example C: Dev hMailLibs postgresql-15.18 2. Start a x64 Native Tools Command Prompt for VS2019. 3. Change dir to %hMailServerLibs% 4. Run the following commands: bootstrap b2 debug release threading=multi link=static --with-thread --with-filesystem --with-regex --with-chrono --with-system --with-atomic --toolset=msvc-14.2 address-model=64 stage --build-dir=out64 -j 4 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. hMailServer source code contains a number of automated tests which excercises the basic functionality. When adding new features or fixing bugs, corresponding tests should be added. hMailServer tests are implemented using NUnit. To run them in Visual Studio, follow these steps: NOTE: When running tests, your local hMailServer installation will be updated with test accounts. Existing domains and accounts are deleted. Each tests prepares the server configuration in differen