summaryrefslogtreecommitdiff
path: root/web/README
blob: d2be6c488303a2644846ac3944ef7f03af08096f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
/* ========================================================================
 * Copyright 2006-2007 University of Washington
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * ========================================================================
 */


WEB ALPINE
----------

Web Alpine is the web-based component of the Alpine Mail System.  It
rests on the same distributed email technology behind Alpine, but is
accessible from almost any browser on the World Wide Web.

Web Alpine uses TCL to provide the programmatic interface between
the Alpine-provided message store and the cgi-served web pages.


REQUIRED SOFTWARE
-----------------

  Base system:
	C compiler
	Tcl scripting package and development tools
	OpenSSL
	Apache web server (though, presumably any CGI supporting
	                   web server should work)

  Optional:
	ispell application
	  Used to support composer spell check functinoality.
	  Featured not offered if ispell not present.

	openLDAP
	  Provides LDAP query services to support login
	  personalization and user-session LDAP query support.

	UW Pubcookie
	  Provides central web-login management.  Note, additional
	  configuration and installation steps are required.  See
	  src/pubcookie/INSTALL for specific instructions.

	Kerberos 5
	  Required by UW-Pubcookie to provide authentication and
	  proxy authorization for IMAP server access.  Proxy
	  authentication only tested under UW imapd.

 

BUILDING AND INSTALLING WEB ALPINE
---------------------------------

See the INSTALL file for basic instructions.


DOCUMENTATION
-------------

User documentation is contained within the application and is
reasonably complete.  Technical documentation is extremely rough and
likely unsatisfying.  It's probably worth reading, but ultimately
configuration or other questions are best answered by reviewing the
source (which itself, while working reasonably, is somewhat spotilly
documented as well).


SUPPORT AND FEEDBACK
--------------------

Send comments and questions to <chappa@gmx.com>