We evaluated the ZCS network edition some months ago on OSX 10.5. it worked great ... had a few issues at the beginning but overall was extremely reliable. We purchased a commercial license and support package. Last thursday we upgraded the server to 6.0 and the nightmare began. Upgrade went flawless, but the server became very unstable ... lots of deferred mail in the queue and it seemed the MTA was dying periodically. Submitted a support case. Yesterday a technician logged into our machine and played around all day basically getting no further than I did with it. the end result "a bug in the apple operating system causes my issue" There was a bug submitted long ago about this.
here is the response i received from the Zimbra Support Team
this bug was submitted almost a year ago and against 5.0.10. we did not have this issue with the pre 6.0 versions...Your Zimbra server is now up and running. However you are running into a bug that we have identify and is caused by Apple's OS. We have filed a bug against the OS with Apple on this issue as well.
Bug 32613 – OSX 10.5 DNS and other issues after system failure
There is no fix for this issue at the moment. A work-around per the bug is to restart postfix and amavisd services. Comment #6 of the above bug contains some information on a script attached that can be ran and execute if the box gets back to the same stage. The script restarts zmmtactl and zmamavisdctl.
the work around mentioned just isnt going to cut it in my opinion. I expect alot more from something that i purchase commercially and purchase support with. Letting something lay around for a year is just not good practice. I suppose my question would be ... has anyone else had this issue and if they have the issue then how was it resolved. We are in kind of a tight spot here... we evaluated ZCS on a mac we had already... when we went to production we ordered a pricey mac pro to run the server and need to make that hardware work for this purpose so moving to another OS is not an option at this point.