This is the full detailed features for CAMAS. Detailed, on each CAMAS modules or function.

• Clients can change IP address during a session. Note this option is to activated by the administrator and is not garantee to work if you have a cluster of CAMAS behind a load balancer.
• SSL support using Caudium SSL support. Note that some navigator has bad SSL support. Microsoft Internet Explorer is not really smart on SSL support. We strongly recommand to upgrade your MSIE to at least MSIE 6.0 SP1 if your favorite browser is MSIE.
• SSL support can be enforcered e.g. http://webmail.foo.com can be automaticaly redirected to https://webmail.foo.com by a the administrator
• SSL can be automaticaly desactivated if navigator client doesn't support it correctly (using Caudium's support database) by administrator
• IMAP and/or SMTP error can be shown to webmail user
• New mails can automaticaly shown in a little popup for the end user. This option can be configured by administrator and by the correct functions inside webmail template
• New user can go when they login for the first time directly on preference screen instead of mail index screen, this option is activated by the administrator
• Persistent IMAP session timeout configurable by administrator. 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.
• URL name can be forced by administrator
• Session garbage collector
• Runtime admin interface to see how many users are on line, what mailbox they are doing, statistics on IMAP mails, mail sents...
• 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.

• Choice of image formats that can be displayed
• Choice of date format to be displayed
• Displaying of delay of mails eg the time between reception of mails in the server and diplaying in webmail. This can be either images or formated text
• Limitation of the size of displayed subject header or from header
• Links in mail can open a new navigator window
• MIME type can be remapped e.g. application/foo can be remapped into text/plain
• Configurable maximal size of a displayed mail

• When sending mail administrator can specify the charset used
• Automatic Copy of sended mail into sent-mail folder
• Incomplete mails can be automaticaly completed with a default domain name configured by the administrator
• IP address of mail writer can be added inside the mail with a X-Originating-IP header. Usefull for Abuse/Spamming problems
• User specified mail headers can be optionaly added into sent mail
• Receipt (user agent or mail transport agent) can be used. Note that MTA Receipt is depending of support to MDN in SMTP transport subsytems
• Attachements
• Organistation header (site wide and/or user configurable)
• Global webmail signature like public well known webmail configurable by administrator
• SMTP server can be local (/usr/lib/sendmail) or remote (using plain SMTP)
• UTF-8 support
• Spelling support using ispell or aspell
• Anwsered mail can be automaticly saved into anwsered folder (Camas 1.2+)
• Prefix / Suffix in for example subjects can be configurable by administrator (e.g: Re:, Fwd:, ....)
• Automatic Bcc address can be specified by the user

• Can import text format addressbooks from Outlook/Excel/CSV, LDAP/Ldif, Pine addressbook format. The format is automaticaly found by CAMAS.
• Optional global addressbook (file format or configuration interface) that can be configured/activated by administrator
• Optional LDAP addressbook that can be configured/activated by administrator
• Addressbook can contain virtualy unlimited header, configurable by administrator
• Addressbook doesn't need an external database to store its data. It is stored inside a IMAP folder on the imap server
• New addresses can be added by selecting email when reading a mail
• Combo box (with To, Cc, Bcc) screen can be used to do multiple adds when composing mail

• User can store some files on server that can be retreived between sessions
• This space can be limited by software quota

• Automaticly create usefull folders like : "sent-mail", "drafts", "trash" and "answered"
• Mail filters
• Administrator can hide several folders
• IMAP folders can be encoded (e.g. if you use > 7 bits characters in folder names)
• Quota utilisation can be displayed
• Folder list can show numbers of mails that have been seen, not seen and the total size of the folder this can be configurable by administrator
• Acces to shared IMAP folder (note that this is work in progress for Camas 1.2+)

• Display HTML mail or treat them as a sperated attachment
• Domain name added at login screen
• Administrator can allow user to modify some options (email adress, Names, Languages, Signature, Company, ...)

• Optional LDAP auth system, with ability to choose IMAP server from LDAP
• Optional Flat file or /etc/passwd support
• IMAP login can be used as login password with possibility to handle serveral imap server differenciated by domains
• Complete API to create you own authentication system if you don't use use LDAP, Flat files or nothing

• Default layout in a module. Administrator can remove it if it is not used
• Form buttons can changed to use image instead, either using special name conventions or use a flat file where this can be specified using any HTML/RXML tags.
• Layout compatible with IMHO webmail (Note this support will be deprecated on 1.3/1.4 version of CAMAS)
• Custom icons can be used in mail index display
• Layout can support frames
• Layout can either in a big RXML file (IMHO way) or a in separate files according to each screen diplayed (eg mailindex, mailread, ...)
• Full customization of the webmail using RXML and XML-like entities (Only in CAMAS 1.2+)

• HTML 3.2 mails can be displayed
• Some tags/containers can be authorised/forbidden to display eg. <script>
• CSS and Javascript include can be deleted
• Automatic relocation of link to a new window of URL in mails
• HTML mails can be reloacated in a <IFRAME ..> to avoid problems with RXML layouting and HTML contents (Only in CAMAS 1.2+)

• 100% Layouting is compatible with IMHO
• IMHO compatiblity can be unloaded if you don't need it (Only with CAMAS 1.2+)
• Compatible with IMHO plugins (deprecated and will be dropped in 1.3/1.4 version of CAMAS)

• Tool to make translation without any programming knowledge : CALTA
• Compatible with IMHO language files
• 13 supported languages : English, French, Catalan, Czech, Dutch, Spanish, Italian, Estonian, Finnish, German, Hungarian, Polish, Portuguese and Swedish. Spanish, French, Italian, Polish and Swedish are natively handled by CALTA

• Errors and/or Actions can be logged into a flat file or in syslog ( Only in CAMAS 1.2+)
• Errors and/or Actions can be logged into a SQL database
• API to create your logger module for you own needs (billing...)