Does that suggest that the Zimbra bug situation is a disaster?
And to respond to a suggestion we contact an account manager, we tried to contact the one we worked with for the purchase. Never received a response.
Does your ERP software vendor Cc you in the same bug database that their developers use? That can be more valuable.
I've had some really long waits too -- my Bug 32536 – Zimbra too trusting of MIME-type sent by client really dates from March 2008 (it took two months to realize what the actual problem was) and is due to be addressed in 5.0.16 any day now -- but I understand that my issues aren't the only issues.
Making sure that your issue is tagged with your support case number (they don't always do that) and (as appropriate) lobbying for votes here do help.
32536 took a long time because it's really a Mozilla bug, not a Zimbra bug, and figuring out how to work around it safely is nontrivial. I don't know about your bugs.
Interesting bug lists ... but impossible to read.
Could you spend some time formatting them into proper lists, with proper spacing, punctuation, etc? Was really looking forward to seeing which (if any) of these correspond to things we've noticed (and entered as bugs) ... but it's all just a big splat text with nothing to differentiate anything from anything.
Our experience has been similar. We did a test pilot of 5.0.0 (starting with RC1 through GA) way back when. During the pilot, a bunch of issues were found and filed as bugs. We also found bug entries that corresponded to issues we were having, so we added comments to those bugs, and voted for them.
After the pilot, we decided not to go with Zimbra. That was about a year ago. Yesterday, I logged into bugzilla as we are againg piloting Zimbra, and over half of the bugs we voted for were marked as complete.
If you aren't willing to spend the time documenting issues and entering bugs and participating in the resolution process, then you really can't complain. :)
after spending their money on a product, any product whether it is software, hardware, the appliances in your house, your car, or any other product one has purchased, don't feel they should have to spend their time and efforts debugging that product. They just expect it to work as advertised.
Somehow, the software industry has been trying to convince their customers that it is their duty to help debug something they have spent their hard earned money on. It doesn't work this way in any other industry and it is a shame the software industry can get by with forcing additional costs in the form of time spent on their customers. Especially when the customer has purchased a support contract.
Some IT people enjoy going through the forum process. But most don't.
I use the FOSS version so I don't say much about this ridiculous process. The couple of bugs I have posted haven't been fixed. One has to be at least a year old. Plus the last two posts I made regarding issues were not even answered.
I definitely would not pay for a product with as many unresolved bugs as Zimbra has plus the hoops you have to jump through to get anything resolved. For a free product it is OK. But there is not one feature in Zimbra that operates as claimed without some kind of glitch or another.
I like Zimbra. But for me, its functionality doesn't go much past a basic E-mail program. Everything else I have tried to use (especially the documents) has bugs that make them not good for business usage.
Of all the paid mailboxes bragged about I wonder how many are hard core business mail boxes and how many are simply used for E-mail.
Bugzilla Main Page . I also encourage the community to vote on bugs that are important.
A couple of Zimbra QA engineers looked through the list of bugs and filed these:
However, some of the listed bugs were duplicates, some were not reproducible, some needed more details, some were working as designed. Those bugs were not filed.
As everyone has stated on this thread, if you find a bug, post it to the Zimbra bugzilla site rather than the forums. To increase the likelihood of your bug being processed, include clear steps to reproduce, describe the behavior that you expect to see, and include applicable message data as attachments (e.g. MIME sample, ICS sample, CSV, server exception, server SOAP trace)
But in the future, adding proper paragraph spacing would go a long way to making things easier for others to read.