My point is that kolab can provide all the things you describe (as Vlad states, you can integrate with AD authentication with some effort) and (since it retains Cyrus as its mailserver) should require no transfer of your existing mail.
I suppose the question you have to consider is whether your Zimbra clients constitute a larger user base than your cyrus ones... and whether the Zimbra users come with a perpetual license for the professional edition, I suppose :)
G
On 4 March 2015 at 17:40, Andres Tarallo <atarallo@xxxxxxx> wrote:
2015-03-04 15:16 GMT-02:00 Geoff Winkless <cyrus@xxxxxxxx>:[..]Incidentally, a question for the OP: why change from Cyrus to Zimbra? If you want collaborative features, wouldn't Kolab do the job (and therefore allow you to keep your Cyrus backend)?Cyrus IMAP is part of an old in-house developed mail solution. I've deployed solutions like that, with small changes, for a while. That solution requires more skilled it staff for trivial tasks like provisioning of new accounts.We found in zimbra a more polished solution, capable of integrating with active directory with a reasonable effort. In that way we keep a single password and account for select users. The admin panel let's our less skilled IT staff take care of more tasks than they actually do. The webmail has a familiar look for people exposed to outlook (most of our users).We can't afford developing a new in-house solution, or enhace the shortcomings of the one we have now. An last, but not least, we purched recently free new domains that have mail handled in a zimbra server. In this case will be doing migration and consolidation.Andrés
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
