Administrator of the Caudium web server can entirely setup his CAMAS module using the HTML-base configuration interface. You can tune Camas to own needs with 250 configuration options.

CAMAS is available in many languages (English, French, Catalan, Czech, Dutch, Spanish, Italian, Estonian, Finnish, German, Hungarian, Polish, Portuguese and Swedish).
Even in the case yours hasn't been written yet by anyone, a tool, named Calta is included to write it yourself.

CAMAS runs templates files whose rules the look of the screens. Writing your own template only require little HTML skills. RXML, JavaScript, Flash etc can be used too in order to get CAMAS look as you want.
A button generation engine is available for on-the-fly rendering: no needs to draw all buttons for each features in all languages. Once created, the images are cached until their destruction by the administrator-configurable garbage collector for a quick service.

Administrator can choose which parameters the users can set themselves, according their computer skills, such as: email address, name, language, template, signature, extra headers, idleness session expiration time, SMTP server and so on. Currently two user preferences modules are available so that you can store and retrieve information from IMAP server or SQL database. An API is available so that you can develop your custom preferences module.

Several modules are available to guess user's domain name, IMAP server, ... Currently available mechanisms are standard Unix file, SQL and LDAP.

Administrator can manage an address book all his users can read from. The address book (named global address book), can be a simple flat file, an list of email addresses given on the Configuration interface of a LDAP server.

Manage your contacts directly in CAMAS, and import them from MS-Outlook, MS-Excel, Netscape Messenger or Pine address book.

Administrator can specify a side-wide signature (eg service/company name, disclaimer...)

Color and icons for mails can be configured to evolve during time for unread mails.

Uses of aspell or ispell to check your prose.

Users can automate the storage of emails in directories by specifying filters on email addresses, dates, CC fields, words in subjects or body. Without the need to install on the IMAP server software like maildrop or procmail.

Filter rules about sender's email address can be set each time the user stores an email into a directory. So, next time an email from this user is received, it will be stored into this directory.

Support for both DSN and MDN delivery notification.

Administrator can disallow JavaScript and insecure HTML containers and tags.

Once logged, users are tracked by 123session mechanism with cookies or without.

The IMAP client keep track of the session using a non blocking mecanism so that you can run multiple users on the same server without any freeze time due to IMAP server.

Camas cache message's headers in memory for fast access. The IMAP client feed this cache in the background at login time so that users feels Camas very fast. This cache also allows us to search in memory in mails instead of asking the IMAP server thus making it the fastest MUA search tool available. This also implies operations like searching in several mailboxes. Morever some cache for HTML rendering have been added.
Finally Camas benefit from the Pike/Caudium architecture, it uses threads and Pike's speed.

Latest Camas are now really modular. Lots of modules follow an object oriented model with overloading and priority managed by Camas core. For example within the Auth modules type, you can load several modules types like LDAP and SQL and assign priority to each of them. You can also extend Camas code with your own actions modules and RXML tags.
Also note that with RXML templating, the code is completely separated from the HTML output.