head	1.4;
access;
symbols
	CAMAS_STABLE_1_0:1.3.0.2
	caudium_1_0_11:1.2
	caudium_1_0_10:1.2
	stable_1_0:1.2.0.4
	caudium_1_0_9:1.2
	caudium_1_0_8:1.2
	caudium_1_0_7:1.2
	caudium_1_0_6:1.2
	caudium_1_0_5:1.2
	caudium_1_0_4:1.2
	caudium_1_0_3:1.2
	caudium_1_0_2:1.2;
locks; strict;
comment	@# @;


1.4
date	2001.08.20.17.23.00;	author kiwi;	state dead;
branches;
next	1.3;

1.3
date	2001.01.13.04.16.33;	author neotron;	state Exp;
branches;
next	1.2;

1.2
date	2000.11.10.10.23.32;	author grendel;	state Exp;
branches
	1.2.4.1;
next	1.1;

1.1
date	2000.11.10.02.41.08;	author kiwi;	state Exp;
branches;
next	;

1.2.4.1
date	2001.01.08.19.30.48;	author neotron;	state dead;
branches;
next	;


desc
@@


1.4
log
@Removed old files
@
text
@----[ CAMAS ]--------------------------------------------------------

This CAMAS - CAudium Mail Access System for Caudium (or compatible)
web server (http://caudium.net, http://caudium.org).

CAMAS is based on IMHO, see the CREDIT file.

CAMAS is Copyright  2000-2001 The Caudium Group


----[ Why CAMAS ]----------------------------------------------------

CAMAS is a fork of IMHO 0.97.1, with a lots of new added functions.

We added a lots of functions to 0.97.1, such as :

 o Mail filters,
 o Size of the folders,
 o Customizable login, logout, compose mail screens
 o Bugs corrections, etc...

Code was split into pmod and .h files to help third-party vendors
make modifications easily.

The sessions system is now based on Kai's 123session module, this helps us
to have more flexibility and maybe the capability to have a cluster
of CAMAS behind a load balancer without any IP persistence system.

A lots of site-wide functions were added to help the administrator in
setting up the defaults e.g. for a commercial webmail system.

----[ Compatibility ]------------------------------------------------

Our aim is to have the most compatible system between IMHO and CAMAS,
if there is some improvement in IMHO we back port it into CAMAS, and
we would wish that the IMHO team have a look into our code to 
add new functionality to their product as well :)

----[ Documentation ]------------------------------------------------

IMHO has a really bad drawback: almost no documentation. The best
way to find the documentation on the layout format is: "use the source, Luke!".
For professional environment this is not acceptable. So we 
expect to create a lots of documentation and give some complete examples
of professional templates to help this tools be accepted by the
professional staff.

----[ EOF ]----------------------------------------------------------

$Id: README,v 1.3 2001/01/13 04:16:33 neotron Exp $
@


1.3
log
@It's 2001 now.
@
text
@d50 1
a50 1
$Id: README,v 1.2 2000/11/10 10:23:32 grendel Exp $
@


1.2
log
@- proof read the CAMAS docs
- added index.htm to the directory parsers - lotsa people still use
  FrontPage... and micro$oft still refuses to acknowledge that .htm
  extension is a stone age, perverted idea... :P
@
text
@d8 1
a8 1
CAMAS is Copyright  2000 The Caudium Group
d50 1
a50 1
$Id: README,v 1.1 2000/11/10 02:41:08 kiwi Exp $
@


1.2.4.1
log
@Removed CAMAS from 1.0.
@
text
@d50 1
a50 1
$Id: README,v 1.2 2000/11/10 10:23:32 grendel Exp $
@


1.1
log
@Adding some documentations about CAMAS
@
text
@d4 1
a4 1
webserver (http://caudium.net, http://caudium.org).
d6 1
a6 1
CAMAS is based on IMHO, see CREDIT file.
d13 1
a13 1
CAMAS is a fork of IMHO 0.97.1, why a lots of new missing functions.
d15 1
a15 1
We added a lots of functions under 0.97.1 like :
d19 1
a19 1
 o Customizable login, logout, compose mail, screen
d22 2
a23 2
Code has been splited into pmod and .h files to help third people
make modifications easy.
d25 1
a25 1
Sessions system is now based on Kai's 123 session, this help us
d27 1
a27 1
of CAMAS behind a loadbalancer without any ip persistance system.
d29 2
a30 3
A lots of site wide function has been added to help administrator to
setup default functions and comportments e.g. for commercial webmail
system.
d35 3
a37 3
there is some improvement in IMHO that is back ported into CAMAS, and
we wishes that the IMHO team will have a look into our code to 
add new functionnalities too :)
d41 6
a46 6
IMHO has a really bad drawback : allmost no documentation, the best
way to find the documentation on layers was : "use the source luke!".
For professionnal, environment this cannot be acceptable. So we 
expect to do lots of documentation and give some complete examples
to do professionnal templates to help this tools be accepted by
professionnal people.
d50 1
a50 1
$Id$
@

