[Dovecot] Exchange-replacement with SOGo
I thought some people here would be interested:
Recently SOGo added support for OpenChange, which means Outlook can natively access it via MAPI the same way as Exchange. Everything is open source, and the great thing about SOGo is that it uses existing IMAP server for mails rather than reimplementing yet another one itself. They seem to prefer Cyrus, but apparently Dovecot should work too. For non-mail (calendar, etc) it uses SQL, but I heard it's not too difficult to replace that either if someone would prefer some NoSQL database or something.
Hi,
On Tue, Oct 26, 2010 at 8:08 AM, Timo Sirainen tss@iki.fi wrote:
They seem to prefer Cyrus, but apparently Dovecot should work too.
I have been using Dovecot 1.2.13 with it, works just fine. Plus, sieve support's also there, which is cool.
On 10/26/2010 12:12 AM, Mohit Chawla wrote:
Hi,
On Tue, Oct 26, 2010 at 8:08 AM, Timo Sirainentss@iki.fi wrote:
They seem to prefer Cyrus, but apparently Dovecot should work too.
I have been using Dovecot 1.2.13 with it, works just fine. Plus, sieve support's also there, which is cool.
We have been using SOGo for about 9 months now and really like it. We are using our standard Postfix/Dovecot with MySQL backend for calendar and OpenLDAP for contacts. I have to wait for the openchange parts to become part of the release version before I can mess with it too much. It would be nice to be able to have a BES server talking to SOGo through openchange .
Op 26-10-2010 4:38, Timo Sirainen schreef:
I thought some people here would be interested:
Recently SOGo added support for OpenChange, which means Outlook can natively access it via MAPI the same way as Exchange. Everything is open source, and the great thing about SOGo is that it uses existing IMAP server for mails rather than reimplementing yet another one itself. They seem to prefer Cyrus, but apparently Dovecot should work too. For non-mail (calendar, etc) it uses SQL, but I heard it's not too difficult to replace that either if someone would prefer some NoSQL database or something.
Interesting.
Now I wonder whether this already supports the SOAP-based EWS protocol, which is - apparently - MS's new alternative to MAPI. Well, unlike MAPI, it is appears to be well-documented [1], making development in that direction relatively straightforward I can imagine.
Regards,
Stephan.
participants (4)
-
Donny Brooks
-
Mohit Chawla
-
Stephan Bosch
-
Timo Sirainen