home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 35 Internet
/
35-Internet.zip
/
wbmail10.zip
/
read.me
< prev
next >
Wrap
Text File
|
2000-11-02
|
6KB
|
177 lines
WebMail/2 - READ.ME
-------------------
Welcome to WebMail/2.
This file contains information you need to install WebMail/2.
This README file is divided into the following categories:
- Before You Install WebMail/2
-Software Requirements
-Hardware Requirements
- Getting Help
- Installing WebMail/2
- Late-Breaking News
Before You Install WebMail/2
----------------------------
Software Requirements
---------------------
WebMail CGI
-----------
Any OS/2 webserver which can execute rexx CGI scripts.
WebManager
----------
OS/2 Warp 3 or better.
VROBJ.DLL: ftp://hobbes.nmsu.edu/pub/os2/dev/rexx/vrobj21d.zip
An email server
---------------
Any POP3/SMTP email server. Then dont need to run under OS/2,
but the supported OS/2 email servers have some advantages.
Hardware Requirements
---------------------
A computer capable of running OS/2.
Getting Help
------------
Please contact the author of WebMail/2:
Author: Dimitris 'sehh' Michelinakis
Email : sehh@altered.com
Installing WebMail/2
--------------------
unzip each file to the correct place:
cgi.zip
-------
Place: Unzip in your /cgi-bin directory
Then edit webmail2.cmd and change the lines at the top, which define
the ip and port of the authentication daemon, or your own authentication
method. Make sure you only use IP addresses, not hostnames!
You shouldn't need to change anything else, unless you want to change
the way the CGI procedures work.
webmailhtml.zip
---------------
Place: In the path you specified in the CGI, or under %etc%\webmailhtml
if you didn't define a directory.
Edit the .wm files, and change them to suit your needs. They are
just examples for testing WebMail/2. The default directory placement
is under %etc%\webmailhtml
NOTICE: Some .wm files don't use the header.wm/footer.wm, like the
user login.
The .wm files can be anything. In them you define variables which
the CGI script parses before send it the output to the client.
webmailimages.zip
-----------------
Place: under /webmailimages/ in your web server html dir.
You can change it, but you'll need to modify the .wm files first.
Its a good idea to create an alias of /webmailimages/ and make it
point to a place that suits your needs.
dll.zip
-------
Place: Put those dlls somewhere in your LIBPATH or the currect directory
that WebManager runs from.
Those dlls are needed only if you user IPS or Inet.Mail/Inet.MailPro.
webmanager.zip
--------------
Place: Unzip and place anywhere you like.
This is the daemon, make sure you configure all the options. Please only
use IP addresses and not hostnames.
Status page
-----------
This page has some statistics and debug information.
Users page
----------
This page allows you to add/remove users when using the Internal
user database authentication. In all other cases its not needed.
Settings page 1
---------------
Section 1
---------
Here you define the port that webmanager listens to, the inactivity
timeout that passes before users are automatically logged off, and
user refresh time which defines every how long to check for the
existance of the file 'refresh.usr' in the current directory. If a
file with that name exists, then webmanager will refresh the user
database from the POP3 server. This is only used for the supported
OS/2 email servers.
Section 2
---------
Define the IP addresses and the ports of the POP3 and SMTP servers.
Section 3
---------
Choose the user database that WebManager uses to authenticate the
users. If you have one of the OS/2 supported email servers then
chooce the appropriate one, else either choose Internal Users or
Generic POP3. The internal users database is a user/password list
that WebManager keeps, the Generic POP3 makes the WebManager to
login to the POP3 server to authenticate the user before allowing
connections from webmail2.cmd.
Settings page 2
---------------
If you enable the alert program, then if a number of failed authentication
attempts is reached then the defined program is executed.
Access page
-----------
Section 1
---------
Add the IP addresses of your webservers which run webmail2.cmd and
are allowed to access your webmanager for authentication. You can
also use this notation to define ranges of IPs:
10.10.10.0, would allow from 10.10.10.1 to 10.10.10.xxx
192.64.0.0, would allow from 192.64.1.1 to 192.64.xxx.xxx etc.
We suggest you define individual IP's for security reasons.
Section 2
---------
Add the IP addresses of the clients (web browsers) who are allowed
to access the webmail2.cmd. You can also use this notation to define
ranges of IPs:
10.10.10.0, would allow from 10.10.10.1 to 10.10.10.xxx
192.64.0.0, would allow from 192.64.1.1 to 192.64.xxx.xxx etc.
0.0.0.0, would allow ALL ip's.
Late-Breaking News
------------------
There are a few issues that you have to keep in mind:
1) Webmail/2 won't detect a locked email account correctly.
2) TCPIP timeouts are not reported, you just get a 'no data' error.
3) The refresh.usr is not deleted after WebManager has finished
the user database refresh.
4) Uploading a file bigger than 100kb will take a very long time to
convert to MIME encoding.