I'm running Zimbra 5.0.0_RC1_1538.DEBIAN4.0 and have a problem with one account (mine!) where the unread count on Inbox is persistently 1 greater than the actual count. "Mark all as read" leaves the unread count at 1. This is not an Ajax problem -- Squirrelmail running over the same im...

Replying to my own post:
This is known bug 22434: Bug 22434 - All Zimlets break on non-standard http port

Port numbers are hard-coded in /opt/zimbra/jetty-6.1.5/etc/service.web.xml.in

Change from 80 or 443 stops Zimlets from working.
Fix is as given in Bugzilla
Cheers -- Ross

Same problem here with 5.0.0_RC1. "Data not yet available" after several days running. No crashed tables or other suggestive error messages in /opt/zimbra/logger/db/data/%myhostname$.err or any other logs that I can find. Unlikely anything to do with ssh port -- I am not using a non-standa...

I noticed all zimlets had stopped working on my installation of 5.0.0_RC1Troubleshooting (backtracking) showed that switching Zimbra to port 81 to coexist with apache was the reason. Switching back to port 80 restored zimlet function. Switching to port 81 stopped them again. Proven through two cycle...

I want to run the Zimbra Open Source edition on a Debian 4.0 amd64 system, and since there is no amd64 distribution I am building from source using zcs-5.0.0_RC1_1538-src and zcs-5.0.0_BETA3_1277-3rdParty-src If/when I succeed, I'll post the fixes I've found to achieve that.I have got as far...