IMAP Timeout on SmarterMail

SmarterMail IMAP Time Out

Over the last 1 week, SmarterMail users has been experience an intermittent unstable connection – mostly are receiving timed out when connection is made to the mail server.

This was a result of the release of the SmarterMail v15.7.6816, v16.3.6816, and v17.0.6816 which contains a TCP connection bugs as explained by SmarterTools:

One of the things last week’s release was supposed to include were some memory optimizations to our TCP code which is used by POP, XMPP, SMTP and IMAP. (Not EAS, EWS or WebDAV). These optimizations were to help streamline processing requests for those protocols as well as address a memory leak that was found. Unfortunately, what appears to have happened is that the code also caused commands to be half-read or for some requests from clients to contain incomplete commands. In either case, clients would drop connections altogether or error out with incomplete info written to the logs. The devs stepped through all that code again and were able to narrow down the issue and get it resolved. We were able to keep the optimizations while mitigating the odd behaviors.
Obviously, we’re never pleased when bugs like this get released. We do have manual QC processes that occur before any minor goes out. 99% of the time, we find issues prior to release. Some issues are harder than others to see ahead of time, and, of course, everyone’s environment is different with different protocols being used, different user counts, different clients, etc. We try to be proactive with testing and QC, but each install is different and user mileage varies. That said, Tim is obviously involved and we are actively discussing how to catch these types of issues more efficiently.
If you have been experiencing the above issues on your SmarterMail installation, apply the latest release by SmarterTools which address the matter across the version v15, v16 and v17 that have 2 fixes as below:
  • IMPORTANT: Fixed issue where TCP connections are being prematurely closed under certain circumstances, causing a variety of issues.
  • Efficiency: Prevent potential memory leaks with how TCP connections were being improperly disposed.

Share With Us About Your Thoughts....