Invalid SQL: REPLACE INTO `swsessions` (`sessionid`, `ipaddress`, `lastactivity`, `useragent`, `isloggedin`, `sessiontype`, `typeid`, `dateline`, `status`) VALUES('nxzbxqbvng9zoxxuz5nux5ff1iomedd2', '', '1527464848', 'CCBot/2.0 (', '0', '40', '0', '1527464848', '0'); (The table 'swsessions' is full) A Brief Introduction to Hmailserver - Powered By Kayako SupportSuite
Fluid Hosting 27 May 2018 
HomeServicesSupportContact UsAbout UsForums |
Support Center » Knowledgebase » A Brief Introduction to Hmailserver
 A Brief Introduction to Hmailserver
Solution As we all know, most Microsoft Windows native email server software such as Microsoft's Exchange or IPswitch's Imail costs a lot to deploy and maintain.   hMailServer on the other hand is a full-featured (which handles IMAP, SMTP, and POP3 email protocols), free email server.  Version 4.4 is licensed under the GPL while version 5 and higher is closed source, but basically is still FREE.   hMailServer is actively developed by Martin Knafve and currently has a very active user-base community.

hMailserver can be deployed and used for a small scale email system to a high capacity, enterprise wide email server solution.  Out of the box, hMailServer uses Microsoft's SQL lite for it's database backend for small to medium sized systems while fully compatible with industrial quality databases such as MySQL and PostgreSQL.  This document will briefly discuss and introduce what the requirements are and what software you need to be able to utilize hMailServer as your email server software for your Widows-based Virtual Private Server (VPS).

In some instances wherein you will need to have a web based email client frontend, Squirrelmail is known and documented to be quite friendly and compatible with hMailServer. In fact, it's the most widely used web based interface for hMailServer.  You will need to install the following if you wish to have a Squirrelmail frontend.

NOTE:  Some of you might ask, why I chose to do individual/independent installs of the major components when it could have been easier to just install a ready WAMP package such as the "WAMP Server" (  The reasoning behind this is that most WAMP systems are designed to be deployed as test environments where programmers and developers will have very minimal problems in terms of security and settings. So if you read the disclaimers on each WAMP type systems, you would always discover that the makers actually DO NOT advise that it will be used in production environments due to the relaxed security settings and other such reasons.
by: kai talledo 06/01/2011

Article Details
Article ID: 348
Created On: 01 Jun 2011 05:41 PM

 This answer was helpful  This answer was not helpful

 Login [Lost Password] 
Remember Me:
 Article Options
Home | Submit a Ticket | Knowledgebase | News | Downloads

Help Desk Software Help Desk Software By Kayako SupportSuite v3.60.04