> > This describes exactly the point of view of administrative staff. They > > live in Microsoft Office, and they need a server to support it. That is > > the assignment given. > > I was looking at Open-Xchange on the web <http://www.open-xchange.com/>. > > The server provides webmail and MAPI interfaces. The "Hosting Edition" > > (and maybe the others, it is not clear) can talk to Cyrus and includes > > ACL support. > > (We're still running both Exchange for admin staff and Cyrus for the > > much larger university community of faculty and students.) > Perhaps things have improved since my last foray into this area, but > I've yet to find an "outlook connector" that was stable and didn't > corrupt the hell out of the users PST. And at least with the Kolab Never had a corrupt PST using ZideLook (the Outlook plugin for OpenGroupware). Make sue they provide a *real* MAPI provider for outlook and not some background sync thingy (as several Open Source Outlook connectors do or at least did). > groupware product when I reviewed it, they made several architecture > decisions that completely killed performance and then they went on to > trivialize my concerns. Storing calendar objects as binary attachments > in an IMAP store, effectively making them unsearchable, meant that every > calendar access had to pull the entire store down, process it and > display it. Not cool. Yep, the Kolab architecture goes in the "what are you, nuts?" column.
Attachment:
signature.asc
Description: This is a digitally signed message part
---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
