Sogo
Thanks to sebastia@, I learned that SOGo was not build on OpenBSD/macppc (4.9) because GNUstep wasn’t:Continue reading...
I’m running SOGo 1.3.5 on a Debian GNU/Linux 5 with the Web front-end installed on NetBSD 5. Today is the day when I upgrade SOGo to 1.3.6.Continue reading...
Learn more about SOGo here .
Quickly sumed up, SOGo is a kind of middleware that will provide Web, CalDAV and CardDAV access to you e-mail and web clients. You can check my NetBSD and OpenBSD articles to see how to build the backend Mail/Directory/SQL services. Once this is done, you can plug SOGo on to this architecture and provide E-Mail, Calendar, AddressBook to your users via mobile phones and mail clients.
I’ll describe here how to setup the sogod backend onto Debian GNU/Linux and the Web frontend onto NetBSD.Continue reading...
On my way to move from Zarafa to SOGo, I needed a way to migrate my e-mail between the two systems. Both provides IMAP capabilites and that’s the service I’m gonna use to move the data.
You can either copy/move the e-mail manually using your favorite IMAP client or automate the migration using imapsync.Continue reading...
Quoting SOGo: Open Source Groupware homepage: SOGo is groupware server with a focus on scalability and open standards. SOGo provides a rich AJAX-based Web interface and supports multiple native clients.
It is a set of access tools to your Mail, Calendar and Address book. It provides Webmail, a CalDAV and a CardDAV services. It also enables integration with native clients, like Mozilla Thunderbird, Microsoft Outlook and Apple Mail.
The difference with M$ Exchange is that it is Open Source software. The difference with Zafara or Zimbra is that it doesn’t come with its own backend ; it sits on top of some already running SMTP and IMAP servers.Continue reading...