Quote:
Originally Posted by phoenix  Don't even try to do that, you will break the system. |
If that's the case, then admins in our situation are completely
screwed. We've already been chained to the Zimbra server 24/7 for nearly a month now, doing 1-4 reboots a day, and so far the only consolation is hearing that a fix may be coming in November. As far as I'm concerned, any email server that crashes four times a day is a lost cause.
If there's a fix for 7.1.1, then the engineers should know how to do the patch for 7.1.2. I know they want to hold it for the larger 7.1.3 release, but that that's like saying,
"Sorry you email server doesn't work because of a flaw in our latest software. We'll fix it in 2-3 months."
Meanwhile, the bug that is keeping us constantly rebooting the server is lised in report
Bug 63100 – imap:deadlock when # of session is overflowed the limit and some imap session has to be pushed out of sessonmap as FIXED. No problem. All taken care of. Except if you made the mistake of 7.1.2, and for that mistake there is no bug report at all. Too bad. You're screwed.
Three years ago when we were selecting a new email server, our number one priority was reliability. Our last system had it, Zimbra had to have it. We had a perfectly stable Zimbra 6.0 system for two years-- no complaints. Now, however, it is anything but stable, and there's no end point in sight. How could anyone recommend or excuse this?
C'mon Zimbra, toss us a bone here. We'd like to spend time with our wives and kids again on the weekends and evenings, and stop getting complaints from 1,600 users who are just trying to use their email.
Bugzilla
Wiki
Source
Getting very hacked off with Zimbra 
Linear Mode
