home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 35 Internet
/
35-Internet.zip
/
os2pops.zip
/
os2pops.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1997-05-08
|
303KB
|
1,457 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
This POP server was written with the administrator in mind. Functions such as
stopping and starting the server as well as client definition and modification
are easily done through the graphical interface. The functions of the POP
server are easily monitored with the status window that is provided. Extensive
logging is also provided to assist in problem determination if it should be
required.
The logging of client connections as well as the number of mail items delivered
along with the actual amount of data delivered provide the framework for
reporting on the activity of your POP server. This information also provides a
way to discover clients that may no longer be using your POP server as well as
clients who may be receiving very large amounts of data.
OS2PopS has been in production since May 1996 serving over 3,000 clients within
IBM. The latest information about OS2PopS may always be found on the Web at
http://www.raleigh.ibm.com/misc/os2pops
ΓòÉΓòÉΓòÉ 2. Copyright ΓòÉΓòÉΓòÉ
This program and the contents of the ZIP file it was contained in are
copyrighted by IBM Corporation.
(c) Copyright IBM Corporation 1996, 1997 - All rights reserved.
ΓòÉΓòÉΓòÉ 3. History of Changes ΓòÉΓòÉΓòÉ
Change History
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéDate ΓöéVersΓöéIntΓöéDescription Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé03/31/96Γöé0.01ΓöéDJMΓöéFirst release. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé04/14/96Γöé0.02ΓöéDJMΓöéMajor reformat of install screen. Changed INI Γöé
Γöé Γöé Γöé Γöéinformation to root directories only. Each area, Γöé
Γöé Γöé Γöé Γöéuser file, mail, accounting, and log, has its own Γöé
Γöé Γöé Γöé Γöédirectory below the server root. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé04/17/96Γöé0.03ΓöéDJMΓöéCompleted client maintenance details. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé04/25/96Γöé0.04ΓöéDJMΓöéAdded data items sent and number of bytes to the Γöé
Γöé Γöé Γöé Γöécontrol panel. Removed some of the messages that Γöé
Γöé Γöé Γöé Γöéwere going to the status window to reduce the Γöé
Γöé Γöé Γöé Γöéclutter. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé04/26/96Γöé0.05ΓöéDJMΓöéAdded maillock empty file to a clients mail Γöé
Γöé Γöé Γöé Γöédirectory when they log in to prevent the same Γöé
Γöé Γöé Γöé Γöéclient from connecting a 2nd time. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé04/28/96Γöé0.06ΓöéDJMΓöéAdded handling of the TOP command. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé04/30/96Γöé0.07ΓöéDJMΓöéAdded checking and cleanup of lock files during Γöé
Γöé Γöé Γöé Γöéinitialization. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé05/05/96Γöé0.08ΓöéDJMΓöéMoved client counter update into a single routine Γöé
Γöé Γöé Γöé Γöéto make sure it's always updated correctly. Added Γöé
Γöé Γöé Γöé Γöéchecking to make sure the Rexx functions we need Γöé
Γöé Γöé Γöé Γöéget loaded correctly (including the socket Γöé
Γöé Γöé Γöé Γöéfunctions). If they don't load correctly we'll Γöé
Γöé Γöé Γöé Γöéshow an error message and die. Changed INI file Γöé
Γöé Γöé Γöé Γöéfor main window position, status window position, Γöé
Γöé Γöé Γöé Γöéand status window colors and font to be single Γöé
Γöé Γöé Γöé Γöévalues (MainPos, StatPos, StatLooks). Changed theΓöé
Γöé Γöé Γöé Γöécall to VRSet for positioning the windows to a Γöé
Γöé Γöé Γöé Γöésingle call instead of a call for each portion of Γöé
Γöé Γöé Γöé Γöéthe window positioning. Force all user IDs to Γöé
Γöé Γöé Γöé Γöélower case in client maintenance when adding Γöé
Γöé Γöé Γöé Γöéclients. Forcing IDs to lower case was also done Γöé
Γöé Γöé Γöé Γöéin POPSMAIL to make sure things are consistent. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé05/10/96Γöé0.09ΓöéDJMΓöéMinor cleanup and double check for ways the clientΓöé
Γöé Γöé Γöé Γöécounter could get out of sync. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé05/15/96Γöé0.0AΓöéDJMΓöéChanged our INI values to only store the root Γöé
Γöé Γöé Γöé Γöédirectory to where we store things. The rest of Γöé
Γöé Γöé Γöé Γöéthe directories may be derived from the root and Γöé
Γöé Γöé Γöé Γöéwe can add any we might need easily. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé05/18/96Γöé0.0BΓöéDJMΓöéFixed a bug in the client interaction code that Γöé
Γöé Γöé Γöé Γöéwas introduced trying to handle only linefeeds Γöé
Γöé Γöé Γöé Γöéinstead of crlf from clients (like LAMPOP). Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé05/30/96Γöé0.0CΓöéDJMΓöéMoved report selection and generation out of this Γöé
Γöé Γöé Γöé Γöéprogram and made it a separate program that we Γöé
Γöé Γöé Γöé Γöéstart. This was done to avoid blocking the Γöé
Γöé Γöé Γöé Γöélistening thread and the client interaction Γöé
Γöé Γöé Γöé Γöéthread(s). Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé05/30/96Γöé0.0DΓöéDJMΓöéChanged Check_Directory routine to handle nested Γöé
Γöé Γöé Γöé Γöédirectories since we don't prevent the user from Γöé
Γöé Γöé Γöé Γöéinstalling us several directories deep. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé06/17/96Γöé0.0EΓöéDJMΓöéFixed bug in Client_Maint window that was cutting Γöé
Γöé Γöé Γöé Γöéoff client IDs longer than 10 characters. This Γöé
Γöé Γöé Γöé Γöéwas seen when trying to delete a client ID longer Γöé
Γöé Γöé Γöé Γöéthan 10 characters. Fixed focus problem after Γöé
Γöé Γöé Γöé Γöéadding/updating a client. Focus was returning to Γöé
Γöé Γöé Γöé Γöéthe main window. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé06/25/96Γöé0.0FΓöéDJMΓöéChanged client maint window to invisible in the Γöé
Γöé Γöé Γöé Γöédesign so it doesn't "bounce" as it is being Γöé
Γöé Γöé Γöé Γöépositioned. Changed client information stored in Γöé
Γöé Γöé Γöé Γöéthe client. stem in order to reduce the memory Γöé
Γöé Γöé Γöé Γöérequirements. We never really used the comment Γöé
Γöé Γöé Γöé Γöéportion of the client information anyway. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé07/07/96Γöé0.0GΓöéDJMΓöéStarted adding remote admin support. Added 2 new Γöé
Γöé Γöé Γöé Γöécode files, MonP6110 and RemotAdm, as well as the Γöé
Γöé Γöé Γöé Γöégroundwork for adding/changing/delete admin IDs. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé07/14/96Γöé0.0HΓöéDJMΓöéCompleted remote admin to the point where client Γöé
Γöé Γöé Γöé Γöéadditions will work. For now IDs and PWs are hardΓöé
Γöé Γöé Γöé Γöécoded here. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé07/24/96Γöé0.0JΓöéDJMΓöéFINALLY found and fixed the problem that was Γöé
Γöé Γöé Γöé Γöécausing delivery failures for some people. Turns Γöé
Γöé Γöé Γöé Γöéout it was probably responsible for a lot of Γöé
Γöé Γöé Γöé Γöécorruption that probably wasn't noticeable in Γöé
Γöé Γöé Γöé Γöéplain text. Turned off Trace and Info logging Γöé
Γöé Γöé Γöé Γöéuntil the settings notebook is completed. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé07/27/96Γöé0.0KΓöéDJMΓöéAdded settings notebook for logging and pruning. Γöé
Γöé Γöé Γöé ΓöéAdded registration key menu pulldown. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé07/30/96Γöé0.0LΓöéDJMΓöéAdded status window clear setting to the misc Γöé
Γöé Γöé Γöé Γöésettings notebook page. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé08/03/96Γöé0.0MΓöéDJMΓöéFixed a bug in the Quit routine that only showed Γöé
Γöé Γöé Γöé Γöéup at installation time. We can't try to log Γöé
Γöé Γöé Γöé Γöéanything until after the installation in complete.Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé08/11/96Γöé0.0PΓöéDJMΓöéAdded a display options page to the notebook to Γöé
Γöé Γöé Γöé Γöéallow control of how much detail is shown in the Γöé
Γöé Γöé Γöé Γöéstatus window. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé08/17/96Γöé0.0QΓöéDJMΓöéChanged method of passing data to AddMLEMsg so we Γöé
Γöé Γöé Γöé Γöécan allow the user to choose the level of detail Γöé
Γöé Γöé Γöé Γöéthey want displayed. Changed client abnormal Γöé
Γöé Γöé Γöé Γöédisconnect messages to W (warning) level instead Γöé
Γöé Γöé Γöé Γöéof error. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé08/20/96Γöé0.0RΓöéDJMΓöéFixed buglet that was causing the display options Γöé
Γöé Γöé Γöé Γöéto be "forgotten" and not displayed again after Γöé
Γöé Γöé Γöé Γöéthe NB had been closed. Fixed error handling in Γöé
Γöé Γöé Γöé Γöéregistration screen that would cause the Γöé
Γöé Γöé Γöé Γöéregistration screen to be closed if an invalid Γöé
Γöé Γöé Γöé Γöécombo of name and key was entered. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé08/27/96Γöé0.0SΓöéDJMΓöéFixed a typo in the Add_Client routine. It was Γöé
Γöé Γöé Γöé Γöécalling the wrong error routine if a problem was Γöé
Γöé Γöé Γöé Γöéfound while updating the user file. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé08/31/96Γöé0.0TΓöéDJMΓöéChanged main window saving and positioning to onlyΓöé
Γöé Γöé Γöé Γöéuse the Top and Left values since the window can'tΓöé
Γöé Γöé Γöé Γöébe sized. Added silent saving of the positions of Γöé
Γöé Γöé Γöé Γöéthe client maint and client details windows. MovedΓöé
Γöé Γöé Γöé Γöéretrieval of the physcial screen size into the Γöé
Γöé Γöé Γöé ΓöéINIT routine so we only have to do it once. Added Γöé
Γöé Γöé Γöé Γöémenu items to the Control pulldown to show/hide Γöé
Γöé Γöé Γöé Γöéthe status window. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé09/30/96Γöé1.00ΓöéDJMΓöéFinal cleanup for release. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé10/13/96Γöé1.01ΓöéDJMΓöéRemoved registration screen and defaulted to an Γöé
Γöé Γöé Γöé Γöéunlimited number of clients for OS2TOOLS. Added Γöé
Γöé Γöé Γöé Γöéwarning and cautions to the sendmail.cf help so Γöé
Γöé Γöé Γöé Γöépeople don't accidently destroy the tabs in Γöé
Γöé Γöé Γöé Γöésendmail.cf. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé11/04/96Γöé1.02ΓöéDJMΓöéContinued work with remote admin support. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé11/16/96Γöé1.03ΓöéDJMΓöéAdded stripping and space(0) to client values thatΓöé
Γöé Γöé Γöé Γöéare retrieved during client maintenance. Removed Γöé
Γöé Γöé Γöé Γöéextra spaces in the window list titles that we Γöé
Γöé Γöé Γöé Γöépresent for various components. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé11/29/96Γöé1.04ΓöéDJMΓöéFixed bug in the variable that was added to Γöé
Γöé Γöé Γöé Γöéconfig.sys when installing. Instead of just the Γöé
Γöé Γöé Γöé Γöédrive and path the entire name of the INI file wasΓöé
Γöé Γöé Γöé Γöébeing added (incorrectly). This caused us to Γöé
Γöé Γöé Γöé Γöéthink we hadn't been installed when in fact we Γöé
Γöé Γöé Γöé Γöéhad. Fixed a bug in detecting whether or not the Γöé
Γöé Γöé Γöé ΓöéRXSock DLL was available and the socket functions Γöé
Γöé Γöé Γöé Γöéwere loaded without error (if they weren't Γöé
Γöé Γöé Γöé Γöéalready). Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 4. Why OS2PopS? ΓòÉΓòÉΓòÉ
Some of you may be wondering why you should try OS2PopS instead of one of the
other POP servers that are available. Here are some of the reasons we think
you should give it a try and why we think you will like it.
Production proven - in use since May of 1996 serving over 3,000 clients
Ease of administration - all administrative chores are presented with a
graphical interface with ease of use a top priority
Experience - 15 years of experience with Rexx resulting in optimal coding
for the speed which is critical for a POP server
Once you have given OS2PopS a test drive we are sure you will be pleased. If
you have any questions, comments, concerns, or problems please let us know.
You may reach us by E-Mail by writing to djm@raleigh.ibm.com or by visiting
the OS2PopS Web page at http://www.raleigh.ibm.com/misc/os2pops
ΓòÉΓòÉΓòÉ 5. Requirements ΓòÉΓòÉΓòÉ
The OS2PopS POP server has no special hardware requirements but we'll try to
provide some guidance on what you will need in the Hardware section. There are
some software requirements though so we'll give you the information you will
need in the Software section.
Important Note! Installation of the OS2PopS POP server assumes that you have
installed and configured your system, including TCP/IP, before you install and
use OS2PopS.
Of particular importance is the configuration of sendmail and the sendmail.cf
configuration file for Sendmail.
ΓòÉΓòÉΓòÉ 5.1. Hardware ΓòÉΓòÉΓòÉ
There are no hard and fast rules when it comes to choosing what hardware to use
for your OS2PopS POP server. Obviously the more clients you plan on supporting
the more powerful a machine you will need.
The 2 things that will contribute most to having a server that is fast enough
to respond to your clients requests are memory and disk. The amount of memory
available and the "speed" of your disks drives will have the most impact on the
service your clients receive.
You should consider, at a minimum, a machine with the following
characteristics:
60 Mhz Pentium class CPU
16 megabytes of memory
1 gigabyte SCSI disk drive
Network adapter card or modem for connectivity
Memory
Let's talk about memory first. If you are planning on having only a few
clients, say 10 or less, you can probably get away with only 16 megabytes of
memory. Of course more is always better.
Any more than 10 clients and you'll want to consider 32 megabytes as the
minimum. Our server with 500+ clients handles them just fine with 32 meg of
memory. As always, if you can afford to have more do it.
If you will have more than 1,000 clients consider 64 megabytes of memory the
minimum. And, at the risk of being repetitive, more is always better.
Disk Drives
The capacity of the disk drives you choose is not as important as the average
access time of the disk drives. The lower the number the better. The fastest
drives you will find are SCSI drives which are available in a dizzying array
of sizes and access times.
Look for disk drives that provide 8 to 10 millisecond average access times
with 8 or 8.5 being ideal. You will find that the access times start going up
when you get above 4 gigabyte sizes so stick with those that are 4 gig or less
in size.
If you can afford it, use a system with 2 separate disk drives. The first
one, the boot drive, only needs to be 500 megabytes or so since it will
contain only OS/2 and supporting software such as TCP/IP.
The 2nd drive should be as large as you anticipate you will need to hold your
clients data. There is no way to predict that x number of clients will need y
amount of disk space so, at best, the size of this 2nd disk is a judgement
call.
Our server provides service for 500+ clients with only 650 megabytes of disk
space. If your clients may be sending or receiving large files, such as disk
images, that amount of space might not be enough.
Be very generous with disk space. Go for at least a 2 gigabyte or larger
drive. With a single SCSI disk controller you will be able to support a total
of 7 devices so you should be able to grow easily.
There are other options available that can provide large disk "images" by
presenting multiple disk drives as a single very large disk drive to the
operating system. There is nothing in OS2PopS that would prevent them from
being used.
You have probably noticed that we haven't mentioned IDE disk drives at all so
far. Although they will work just fine for your OS2PopS POP server, their
access times are usually slower than SCSI disk drives and we don't recommend
them if you will have more than a few clients.
The CPU
The CPU is close behind memory and disk drives in importance. Even with just
a few clients a 60 Mhz Pentium class machine should be considered the minimum.
If you anticipate a lot of traffic and/or a large number of clients step up to
a 133 Mhz or better machine.
Miscellaneous
The type of display you use does not matter to the OS2PopS POP server. The
main control panel and status panel will fit just fine on a screen running at
VGA resolution.
Other than the display you will need some type of connection to a network
whether it be within your company or a direct connection to the Internet. We
can't possibly try to explain all of the options you might have available in
this area so just make sure you have some sort of network card or modem to
connect to "a network".
ΓòÉΓòÉΓòÉ 5.2. Software ΓòÉΓòÉΓòÉ
The minimum software requirements for OS2PopS are:
OS/2 Warp Connect
The VROBJ.DLL revision level D or higher
TCP/IP version 3
Software to support your network card or modem connection
The VROBJ.DLL must be at revision level D or higher or OS2PopS will not work
correctly. You will need to install the DLL, which is provided in the OS2PopS
ZIP file, in a directory that is in your LIBPATH. If you have Warp Connect
installed you may find an older level of the DLL in the \grpware directory on
your boot drive.
If you have an older version of VROBJ.DLL in your \grpware directory you will
have to replace it with the version supplied in the OS2PopS ZIP file. If any
program you use has called functions in the DLL since you last booted the DLL
will be "locked" and you will not be able to replace it without rebooting.
If you have to reboot to install a new VROBJ.DLL use Alt-F1 when the little
white square appears in the upper lefthand corner of your screen. Select "C"
from the list of options that will be displayed and you will be presented with
an OS/2 full screen session. Change to the \grpware directory on your boot
drive and replace the copy of VROBJ.DLL.
ΓòÉΓòÉΓòÉ 6. Installation ΓòÉΓòÉΓòÉ
You may install the OS2PopS POP server code on any HPFS formatted drive on your
system. You may install it in any directory name you'd like but we recommend
using OS2PopS so it is easily identified.
The following installation topics will provide more details about installing
OS2PopS.
Contents of the ZIP file
Where should I install OS2PopS?
The installation screen
SENDMAIL
sendmail.cf
PopSMail
Why is HPFS required?
ΓòÉΓòÉΓòÉ 6.1. Contents of the ZIP file ΓòÉΓòÉΓòÉ
The OS2PopS distribution ZIP file should contain the following files:
ReadMe.1st - brief how to get OS2PopS installed instructions
License.TXT - IBM License Agreement
OS2POPS.ABS - OS2PopS abstract
OS2POPS.EXE - the main program
OS2POPS.ICO - the OS2PopS icon
VROBJ.DLL - VXRexx support DLL
RXMD5.DLL - DLL to support MD5 encoding (for APOP and remote admin)
OS2POPS.INF - this on-line document
OS2POPS.HLP - help on demand in OS2PopS
POPSMAIL.EXE - the sendmail "endmailer"
POPSRPTR.EXE - the OS2PopS report program
POPSRPTR.ICO - the OS2PopS report program icon
POPRADM.ZIP - the OS2PopS remote administration package
WEBREG.CMDSAMPLE - sample CMD file for registering people to a OS2PopS
POP server via the Web (using GoServe as the Web server)
SENDMAIL.ZIP - a copy of version 2.01 sendmail for OS/2
ΓòÉΓòÉΓòÉ 6.2. Where should I install OS2PopS? ΓòÉΓòÉΓòÉ
Although it doesn't really matter where you install the OS2PopS POP server
code, we highly recommend putting it into a directory named OS2PopS. This
makes it easier to identify and find. The only requirement OS2PopS has is that
it MUST be installed on a drive that has been formatted with HPFS. See Why is
HPFS required? for details on why an HPFS formatted drive is required.
The other thing you need to consider is how many clients you anticipate having.
The amount of disk space you will need is, in part, based on the number of
clients. As mentioned in the Introduction, the OS2PopS POP server has been in
production serving over 800 clients. The server and client mail store is on a
partitioned 1 gigabyte disk drive with approximently 650 megabytes of space
available.
As mail is received by OS2PopS, and then retrieved by your clients, the amount
of disk space available will vary constantly. You will want to be VERY
generous with disk space so you don't run short. We estimate that the 650
megabytes we have with 500 clients today should be able to support at least
another 500, for a total of 1000 clients, before we'll need to consider
additional disk space.
Of course there are no hard and fast rules nor anything preventing your clients
from receiving multi-megabyte files so the best advice is to keep an eye on the
amount of disk space remaining.
ΓòÉΓòÉΓòÉ 6.3. The installation screen ΓòÉΓòÉΓòÉ
This is the first screen that OS2PopS will display if you have never installed
OS2PopS before. Detailed information about the fields displayed my be found
here.
ΓòÉΓòÉΓòÉ 6.4. Installation screen details ΓòÉΓòÉΓòÉ
The first time OS2PopS is started it will not be able to find its INI file and
will assume that you are installing OS2PopS for the first time. The
installation screen contains some brief information about where you might want
to install OS2PopS followed by several choices you will need to make regarding
the installation.
The first thing you must decide is where you want OS2PopS to store its INI
file. The INI file is used to store the OS2PopS root directory, the positions
of the main control panel and status panel on the screen, and several other
pieces of information. Details of what the INI file contains may be found
here.
OS2PopS will, by default, look for its INI file in the following locations in
the order shown before giving up and deciding that an INI file is not
available:
1. The directory pointed to by the ETC variable in config.sys
2. The directory pointed to by the OS2PopS variable in config.sys
3. The OS/2 user INI file - OS2.INI (application name OS2PopS)
The ETC variable
When TCP/IP or MPTS is installed, the ETC directory will be created. The
location of this directory is defined by the ETC variable that is added to
config.sys. You may find out where your ETC directory is by issuing SET ETC
in an OS/2 window. OS2PopS will default to using the ETC directory for its
INI file since using it does not require a reboot of the machine after OS2PopS
is installed. The ETC directory is also one of the directories that should be
backed up on a regular basis.
The OS2PopS variable
You may choose to have OS2PopS store its INI file in its own directory instead
of the ETC directory. If you choose this option your config.sys will be
updated and you will need to reboot to pick up the change. Note however that
OS2PopS will start and run 1 time without a reboot.
If this option is choosen the single line that will be added to your
config.sys (at the very bottom) is:
SET OS2PopS=D:\OS2POPS\
Of course the drive and directory will depend on where you choose to install
OS2PopS.
The OS/2 INI file
If you don't mind an application such as OS2PopS updating the OS/2 user INI
file, OS2.INI, choose this option and OS2PopS will store the location of its
INI file there. It will be stored under the application name OS2PopS with a
single key named "INILoc". The INILoc key will contain the location of the
OS2PopS INI file.
OS2PopS INI location
If you decide to store the OS2PopS INI file in the OS2PopS directory the
OS2PopS INI location input field will be enabled. You may store the OS2PopS
INI file on any HPFS drive on your system. We strongly suggest that you
choose to store it in the same place as the rest of the OS2PopS POP server.
Enter the INI file location in the format:
drive:\directory\
OS2PopS root location
The OS2PopS root location is key to the operation of OS2PopS. All of your
client mail, the user file with your client information, log files, and
accounting files will all be stored in directories below the directory you
specify here. You will want to make sure that the drive you choose will have
enough space.
Enter the OS2PopS root location in the format:
drive:\directory\
By default this field will contain the drive and directory where you started
OS2PopS for the first time.
After you have made your choices clicking on the green bar at the bottom of
the installation screen will cause OS2PopS to build all of the necessary
directories and files and create its INI file. Once these things are done it
will start running and be ready to accept client connections.
If you decide not to install OS2PopS click on the red bar at the bottom of the
window. Cancelling the installion of OS2PopS will prevent any directories or
files from being created.
ΓòÉΓòÉΓòÉ 6.5. SENDMAIL ΓòÉΓòÉΓòÉ
We won't attempt to explain what the sendmail program does here because it
would take a large book all by itself. The installation of OS2PopS assumes
that you already have TCP/IP installed and configured and that sendmail is
functioning properly. You should have sendmail being started automatically by
TCPSTART which is usually shadowed out of the TCP/IP folder into the STARTUP
folder.
The OS2PopS POP server receives mail via sendmail by modifying the Mlocal line
in your existing sendmail.cf. What it does is add an endmailer that actually
receives the data from the sendmail program and puts it into the directory of
the client it is addressed to.
The Mlocal line in sendmail.cf allows additional arguments to be passed to the
endmailer. For OS2PopS we pass the endmailer the OS2PopS root directory, the
user name that the mail item is addressed to, and the address that the mail is
arriving from as arguments. The OS2PopS root directory is a hard coded value
that is inserted on the Mlocal line in sendmail.cf.
As mentioned above, you will want to make sure sendmail is being started by
TCPSTART. You also need to make sure that it is using sendmail.cf and not
sendmail.uml (the sendmail configuration for the UltiMail product). The
easiest way to find out which sendmail configuration is being used is to edit
the TCPSTART.CMD file you'll find in your \tcpip\bin directory. If you have
TCPSTART starting sendmail you should see a line like this:
start sendmail -bd -q30m -CD:\mptn\etc\sendmail.uml
What is wrong with the example above is that the sendmail configuration program
that will be used is sendmail.uml and not sendmail.cf. You may either change
sendmail.uml to sendmail.cf or remove the -C parameter completely. By default
sendmail will look for and read sendmail.cf in the etc directory.
You'll find more information about the OS2PopS endmailer PopSMail here.
ΓòÉΓòÉΓòÉ 6.6. sendmail.cf ΓòÉΓòÉΓòÉ
CAUTION:
Always make a backup copy of sendmail.cf before you attempt to modify it.
After modifying sendmail.cf compare its size to the backup copy you made. They
should be within a dozen or so bytes of each other (+/- 25%).
Warning: The sendmail.cf file contains embedded tab characters. Do NOT use an
editor that will expand tabs or you will render sendmail.cf useless.
Warning: Running the TCP/IP configuration program may overwrite your
sendmail.cf file. Always make a backup copy of sendmail.cf before opening the
TCP/IP configuration program.
Note: The "E" editor, not EPM, should edit sendmail.cf without modifying the
tab characters.
The sendmail.cf file can be very intimidating at first glance. The sendmail
program is very powerful and a lot of its flexability is controlled by
sendmail.cf. The only part of sendmail.cf we will discuss here is the Mlocal
line since every sendmail.cf file will have one.
As we have already mentioned, the PopSMail endmailer is specified on the Mlocal
line in sendmail.cf. The Mlocal line needs the full path to where it will find
PopSMail in order for things to work.
This is the working Mlocal line from the sendmail.cf file that we use:
Mlocal, P=f:\os2pops\popsmail.exe, F=lsDFP, S=10, R=20, A=f:\os2pops $u $f
In order for sendmail to find the PopSMail endmailer the full path to PopSMail
along with PopSMail.exe must be specified immediately following the P= as shown
above. The 3 pieces of information that PopSMail needs in order to function
properly are the OS2PopS root directory, the user name the mail is destined
for, and the address the mail was received from.
The letters following F= are flags that tell sendmail what kind of endmailer
PopSMail is along with other things. You will probably want to use the letters
as shown in the example. For the purposes of this document you may ignore the
S= and R= portions of the Mlocal line.
The data after the A= are the parameters that are passed to the endmailer
(PopSMail in our case). As you can see, the first parameter is the location of
the OS2PopS root directory. The 2nd parameter, the user name the mail is
destined for, is passed with $u which is a sendmail variable that will contain
the user name the mail is destined for.
The 3rd and final parameter is the address the mail was received from. This is
passed to PopSMail by using the $f sendmail variable. The 2 sendmail
variables, $u and $f, should be found in just about every sendmail.cf file. If
the $f variable is not set for some reason it will not cause PopSMail any
problems.
ΓòÉΓòÉΓòÉ 6.7. PopSMail ΓòÉΓòÉΓòÉ
PopSMail is the OS2PopS endmailer that receives the mail from sendmail and
delivers it to the correct client directory for retrieval by the client. Since
PopSMail does not "speak" SMTP it is very simple. PopSMail only requires 3
things in order for it to function correctly. The 3 things are:
The OS2PopS root directory
The user name the mail is destined for
The address the mail was received from
These parameters are passed to it by sendmail.
With the user name and OS2PopS root directory PopSMail can find the OS2PopS
user file, examine it, and make sure the user name is a known POP client. If
the user is a POP client the mail that PopSMail received is placed into the
proper directory. If the user is NOT a POP client the mail is deposited in
the mail directory for the default POP client known as nobody.
Each file that PopSMail creates will have a unique name. The file name is the
date, in yyyymmdd format, that the mail was received and processed by
PopSMail. The file extension is the time in hhmmssuu which almost guarantees
that every file received will have a unique file name. A file name created by
PopSMail might look like this:
19950521.07353903
ΓòÉΓòÉΓòÉ 6.8. Why is HPFS required? ΓòÉΓòÉΓòÉ
The OS2PopS POP server must be installed on an HPFS formatted drive for 2
primary reasons.
Performance
Easier file naming
Performance is the main reason HPFS is required. Due to the "sparse" nature
of files in HPFS the read/write head in the disk drive usually doesn't need to
travel as far to read or write a given amount of information. For a POP
server that may be receiving data while delivering data to multiple clients
this speed "boost" is essential. The FAT file system on the other hand
requires the read/write head to travel to a specific area of the disk every
time a file is written, read, or erased. This additional movement can cause a
noticeable difference on a POP server.
Keep in mind that OS2PopS will be receiving and delivering hundreds, if not
thousands, of mail items every day all day. Each of those operations involves
at least several disk accesses. Without HPFS the additional overhead of FAT
makes it impractical for a POP server.
Easier file naming simply means that OS2PopS can create file names for mail
items that are received with long names that uniquely identify each piece of
mail for each client. It also allows the logging and accounting files that
OS2PopS maintains to have file extensions that correspond to the date the
logging or accounting takes place.
On the "back end" these naming schemes allow data to be gathered easily and a
variety of reports to be built detailing every facet of your OS2PopS POP
server installation.
One additional benefit for received mail is that the naming scheme inserts
mail items into a clients directory so they will always be delivered to the
client in the order they were received.
ΓòÉΓòÉΓòÉ 7. Day-to-Day operation of OS2PopS ΓòÉΓòÉΓòÉ
We think you will find that OS2PopS pretty much takes care of itself. There is
nothing you have to do with it on a daily basis. If you run with it minmized
you may even forget that it is running!
Most of the administrative interaction with OS2PopS will be adding, modifying,
and deleting clients and OS2PopS provides a simple, easy to use, graphical
interface for those tasks. We have broken each of the functions available into
separate sections to make it easier to find what you are looking for.
The OS2PopS Main Control panel
Client Maintenance
The OS2PopS Main Control panel pulldown menus
The OS2PopS Status window
ΓòÉΓòÉΓòÉ 7.1. The OS2PopS Main Control panel ΓòÉΓòÉΓòÉ
This is the main control panel for OS2PopS. With this panel alone you may
easily monitor, on an ongoing basis, the status of your OS2PopS POP server.
After explaining what you'll find available on the main control panel we'll
provide the details on each of the options available on the pulldown menus in
the next section.
Server Is - Will contain the word Active when OS2PopS is listening for
client connections on port 110. When the server is stopped the border
will be red and Active will read Halted. When the server is halted no
clients will be able to connect and retrieve mail.
Clicking on the word Active or Halted will toggle the state of the
server.
Clients Connected - This is the actual number of clients that are
currently having a "conversation" with the OS2PopS POP server.
The "slider" under the Clients Connected heading will graphically show
you how many clients are connected to the OS2PopS POP server at any
instant. When there are 1-14 clients connected the display will be
green. When there are 15-19 clients connected the display will be
yellow. If there are 20 or more clients connected at the same time the
display will be red.
Mail Items Delivered - How many individual pieces of mail have been
delivered to all clients since the last time OS2PopS was started.
Overall totals are safely stored in log files.
Client Maintenance - Brings up the Client Maintenance window which allows
you to add, delete, or modify your clients information.
ΓòÉΓòÉΓòÉ 7.2. Client Maintenance ΓòÉΓòÉΓòÉ
When the Client Maint button is pushed on the OS2PopS main control panel the
panel shown below will be displayed.
From this panel you may add new clients, modify existing clients, and delete
clients. When a client is selected modify will allow you to change the password
for that client as well as the comment field associated with that client.
You will not be able to delete the nobody or postmaster entries but any other
client that is selected may be deleted by pressing the Delete button. You will
be asked to confirm that you want to delete the client before the directory,
and any mail that may have been waiting, for the client is deleted and the
client entry removed from the user file.
Whether you are adding a new client or modifying an existing client the client
details window will be displayed after the Modify or Add button is pressed.
The fields and buttons on the client details panel should be pretty self
explanatory. If the cancel button is pressed no changes are made to the client
entry (or a new client is not added). The modify (or add) button will cause an
update to be made as required.
Once you modify/add a client or cancel this panel you will be returned to the
client maintenance panel.
ΓòÉΓòÉΓòÉ 7.3. The OS2PopS Main Control panel pulldown menus ΓòÉΓòÉΓòÉ
Shown below are the pulldown menus available on the main control panel.
The Options pulldown menu
The Control pulldown menu
The Help pulldown menu
ΓòÉΓòÉΓòÉ 7.3.1. The Options pulldown menu ΓòÉΓòÉΓòÉ
Save Control Window Position - selecting this option will store the
current position of the control window. The next time OS2PopS is started
the control window will be restored to this position.
Settings - selecting this option will display the settings notebook which
allows you to define what options you'd like OS2PopS to use. You may
select a notebook page below for mores details.
Logging Options
Display Options
Pruning Options
Miscellaneous Options
Remote Admin Options
Run Reports - This option will start the PopSRptr program to allow you to
run reports detailing information about your OS2PopS POP server.
Exit - Kills any client threads that may be active and stops OS2PopS.
Unlike the Active/Halted button on the Main Control Panel Exit will
disconnect any clients that may be connected and exit the OS2PopS
program.
ΓòÉΓòÉΓòÉ 7.3.1.1. Logging Options Notebook Page ΓòÉΓòÉΓòÉ
The logging options notebook page allows you to select the amount of detailed
information OS2PopS should log. By default the maximum amount of logging is
enabled.
ΓòÉΓòÉΓòÉ 7.3.1.2. Display Options Notebook Page ΓòÉΓòÉΓòÉ
The display options allow you to control how much detail is shown in the status
window. By default only client connections will be shown in the status window.
ΓòÉΓòÉΓòÉ 7.3.1.3. Pruning Options Notebook Page ΓòÉΓòÉΓòÉ
The pruning options page allows you to select how long information that has
been logged should be retained.
Pruning has not been enabled yet.
ΓòÉΓòÉΓòÉ 7.3.1.4. Misellaneous Options Notebook Page ΓòÉΓòÉΓòÉ
Clear Status Window - allows you to specify how much time, in minutes,
between status window clears. Possible values are 5, 10, 15, 20, 30, 45,
60, 90, 120, 150, 180 minutes.
Enforce Minimum Password Length - allows enforcement of a minimum
password length when adding or modifying clients directly on the server.
Values between 1 and 50 are allowed. Enforcement of the minimum length
is NOT available with remote administration.
TCP/IP host name of this machine - for remote admin and support for the
APOP client command to work OS2PopS must be able to determine its own
TCP/IP host name. If, for some reason, it is unable to determine the
name using standard TCP/IP calls completing this field will allow remote
admin and APOP support to still function.
The fully qualified host name should be entered as shown in the example.
ΓòÉΓòÉΓòÉ 7.3.1.5. Remote Admin Notebook Page ΓòÉΓòÉΓòÉ
Enable remote administration - when this checkbox is selected remote
administration will be enabled. At least one remote administrator must
be defined for remote administration to work.
Add - selecting Add allows you to define a new remote administrator ID
Modify - selecting Modify allows you to modify the password or general
information associated with a remote administrator ID that is already
defined
Delete - selecting Delete will remove the selected remote administrator
ID
ΓòÉΓòÉΓòÉ 7.3.2. The Control pulldown menu ΓòÉΓòÉΓòÉ
Start Server - This option will be enabled when OS2PopS has been stopped.
Otherwise it will be disabled. When enabled Start Server will cause
OS2PopS to start listening on POP port 110. This means that clients will
be able to connect to OS2PopS
Stop Server - This option will be enabled when OS2PopS is running
(started). Otherwise it will be disabled. When enabled Stop Server will
cause OS2PopS to stop listening on POP port 110. This means that no
clients will be able to connect to OS2PopS
Reset Counters - Resets the "Mail Items Delivered" counter on the main
control panel to zero. This does not affect what data will be available
for reporting.
Show Client Count - OS2PopS will display the number of clients defined in
the status window.
ΓòÉΓòÉΓòÉ 7.3.3. The Help pulldown menu ΓòÉΓòÉΓòÉ
Help - Displays this INF file.
Product Information - Shows the IBM Corporation address where you may
contact us along with the copyright statement. This is what the Product
Information panel looks like:
ΓòÉΓòÉΓòÉ 7.4. The OS2PopS Status window ΓòÉΓòÉΓòÉ
The OS2PopS status window is a simple MLE (multi line entry field) that is
write protected. The OS2PopS POP server will display various messages in this
window as clients connect and disconnect. Unexpected conditions, such as a
client disconnecting in the middle of a conversation, will also be displayed.
By default the status window will be cleared every 30 minutes. When the status
window is cleared the IBM Corporation copyright will be displayed followed by
the version number of OS2PopS that is being used and then a count of how many
clients have been defined.
The status window clearing delay may be changed on the Miscellaneous Options
page of the Settings notebook. The background and foreground colors as well as
the font used in the status window may be changed by pressing the RMB anywhere
in the Status window.
When the RMB is pressed the options available as shown below.
Change Font - This option will show you the standard font selection
window where you may choose any font you'd like for the Status window.
Changes to the Status window are made if you select "OK" in the font
window.
Here is what the font selection window looks like:
Change Colors - This option will display a window that will let you
choose the background and foreground colors of the Status window. The
color change window allows you to save the color changes or to cancel
them. If you save the changes they will be used the next time OS2PopS is
started.
Here is what the color change window looks like:
Save Window Position - Once you have positioned and sized the status
window to where you want it on the desktop, select this option to save
its position. The saved position will be used the next time OS2PopS is
started.
Clear Status Window - Immediately clears the status window and displays
the IBM Corporation copyright as well as how many clients are defined.
Show Client Count - Adds a line to the status window showing how many
clients are defined to OS2PopS.
ΓòÉΓòÉΓòÉ 8. Problem determination ΓòÉΓòÉΓòÉ
We don't think you will run into any problems with OS2PopS itself but you may
be contacted when one of your clients has a problem. The most common problem
will probably be confusion about a password. It is important to remember that
passwords are case sensitive. Abc is not the same as ABC when it is used as a
password.
There really isn't much more to add here. If you run into problems that you
think other people might too, please drop us a line and we'll update this
section as needed.
ΓòÉΓòÉΓòÉ 9. Security ΓòÉΓòÉΓòÉ
The OS2PopS POP server maintains security for client connections as outlined in
RFC1725 which describes how a POP server must handle client connections. There
is no limit to the number of attempts a client may make with an invalid
password so there is a chance someone could "hack" into a mailbox. Which leads
to the next point.
You should encourage your clients to choose passwords that are both long and
contain upper and lower case letters. Another good choice is a combination of
letters and numbers. Although OS2PopS does not require a minimum length for
passwords, at least 6 letters and/or numbers should be considered a minimum.
The client passwords are stored as plain text in the OS2POPS.Users file in the
UserInfo directory under the OS2PopS root directory. You should take great
care to restrict both logical and physical access to the machine that OS2PopS
is running on.
Logical access includes, but is not limited to, ftp, telnet, net use, mount,
etc. Most access methods, including the ones listed, provide some sort of
mechanism for limiting access. The one exception is telnet, on OS/2, which
does not provide a way to limit access. If someone can telnet into the machine
running OS2PopS they may do anything to the system.
ΓòÉΓòÉΓòÉ 10. OS2PopS Reports ΓòÉΓòÉΓòÉ
The PopSRptR reporting program may be used to generate informational reports
that detail the activity of your OS2PopS POP server. The following reports are
currently available:
Data delivered analysis - summarizes how many files and bytes of data
have been delivered to your clients on a daily basis. The average size
of the data delivered is also included.
Active client analysis - summarizies activity for active clients (clients
that have received data from the OS2PopS POP server during the reporting
period selected).
Inactive client analysis - summarizes clients who have NOT received any
data at all from the OS2PopS POP server during the reporting period
selected. This report may be used to identify clients who are not
actively using your OS2PopS POP server.
Report output destination - You may have the report that is built displayed
with the E editor or saved in a file. If you select "Display report in
editor", the report will be generated and displayed using the E editor. The
reporting program will be halted until you exit the E editor.
If you select "Save report in a file", you will be prompted to select a
location for the file as well as the file name. By default OS2PopS reporting
will store the report in the \OS2POPS\Reports directory. The default file
name will be:
For Data delivered analysis - Sent.Data.Report.StartDate.EndDate
For Active client analysis - Active.Clients.Report.StartDate.EndDate
For Inactive client analysis - Inactive.Clients.Report.StartDate.EndDate
All dates will be in the format yyyymmdd (year month day).
We'd like to get your ideas for the types of reports you would find useful
along with how you would like to see the data presented. Some possibilities
include:
Client connection activity - how often are clients checking for mail
Delivered data analysis - are any of your clients getting large data
items on a regular basis - what is the peak time of data for data arrival
Anything else you can think of will be considered. Just drop us a note with
the details and, if possible, how you would like to see the information
presented.
ΓòÉΓòÉΓòÉ 11. Commands OS2PopS supports ΓòÉΓòÉΓòÉ
OS2PopS supports the following commands:
APOP
QUIT
USER
PASS
STAT
LIST
RETR
DELE
NOOP
RSET
TOP
UIDL
HELP
OS2PopS also supports the following commands which are NOT part of the RFCs
for a POP server. They were added to support remote administration of
OS2PopS.
ADDCLIENT - define new client
DELCLIENT - delete a client
MODCLIENT - modify a client
QUIT - end session
RADMIN - admin user ID
USERDATA - retrieve user data
Details on the remote administration commands may be found in the Remote
Administration Commands section that follows.
ΓòÉΓòÉΓòÉ 12. Remote Administration Commands ΓòÉΓòÉΓòÉ
You will not find any of the commands for remote administration listed in any
of the RFCs. These commands are sent to the OS2PopS server by the remote
administration client. They are detailed here for your information.
All commands sent to the OS2PopS server are terminated by a CRLF (carriage
return/line feed - '0D0A'x). If a command requires data, such as the ADDCLIENT
command, the data is sent in the same packet as the command itself with a
single blank between the command and the data the command requires.
As an example, to retrieve information about a client user ID of joeuser the
following command would be sent to the OS2PopS POP server:
USERDATA joeuser <CRLF>
Responses from the OS2PopS POP server
If a command sent to a OS2PopS POP server succeeds the OS2PopS POP server will
return +OK which is the normal POP3 positive response. If the command does not
succeed the OS2PopS POP server will return -ERR which is the normal POP3
negative response.
In the examples the hex01 is the value '01'x. This is the value that is used
to delimit data that some commands require.
ADDCLIENT - to define a new client to the OS2PopS POP server a single
line of data is sent to it. The single line contains exactly the
contents of an entry in the OS2PopS users file.
Specifically, it must contain:
hex01UserIDhex01PassW1hex01Commenthex01
Any agent that is adding clients to the OS2PopS POP server should use the
USERDATA command to verify that the client user ID that will be added
does not conflict with an existing user ID.
The user ID may not be longer than 50 characters and may NOT contain
blanks. The password may also be up to 50 characters in length and may
NOT contain blanks. The comment may contain up to 200 characters and
blanks are permitted.
For example, to add a client user ID of joeuser to the OS2PopS POP server
the following command would be sent to the OS2PopS POP server:
ADDCLIENT hex01joeuserhex01joespasswordhex01This is Joe Users commenthex01 <CRLF>
DELCLIENT - to delete an existing OS2PopS POP server client user ID the
user ID to be deleted is sent to the OS2PopS POP server. For example, to
delete the client user ID joeuser the following command would be sent to
the OS2PopS POP server:
DELCLIENT joeuser <CRLF>
MODCLIENT - used to modify an existing clients password or comments
field. The data that is sent to the server is exactly the same as the
ADDCLIENT command.
For example, to modify the joeuser user ID on the OS2PopS POP server the
following command would be sent to the OS2PopS POP server:
MODCLIENT hex01joeuserhex01joesnewpasswordhex01This is Joe Users new commenthex01 <CRLF>
QUIT - ends the session between the remote administration client and
the OS2PopS POP server. This is a "clean" break and should be used after
every command is sent to the OS2PopS POP server.
QUIT <CRLF>
RADMIN - initial command sent to the OS2PopS POP server by the remote
client to establish a connection with the OS2PopS POP server. The RADMIN
command works exactly like the APOP command for POP clients and requires
access to code that can build an MD5 digest string.
The initial greeting presented by the OS2PopS POP server when a remote
administration client connects includes a unique string that the remote
administration client must use to compute the MD5 string that is used
with the RADMIN command.
Rather than repeat all of the details about how the APOP command works,
I'll refer you to RFC1939 which contains all of the details. After the
remote administration client has computed the necessary MD5 digest value,
the RADMIN command is sent to the OS2PopS POP server to establish the
connection.
RADMIN adminuserid md5_digest_value_using_the_admins_password
USERDATA - is used to retrieve details about a specific client user ID
or a list of all client user IDs that are defined to the OS2PopS POP
server. When information about a specific client is required, the client
user ID that remote administration wants the details about is passed as
the first and only argument.
For example, to retrieve all of the details about client user ID joeuser
the following command would be sent to the OS2PopS POP server:
USERDATA joeuser <crlf>
To retrieve a list of all of the client user IDs defined to the OS2PopS
POP server the value *all* is sent to the OS2PopS POP server.
USERDATA *all* <crlf>
The difference between the 2 formats of the command is what is returned
to the remote administration client. For the first case, retrieving data
for a specific client, the OS2PopS POP server will return +OK <crlf>
followed by a single line of data that contains the client user ID
details.
The client information will be terminated by an End Of Data (EOD) string
which consists of <crlf>.<crlf> (that's a period between the CRLF pairs).
This happens to be the same EOD string that is used when OS2PopS is
delivering mail to clients as documented in RFC1939.
The string of data with client details matches exactly what is stored in
the user file on the OS2PopS POP server. It will consist of:
hex01joeuserhex01joespasswordhex01This is Joe Users commenthex01
It is easily broken up into individual parts by using:
parse var datain (hex01) userid (hex01) userpw (hex01) usercomment (hex01) .
The 2nd form of the command, to retrieve a list of all defined user IDs,
only returns a list of user IDs delimited by a <CRLF> between them (no
password or comment data is returned). The list of defined client user
IDs is terminated by the EOD string so remote administration knows when
the list of IDs is complete.
A sample CMD file that we have used to register clients to our OS2PopS POP
servers via a Web page is included in the OS2PopS ZIP file as
WebReg.CMDSample. It illustrates the use of all of the commands shown above
and may be modified and used if you so desire.
The sample is, necessarily, modified slightly from the version we actually use
and has NOT been extensively tested. Modify and use at your own risk.
ΓòÉΓòÉΓòÉ 13. The OS2PopS directory structure ΓòÉΓòÉΓòÉ
The directory where the OS2PopS main program is installed is known as the root
directory for OS2PopS. All other directories are below this directory
including the client mail store. At installation time OS2PopS will create the
following directories (we'll assume an installation on the "D" drive):
D:\OS2POPS
\Accounting
\LogFiles
\MailRoot
\nobody
\postmaster
\....
\OutBound
\Reports
\UserInfo
\Work
Accounting - the files in this directory maintain a running log of client
connects and disconnets
LogFiles - all OS2PopS activity is logged in various files in this
directory
MailRoot - each client defined to OS2PopS has a directory below this one
- nobody and postmaster are the default clients that are created during
the installation of OS2PopS
OutBound - files sent from clients using the XMIT command are stored here
until they are sent
Reports - if any reports are generated this is the default directory
OS2PopS will write them to
UserInfo - this is where the file that contains client information
resides
Work - a temporary area for OS2PopS
The The files that OS2PopS creates section provides details on the files that
will be found in each directory.
ΓòÉΓòÉΓòÉ 14. The files that OS2PopS creates ΓòÉΓòÉΓòÉ
Detailed here are the files, and their formats, that OS2PopS creates in the
various directories. All of the log files have a file extension that is
composed of the year, month, and day in the format yyyymmdd. Each line within
the log files starts with the date in yyyymmdd format followed by the time in
hh:mm:ss format. Beyond that, the contents of the line are different for each
type of log file.
Accounting - the only file name created in this directory is Accounting.
Following the date and time is a single word that will be ON or OFF
followed by the client ID that logged ON or disconnected (OFF). Here's
an example of what a line might look like:
19960625 02:33:13 OFF nobody
LogFiles - several types of logging may be done by OS2PopS. All of the
logging is done into files in this directory. Each type of logging
activity uses a different file name.
- Data - this log file details data that has been delivered to
clients. In addition to the date and time, each line contains the
number of bytes delivered to the client, how long it took OS2PopS to
deliver that data, and the client user ID the data was delivered to.
Here's an example of what a line might look like:
19960506 01:56:53 1216 0.03 nobody
In this example 1216 bytes of data were delivered to client ID
nobody in 0.03 seconds.
- Errors - this log file details unexpected errors that will occurr
while clients are connected to OS2PopS. Generally speaking, what is
logged here may not necessarily be an error. It is usually simply
an indication that a client disconnected abnormally. Following the
date and time in the file is the error message generated by OS2PopS.
This message will usually contain the socket number the client was
using as well as the error from TCP/IP itself if any. Here's what
an entry might look like:
19960505 16:09:33 Client using socket 652 disconnected during conversation
- Info - this log file details general information type messages. The
most common is the initial client connection message which includes
the address the client is connecting from as well as the socket they
used when they connected. Here's what an entry might look like:
19960504 00:01:23 Connect from 1.127.0.0 using socket 2039
- Received - this log file details mail items that are received via
sendmail and processed by the PopSMail endmailer. Following the
date and time each line contains the client ID on the OS2PopS POP
server that the file was destined for, the number of bytes received,
and the address that the file was from. Here's what an entry might
look like:
19960511 00:12:34 nobody 1017 nobody@nowhere.com
In this example client nobody received 1017 bytes of data from
nobody@nowhere.com.
- Trace - this log file details the "conversation" between OS2PopS and
its clients. Following the date and time is either Sent or Received
to indicate if data was sent to a client or received from a client.
After that the actual data that was sent or received is logged.
Here's what a couple of entries might look like:
19960503 06:58:43 Received USER nobody
19960503 06:58:43 Received PASS somepw
19960503 06:58:43 Received STAT
19960503 06:58:43 Sent 6 10328215
19960503 06:58:43 Received UIDL
19960503 06:58:44 Received RETR 1
19960503 06:58:44 Received DELE 1
As you might anticipate, the trace log files can grow very quickly.
It only needs to be enabled if a particular client is having a
problem and you need to see what the client and server are sending
each other.
MailRoot - no files are stored in the MailRoot directory itself. Instead
you will see a directory beneath MailRoot for every client you have
defined.
- Client directories - as mail is received the PopSMail endmailer
deposits it into the appropriate client directory. One file for
each mail item received is created. Each file will have a unique
name and extension which is based on the date and time received. A
file name might look like this:
19950521.07353903
The file name is the date in yyyymmdd format. The file extension is
the time in hhmmssuu which almost guarantees that every file
received will have a unique file name.
OutBound - this directory is used as a temporary storage area for files
that clients send via the OS2PopS POP server using the client XMIT
command.
Reports - this is the default directory where OS2PopS will write reports
that are generated. When reports are generated you will be given a
chance to change the location and name of the report file if you don't
want to have it created in this directory.
UserInfo - this is where the file with all of the information about your
defined clients is stored. The primary user file name is OS2POPS.Users.
As you add, modify, or delete clients you will notice that 10 generations
of the user file are maintained for backup should something happen and
you need to undo an update. There is also one additional backup copy of
the main file that is created immediately before the main file is updated
for any reason.
- OS2POPS.Users - this is it. All of the information about your
clients is stored in this file. For the most part this file is
plain text so you may view it if necessary but be careful. A value
of "01"x (hex 01) is used to separate the components of each line
and they are absolutely critical for the proper operation of
OS2PopS.
Don't update this file manually because OS2PopS won't see any
changes you make. And if you should update, add, or delete a client
any manual changes you may have made will be lost. Each line of the
file consists of 3 things each of which is surrounded by hex 01.
The 3 elements are:
client user ID
client password
comments (freeform)
The client user ID will always be lower case but the client password
is case sensitive. The comments may contain anything at all. We
store our clients real name in the comments section.
Work - this directory is used by OS2PopS from time to time to store
temporary files.
ΓòÉΓòÉΓòÉ 15. The OS2PopS INI file ΓòÉΓòÉΓòÉ
The OS2PopS INI file is used to hold several pieces of information that are
used by various components of OS2PopS. There is only 1 application name used
in the OS2PopS INI file and that name is OS2PopS. All of the keys that have
more than 1 value have the values separated by a semi-colon ";". If a key is
identified as having "binary flags" the value(s) will always be a zero or a
one. The following keys are defined:
CDetailsPos - 2 values for the position of the Client Details window -
left side, top
CMaintPos - 2 values for the position of the Client Maintenance window -
left side, top
DisplayOptions - 3 binary flags - info messgaes, warning messages, error
messages
LogOptions - 3 binary flags - info logging, trace logging, receive
logging
MainPos - 2 values for the position of the main control panel on the
desktop - left side, top
MiscOptions - 1 binary flag and 1 numeric value - remote administration
enabled and number of minutes to delay status window clearing
POPSRoot - 1 value - complete path to OS2PopS root directory (includes
trailing \)
PruneOptions - 2 values for log file pruning - info and trace
Registration - 3 values - registered name, client limit, key
StatLooks - 3 values for appearance of status window - background color,
foreground color, font
StatPos - 4 values for position of status window on the desktop - height,
left side, top, width
ΓòÉΓòÉΓòÉ 16. Contacting IBM ΓòÉΓòÉΓòÉ
This program was written by Dave Martin of IBM Corporation in Research Triangle
Park North Carolina USA. You may reach Dave by sending E-Mail to:
djm@raleigh.ibm.com
The latest version of OS2PopS and all of the latest news may be found on the
Web at http://www.raleigh.ibm.com/misc/os2pops
A mailing list run by MajorDomo is available for OS2PopS questions,
suggestions, and bug reports. A Web interface to MajorDomo is available on the
Web at http://www.raleigh.ibm.com/maillists
You may also contact the MajorDomo server by E-Mail. To subscribe send mail to
majordomo@raleigh.ibm.com and include a single line in the body of the note
that contains:
subscribe os2pops
If you wish to unsubscribe from the list send a note to the same address and
include a single line in the body of the note that contains:
unsubscribe os2pops