Caudium: The Webmail

CAMAS has been developped mainly for ISP usage. So some of first users has been ISP before others.

Oreka, a french ISP. (see it)
iTeam, the engineer students of this association which promote free software at ECE (Ecole Centrale d'Electronique, Paris) use CAMAS for accessing mail outside their school.
Linkeo, a french Application Service Provider specialized in Consumer Relationship Management tools and Web Call Centers use CAMAS as a front-end for its incoming mail processing application.
Cable & Wireless, France use it for their internal users and vISP customers in the world.
Cable & Wireless, Italy use it for their customers. (see it)
University of Le Mans, France use it for their students.
CVF a french company specialized in global business strategy based on new technologies use it for its employees.
CSL a german computer service company provides CAMAS service.
VDI a german association of engineers provides CAMAS webmail account to their members.

What is new in Camas compared to IMHO?

Quite a few things has been fixed. In general Camas is more tolerant to badly formed or non RFC compliant headers and mails.
Camas design is modular, eg you have a auth module, a layout module etc... Each of theses modules has open APIs to help developpers to make new interfaces.
Because modules are small and loaded only if needed, they are more easy to develop, maintain or add new features.
We have also a lots of features that IMHO don't have, and mainly ISP and B2B oriented like sitewide signature (signature added when sending a mail like Yahoo's or Hotmail's ones).
Templates are compatibles between IMHO and CAMAS. Some new features and customizations can be done in CAMAS, but not on IMHO.

Is Caudium a successor to IMHO

No. We have forked a from IMHO to Camas because we think that nonolitic module cannot be a viable developpement model. Camas works only (for now) on Caudium, IMHO works AFAIK on all Roxen's webserver and maybe on Caudium (not tested recently).
Because we decided a another development scheme, we start at version 1.0 opposed to 0.98.x to show that Camas is something completly new.

Do you have a version number scheme?

Yes. It's inspired by the Linux version scheme. This scheme will fall in effect after the first release of Caudium. All stable version will have an even second digit (1.0, 1.2, 2.4 and so on) while unstable/developer version will have an uneven digit. Also the build number will always be uneven for CVS / snapshot versions but even for actual releases. I.e after the release of 1.0.10, the CVS version of the 1.0 branch will be 1.0.11. This way we can distinguish releases from CVS versions.
Our release scheme is equally simple. When a release is near, the code will be feature frozen. Testing of the code will start and any bugs fixed. When we no longer find any obvious bugs, the code is frozen and a tar-ball is build - this is release candidate 1 or rc1. This will be tested and only important bugs will be fixed (minor ones like typos will not be fixed after the code freeze). If RC1 is unsatisfactory (major bug found for example), bugs will be fixed and RC2 will be released. Once the RC is satisfactory the last stable one will be named the actual release.

Why should i use Camas instead of IMHO?

Many reasons could be listed here. The main one might be that you are a Roxen 1.3 user, and you don't have the resources to rewrite your RXML pages. Also you might not agree the direction Roxen 2.x is heading. It's up to you to make up your mind.

Why Camas? Does it mean something?

CAudium Mail Access System.

What Caudium version do I need?

Any Caudium version is supported. Because of caching problems with Microsoft Internet Explorer, we recommand Caudium 1.1.3 or greater that have corrected such problem.

What operating systems will you support?

Camas is supported on every OS that support Caudium, e.g. every un*x that Pike runs.

HTML OK CSS	Copyright © 2000 - 2005 The Caudium Group All Rights Reserved. Hosting by Kazar.