Sorry, I still vehemently disagree. This has been very costly to us but the world is not just about me. I have gladly wrestled this to the ground and now we have solved it so that others may benefit from our work. I believe that is one of the core definitions of community and open source contribution - my and my company's way of contributing rather than just leaching. Yes, this one cost us a lot more than we would have liked and we sure wish someone else had paid the tuition before us but our contribution pales in light of what it has cost others to give us the wealth of open source products that power our company.
Along the way, we have enriched our engineering knowledge base so we can move beyond taking the defaults and being glad it works. We now know much more about how Zimbra works. We have resolved many other issues along the way and can now bend the product to our environment so that our environment can better serve our clients rather than having to bend our environment to the product. We did not find it particularly helpful to be told to disable most of our security, violate best practice security models, change our entire infrastructure and all of our other IT products just so that this one product would work. Although it is understandable from the point of view of containing the cost of support, it is a product centric approach rather than a customer centric one. We have now preserved our security model, our infrastructure, our other product choices, can use Zimbra in that environment and will share that knowledge with others.
We will post the resolution shortly once we have worked out the final details. |