How To Configure SpamAssassin for HMailserver in Windows Server 2003

Setting up SpamAssassin for MailServer in Windows is a tricky thing to do.

Documentation on the subject is sparse and Google searches turn up very old posts or posts that point you in the wrong direction. Fortunately once you know the setup process, it is fairly straightforward and easy to do.

There are several different versions of SpamAssassin out there. The main branch requires you to download the source code, then download perl to compile the source as binaries. Fortunately in our case, there is already versions compiled for Windows in the form of SAWin32.

How to Configure SpamAssassin for HMailserver in Windows

1. Download SAWin32 3.2.3.3, which is the latest windows build of SpamAssassin (As of September 8, 2009).
   
2. Download the latest SpamAssassin for Win32 command-line tools 3.2.3.5
3. Unzip both files into your computer with HMailServer installed under the path "c:\sa\"
4. Next we will have to create a new Windows Service called "SpamAssassin". This will allow HMailServer to use SpamAssassin.
   
   1. Install the Windows Server 2003 Resource Kit Tools. This will give you the necessary INSTSRV.EXE and SRVANY.EXE files to run SA as a service
   2. Go to Start Menu -> Run -> cmd
   3. Under the command line, enter in the following line (with quotes):
      
      "C:\Program Files\Windows Resource Kits\Tools\INSTSRV.EXE" SpamAssassin "C:\Program Files\Windows Resource Kits\Tools\SRVANY.EXE"
      
      
   4. Once installed, open up Regedit
   5. Go to HKLM -> SYSTEM -> CurrentControlSet -> Services -> SpamAssassin
   6. Add a new key called "Parameters"
   7. Under Parameters, add a new String Value of Application, and set the value data to (without quotes):
      
      "c:\sa\spamd.exe -l -s c:\sa\spamd.log --round-robin"
      
      
   8. Then go to the services control panel and start up the spam assassin service.
   9. If there are any issues, check the c:\sa\spamd.log file for more info
5. Then you might have to allow dccproc and spamassassin in your firewall
6. Adjust your hMailServer settings to allow the incoming e-mail check against SpamAssassin
7. And finally you might have to restart your hMailServer service for the new service to take effect.