Welcome to UUPC2POP.  This program "pops" a user's incoming UUPC
mail file to a POP3 mail directory.  Simply SU to the user and
run the program.  You can also look at the example batch files
for guidance in a multiuser environment.  The enclosed SU.CMD was
written by Kew Software, authors of UUPC/Extended, and additions
were made by yours truly for use with Yarn, souper, TIN, TRN, etc.
If you do not wish to use the SU.CMD, then you must set the
USER variable manually.

This was written and compiled using emx, and it does require the
emx runtime package, which is available at your favorite ftp site.

As you are totally at the whims of the POP3 agent, your POP3
daemon might require user\inbox or mailbase\user.  If it is user\inbox,
then simply define the home directory in the personal.rc file.
If it is the latter, you will need to define a MAILBASE environment
variable in CONFIG.SYS or elsewhere before running the program.

For example, if the POP3 daemon does basedirectory\user\inbox, then
put the basedirectory\user in the user's personal.rc.  If the user
is sysop, and all of the user directories are located in F:\USR,
then define the Home directory as f:/usr/sysop in SYSOP.RC.  The
program will then put all popped mail into F:\USR\SYSOP\INBOX.
Personally, I like this approach better, since it does not clutter
up the root of a user's home directory, which may be used for other
things on a BBS.  Most POP3 servers I've seen will not tolerate
other files in their directory or will attempt to turn them into mail!

However, if the POP3 daemon demands mailbase\user without the option
of subdirectories, you can define the MAILBASE variable.  If the
user is sysop, and all incoming mail is placed into I:\MAILSTORE,
then put SET MAILBASE=I:\MAILSTORE into CONFIG.SYS.  Sysop's mail
will now go into I:\MAILBASE\SYSOP.  Note, in the example above, that
you can also use the user's home directory, if it will not be used 
for anything else.  You would then SET MAILBASE=F:\USR.

This program is freeware for all.  The warranty is as large as
the cost.  If it does not work with your particular daemon, then
it may well be the POP3 daemon.  Most I've seen have problems, one
shareware one died without an error message before I even got a
chance to send mail to it, and some bomb for various other reasons.
The state of POP3 daemons for OS/2 seems pretty sad, indeed, right
at the moment.

