home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
rtsi.com
/
2014.01.www.rtsi.com.tar
/
www.rtsi.com
/
OS9
/
OSK
/
TELECOM
/
OSKBox.lzh
/
MAILBOX
/
CC
/
DOCS
/
mailbox.doc
< prev
next >
Wrap
Text File
|
1991-02-02
|
6KB
|
132 lines
NAME:
mailbox - packet radio mailbox system.
AUTHOR:
Eric Williams WD6CMU, 71336,1424
SYSTEM CONFIGURATION:
OS9/68K, MW C v2.0
SYNTAX:
mailbox [<callsign> <port> <callsign>...]
DESCRIPTION:
mailbox provides a reentrant messaging system for use in conjunction
with the WA8DED host translator (host). It provides packet radio users
with a public message system and file services, as well as maintaining
accounting information for the mailbox administrator. Although the normal
mode of operation for mailbox is to be forked from the host translator, it
can be run from any terminal in the system in order to allow debugging and
local access to the mail system.
The first argument to mailbox, if provided, gives the callsign of the
station accessing the mail system. If not provided, it defaults to
"SYSOP" and the user is given sysop privileges. The second argument is
intended to be the device name of the TNC through which the mailbox user
is connected, minus the "/". Any additional arguments are assumed to be
the callsign of the digipeaters through which the user has connected.
For example:
mailbox W6MEO T7 KB6GOZ-1
When mailbox runs, its first action is to change its working data
directory to "/dd/mailbox". Within this directory it expects to find
several files. All files and directories described below reside within
this directory.
The first file mailbox expects to find is one called "users" which
contains a database of all stations which have checked into the mail
system. Various vital statistics on each user are kept by mailbox and a
user's entry will be updated each time he connects. (Note: no entry is
made for someone running mailbox without a callsign argument.)
A text file called "motd" will then be searched for. If it exists,
and if its last access date is later than the last checkin date of the
user, it is printed out.
A file called "mail_dir" must be in the mailbox directory, with a
copy of the file in a data module of the same name. This file is loaded
by the program "mbinit".
A directory called "MAIL" contains the message database. Each file
in this directory represents a message in the mail system. The file name
consists of a 6-digit number (with leading zeroes) which corresponds to
the message number.
Zero or more distribution list files, whose name end with ".dis" are
then searched for in the mailbox directory. The names of these files are
used to specify bulletin distribution designators and the mailbox will
force a BID to be generated for messages addressed @ any of these
designators. These files consist of one or more BBS callsigns, one per
line, to which copies of bulletins carrying a designator matching the
file's name should be sent.
The directory "HELP" contains several text files which are accessed
and printed when the user asks for help.
The directory "FILES" contains the user-accesible files which can be
downloaded and uploaded, as described in the user commands. The file
"file_ownders" contains a list of files and the callsigns of the stations
that uploaded them, and so have permission to rename or delete them.
The text file "info" will be printed out in response to the I
command.
The file "logfile" is a running log of who did what. Currently, only
actions which actually modify the message or file data are logged. The
first seven characters of each line are the callsign of the station making
the action. The next 10 characters are the date and time of the action in
the format YYMMDDHHMM. The next character is the action itself. Upper-
case characters refer to commands given to the mailbox and are followed by
the arguments to the command, if any. Lower-case characters refer to
actions other than those caused by user commands. The following codes
(other than mailbox commands) are currently defined:
c: connect (followed by connect path, including port)
d: disconnect
f: message forwarded (followed by msg #, see doc for forward)
r: message was refused forward (followed by msg # and reason for
refusal, if any)
Documentation for the various commands that mailbox responds to can
be found in the help files as used by the program. Listed here are the
non-user oriented commands.
If a user is marked in the userfile as having sysop privileges, then
he is allowed to read or kill any message in the system. He is also
allowed to rename or erase any file in the system. Users marked as sysop
or bbs in the userfile can also send messages with an originating callsign
other than their own by adding "< <callsign>" to the send command.
The List command can be augmented by the X and/or E flag. X calls for
a listing of deleted messages as well as active messages. Deleted messages
will show a X in the status column. The E modifier will give an extended
message listing, showing date last modified, distribution status, full
hierarchical route, and message BID. The distribution status is a
hexidecimal number, each bit of which corresponds to a callsign in the
distribution list file (described above). The X and E flags can be added
to any legal list command after the L, for example: "LXL 5", or "LE@
AMSAT". Note that the X and E flags must appear in that order if they are
used together, for example: "LXE> WD6CMU". (Not: "LEX> WD6CMU"!)
A user marked sysop can use the Modify command to change any message,
and to change fields in the mail database not available to users.
The @ command provides a "back door" into the OSK operating system.
This is available only to users marked as sysop, and required a numerical
key for an argument. This key is created by passing the month, day, year,
hour, minute, and second through the standard OSK 24-bit CRC algorithm.
The CRC can be initialized with a sysop-selected "password" to make the
code unique. Programs to calculate the CRC are available in C, Basic,
and for the HP-16C programmable calculator.
BUGS:
The Bye command does not always result in a disconnect, for unknown
reasons which probably involve the host command.