Talk:Kerio MailServer

= Kerio Connect =

I am aware that, as of February 9th, 2010, there is new version of Kerio MailServer (7.0.0) that has been renamed to Kerio Connect.

I have yet personally upgraded to or tested this version (for various reasons) however I do intend to test it out soon.

If anyone has already done so and has had good or bad experiences please post them here - it would help a great deal.

Many thanks! -  Mousee 17:16, 3 April 2010 (GMT)
 * Just to note, my preliminary testing with Kerio Connect (KCN) indicates that it works "flawlessly" with the current wiki article's instructions. Obviously replace any references to KMS with KCN as needed.


 * Eventually I'll get around to creating a new page for KCN and, as I think it's long overdue, I'll try to include the ebuild I've created for installing the main mail server program, the admin console, and the documentation (which is currently non-existent for KCN). I'll also attempt to add a "Tips & Tricks" section(/sections?) detailing some spam prevention techniques, etc. Don't expect it for a while however - as Kerio has yet to fix the performance issues that have cropped up since 7.0.x was first released (and thus it's not my intention to upgrade any time soon). Mousee 15:53, 23 May 2010 (GMT)

= Init Script Changes & Issues =

After having had some recent issues with the KMS executable during a server migration I went through and cleaned up the init script.

Namely I removed the init script's check for files/directories that, I believe, never would have existed on a Gentoo system in the first place.

Further, I included a "KILL" timer as well as a "Retry Wait Time" to the init and config scripts. Under normal operating circumstances the "KILL" function should never be reached when you issue a /etc/init.d/keriomailserver stop. Setting the "STOPTIME" variable even higher will ensure this. However there are, apparently, times when the mailserver executable will "hang" permanently. I'm unsure of the exact cause for this but in my own experience, having negated the possibility that it was a difference in the base system (ie. CFLAGS, missing or different versions of packages, etc), I discovered that a perfectly functional mailserver.cfg config file in one system would cause the mailserver process on another system to "hang" indefinitely. In my own situation I removed some, apparently, obsolete entries in the config file and that "magically" allowed the mailserver process to start and stop properly once again.

If you do not like the idea of the init script killing the mailserver process itself then please feel free to remove the "KILL" functions within the init script. I may modify that functionality in the near future to become a switchable (on/off) option in the config file so that direct modification of the init script is unnecessary. Mousee 15:46, 18 May 2010 (GMT)