From Kolab wiki

Contents 1 Google Summer Of Code 2006 Ideas 1.1 Web Admin interface cleanup or complete rewrite 1.2 Horde webmail Integration 1.3 Kolab auto-upgrade service 1.4 Kolab Certification Authority services 1.5 Kolab OpenSSH server integration along with SSH KEYS handling trough LDAP 1.6 Kolab Server Specialization 1.7 Kolab Murder Server integration 1.8 Kolab Cyrus 2.3 High availability and replication testing 1.9 Kolab centralized log management and analisys 1.10 Auditing support 1.11 Kolab Antivirus & Antispam management support

Google Summer Of Code 2006 Ideas

These are just ideas that have propesed by Fabio Pietrosanti on the kolab-devel (at) kolab.org e-mail list.

Web Admin interface cleanup or complete rewrite

• We should ask for "feature proposal" on the lists for what would be welcome for web administration features and have them implemented by a good php coder. The webadmin interface require serious enhancements imho.
• Integrate a very good logic to manage transport and routing

I (Fabio) still propose to have a complete rewrite based on Horde code which is stable and doesn't "reinvent" the wheel.

Horde webmail Integration

• Develop an horde ldap datatree driver (this would allow the removal of MySQL dependency)
• Enanche the Horde Kolab Driver (fix the passwd, fix multidomain support, fix the security framework (doesn't connect to ldap as manager), etc)
• Customize the OpenPKG apache/php modules in order to support Horde
• Develop a horde package for Kolab
• Integrate the webadmin

Kolab auto-upgrade service

• Develop a custom method for Kolab OpenPKG auto-update (usable only in non customized installation)

Kolab Certification Authority services

• Develop a web frontend for the management of digital certificates of all the kolab servers
• Develop a daemon that would allow the provisioning of files between the master and the slaves (or use the OpenSSH server integration)

Kolab OpenSSH server integration along with SSH KEYS handling trough LDAP

• Integrate OpenSSH server with the support for RSA key management/publication/revocation in the Ldap Server
• Use this system to implement transparent file exchange and log-in using RSA keys between Kolab Servers

Kolab Server Specialization

• Implement in the kolab logic the methods to have dedicated server (in every place where there is 127.0.0.1 this have to be configurable). In that way every "component" could be dedicated (for example an antivirus server or a mail relay or a Cyrus backend or a webadmin, etc)
• Other than the internal-logic all the configuration should be configurable through web admin interface

Kolab Murder Server integration

• Integrate support for Cyrus murder in order to allow transparent access on Kolab Cyrus Services

Kolab Cyrus 2.3 High availability and replication testing

• Analyze the functionality of Cyrus 2.3 trasparent replication and how this could be implemented in Kolab
• A prototype implementation should be implemented (This because cyrus 2.3 is still not release and we cannot use such release)

Kolab centralized log management and analisys

• Implement the framework to support remote syslogging (through syslog-ng openpkg package)
• Implement log analisys logic and software to monitor the status and activity of EACH kolab server
• email traffic and statistics
• http traffic and statistics
• cyrus traffic and statistics
• antivirus & antispam statistics
• Implement the webadmin logic to view and manage such statistics

Auditing support

• Implement all the logic in the web admin interface to support "auditing" of management activity:
  Who created a user? Who changed the password? Who logged in and when?

Kolab Antivirus & Antispam management support

• The policy of Antivirus and Antispam should be configurable trough the webadmin interface.
• A queue of quarantined messages should be created and this should be managed via web.