I have an issue with my aging (and soon to be replaced) GroupWise 6.5 system. The IMAP service in the GWIA tends to periodically shut down, requiring that I restart the service. When IMAP is down, my end users who use Blackberry BIS cannot send or receive email on their devices.
It's a royal pain to have to restart the IMAP service several times a day. The GWIA logs do not seem to indicate a problem.
I thought I was on to something yesterday. I discovered that the gwia.cfg file located in SYS:SYSTEM was actually from GW 6.0. The gwia.cfg in DOMAIN\WPGATE\GWIA was titled for GW 6.5 when opening the file for editing. I changed the generic placeholder info in the file to match my environment and restarted the gwia. However, it made no difference in performance. The IMAP service shuts down about 30 minutes after the last restart.
I know this version of GW is antiquated. We are in the process of migrating to Google Apps. But, if anyone has an idea that could fix this issue, I and my end user community would be forever grateful!
Late yesterday afternoon I changed the number of threads for IMAP4 connections from the default setting of 10 to 100 in the GWIA object under Gateways in ConsoleOne. Since then, the IMAP service has been up and stable.
I'm hoping this is the solution I've been looking for.
Why are you still running a GroupWise 6.5 system today when you should be at minimum running GroupWise version 8.0.x or the latest version 2012 (12.0.1). You should expect to have issues running such an old messaging system in today's age. If you go to http://wiki.novell.com/index.php/GroupWise_Release_History , you can see how old a messaging system you have. Support for version 6.5 has ended a very long time ago.
The solution is to upgrade to GroupWise 12.0.1 on Linux or Windows servers. It is rock solid on there and is better than Google Apps. Get off of NetWare 6.5 since Novell is trying to get all its customers moved off of that to Linux.
Arg. It has been 9 years since I last looked at a GWIA screen, and never with a BIS. There is one TID that looks possible, 10088648, where Notify Link has been tuned to a non-standard value and this breaks things. Beyond that, I'm at a loss.