History: Why Cyrus IMAP and Cypht
Preview of version: 15
Not published yet
Mail functionality in WikiSuite is handled as follows:
- Cyrus IMAP which is a ClearOS app
- Cypht, a webmail client which is integrated in Tiki Wiki CMS Groupware (starting in Tiki20)
- SabreDAV for CalDAV and CardDAV support.
Please see general component criteria and the other Software Components for WikiSuite.
Why Cyrus IMAP and Cypht instead of the many options in this space? Very good question! In one word: JMAP
Why Cyrus IMAP
- The de facto mail system in ClearOS
- JMAP support
- Very active development
- Fantastic community and leadership, and weekly community meetings
- Longevity: started in 1993!
Why Cypht
- Written in PHP
- Jason Munro, the Lead developer, is doing a fantastic job with the project
- Available on Packagist
- Lots of features
- Added JMAP support
Why not Roundcube
- Roundcube is a fantastic webmail and we used as part of Kolab
- No JMAP: https://github.com/roundcube/roundcubemail/issues/5918
- While it's in PHP, there is no way to get via Composer/Packagist: https://github.com/roundcube/roundcubemail/issues/5938
Why not Kolab
- Kolab is a great standalone mail stack suite. Kolab was the mail stack component in WikiSuite for the first few years, but it was too much work to integrate tightly and thus, it stayed quite standalone from the rest of WikiSuite. So we moved to a more tightly integrated solution.
- Kolab uses Roundcube, which doesn't support JMAP
Why not Apache James
- Apache James supports JMAP so it could have worked, but it would be too much work to integrate nicely with ClearOS
Why not SOGo
SOGo is a very interesting solution, and was a strong candidate. However, no JMAP support, and it would have not been as tightly integrated as the chosen solution. SOGo is written in Objective-C (vs Cypht in PHP)
Why not Dovecot
Why not Gmail
- Not Open Source
- https://mako.cc/copyrighteous/google-has-most-of-my-email-because-it-has-all-of-yours
Why not Office 365
- Not Open Source
(to do: add all the other options)