home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Crawly Crypt Collection 1
/
crawlyvol1.bin
/
bbs
/
amail20
/
amail.doc
< prev
next >
Wrap
Text File
|
1993-11-08
|
51KB
|
1,478 lines
_______ ___________ _______ ________ ___
/*******\ /***********\ /*******\ /*******/ /**/
/**/ /**/ /**/ /**/ /**/ /**/ /**/ /**/ /**/
/********/ /**/ /**/ /**/ /********/ /**/ /**/
/**/ /**/ /**/ /**/ /**/ /**/ /**/ /**/ /**/
/**/ /**/ /**/ /**/ /**/ /**/ /**/ __/**/___ /**/_____
/**/ /**/ /**/ /**/ /**/ /**/ /**/ /********/ /********/ v2.0
Written By Andy Styles, July 1992.
| v2.0 released September 1993.
__
/\ \
/ \ \
/ /\ \ \
/ / /\ \ \ (c) 1992,1993 Andy Styles,
/ / /__\_\ \ Hobbit Software.
/ / /________\
\/___________/
(c) Andy Styles, 1992. All rights reserved. This program may be copied free
of charge, providing all its component parts are kept together. This program
may NOT be modified without the prior consent of the author. Please call The
Hobbit's Burrow, (+44)-[0]245-358667 for bug reports, updates, and support.
| Alternatively, netmail me on 90:102/103.0 (NeST), 2:257/403.0 (Fido).
| Please do NOT telelphone me voice, as I will only support bugs and
| suggestions via snail or net mail.
Contents Page
1.0 Introduction 3
1.1 AMail v2.0 3
1.2 Summary of changes 3
2.0 Getting Started 5
2.1 What you need.. 5
2.2 Installation 5
2.2.1 First Time Installation 5
2.2.2 Migrating to AMail v2.0 6
2.3 AMail Files 6
3.0 AMail Operation 8
3.1 How AMail works 8
3.2 The Sequence of Events 8
3.3 Flowchart of Control 8
3.4 AMail in use 8
3.4.1 AMail Main Menu 8
3.4.1.1 Option A: Select Conferences 9
3.4.1.2 Option B: Pack Messages 9
3.4.1.3 Option C: Change Options 10
3.4.1.4 Option D: Download packed mail 10
3.4.1.5 Option E: Upload reply packet 10
3.4.1.6 Option F: Download Prepacked Mail 10
3.4.1.7 Option G: Delete Held Packet 10
3.4.1.8 Option X: Sysop Menu 10
3.4.2 Change Options Menu 10
3.4.2.1 Option A: PERSONAL.IDX Generation 11
3.4.2.2 Option B: Archive type 11
3.4.2.3 Option C: Archive Compression 11
3.4.2.4 Option D: Line Length 11
3.4.2.5 Option E: Own message inclusion 11
3.4.2.6 Option F: Maximum Messages 11
3.4.2.7 Option G: New Files 11
3.4.2.8 Option I: Bulletins 11
3.4.2.9 Option J: Batch Pack 11
3.4.2.10 Option K: Set Default Protocol 11
3.4.2.11 Option L: Set Oldest Message Date 12
3.4.2.12 Option M: Ignore LastRead Pointers 12
3.4.3 Sysop Menu 12
3.4.3.1 User List 12
3.4.3.2 Mail Waiting Users 12
3.4.3.3 Delete User 12
3.4.3.4 Maintenance 12
3.5 AMail parameters 12
3.5.1 Import 12
3.5.2 Batch Pack 13
3.5.3 Sysop Menu 13
3.5.4 Maintenance Mode 13
3.6 AMail Locally 13
4.0 The Configuration File 14
5.0 Key requests 18
5.1 Demo Keys 18
5.2 Payment 18
5.3 Receiving your FULL key 18
5.4 FULL key cracks 18
5.5 Key Updates 19
6.0 Problems 20
6.1 Known Problems 20
7.0 The Future 21
8.0 Credits 22
9.0 AMail Key Request Form 23
Page 2
1.0 Introduction
AMail is a program designed to work with QuickBBS ST, to allow users to pack
mail, and download it online. It packs the mail in a format compatible with
the .QWK mailers, such as SLMR on the PC, and MaxiMiser on the ST. The idea
is that users no longer have to sit logged on, spending money, they can just
spend time waiting for the messages to be packed, and then download them,
enabling them to reply and spend as long as they wish off line. This should
encourage users to stop file troughing a board, and contribute a little more!
AMail was written because all those ///Turbo boards are sitting there looking
very smug, and the PC boards are a little along, grinning like cheshire cats.
Well, AMail will wipe those grins off their faces!
AMail allows users to:
o Select which message areas they wish to be part of
o Select the archive type for downloading
o Pack messages
o Download messages, and Upload replies
using a selected transfer protocol
| o Receive a list of new files from the BBS
1.1 AMail v2.0
| v2.0 is the latest release of AMail. Changes to the original document can
be identified by the | (vertical bar) character in the left hand column.
There are many changes to the code, but most of them are bug fixes or
cosmetic changes.
1.2 Summary of changes
| o Read the Sysop record when DORINFO1.DEF not available
|
| Reading the sysop user record should prevent other users in the
| USERS.BBS file being overwritten when using maintenance, and
| during Batch pack mode.
|
| o Messages to AMail
|
| To send a message to AMail, the description *must* be CONFIG, and
| then AMail will process the message. ADD adds a conference, DROP
| drops a conference, and RESET will reset the lastread pointers to:
|
| -nnn - nnn from the end of the message base
| nnn - to message nnnn
|
| o New configuration commands, MaxSecPack and MaxSpeedPack
|
| MaxSecPack and MaxSpeedPack work in the same way:
|
| MaxSecPack sssss pppppp
|
| Where sssss is the security level and ppppp is the maximum number
| of msgs allowed in a packet. If a user has a level you haven't
| specifed, the number of messages is unlimited. (MaxSpeedPack works
| on baud rate)
|
Page 3
| o Chat Mode
|
| Chat mode is activated by F1, and terminated with ESCape.
|
| o Exit confirmation
|
| Confirmation on exit means that dumb users who pack mail and then
| quit without downloading are warned! This will only be displayed
| when the user has packed some mail and not downloaded it.
|
| o New configuration command, BadPkt
|
| BadPkt is a new config word, all bad uploaded .REP packets go
| there when they cannot be extracted or they're for a different
| BBS: (ends in '\')
|
| BadPkt <path>
|
| o QuickBBS 1.10+ support
|
| With QuickBBS 1.10, there's a new .DOR command that works ONLY
| with AMail:
|
| PUTUSER - stores the LASTREAD pointers for AMail to update
| GETUSER - retreives the updates LASTREAD pointers.
|
| This means that an exit-with-errorlevel is no longer required!!
|
| New AMAIL.DOR:
|
| send Please wait..
| putuser
| cd e:\amail
| amail
| getuser
| send Okay!
|
| o Ignore lastread pointers option
|
| The Ignore LastRead option allows the user to effectively pack the
| whole of your message base into one large QWK packet, if they
| really want to. Selecting this option will update the lastread
| pointers, and will also take note of the Oldest Message Date
| option, so you can pack all messages that occured after a certain
| date, and have your last read pointers updated properly
| afterwards!
|
| o Message writing corrected
|
| The messages written to the *.MSG files on import were incorrect.
|
| o QuickBBS environmental variable
|
| AMail now attemps to read the environment for the variable QBBS,
| and will use that instead of the the "QuickBBS" configuration
| keyword. The configuration keyword is now parsed, but ignored on
| reading the .CFG file. In later releases (after 2.0), this will
| be removed, and "QuickBBS" will be invalid.
|
| o New configuration keyword, Replies
|
| The Replies keyword allows you to specify a separate directory for
| the uploaded packets.
|
| o Enhanced error reporting
|
Page 4
| Errors from external programs have been confusing in the past.
| This has now been re-vamped, and where possible, a textual message
| is entered in the log.
2.0 Getting Started
2.1 What you need..
To run AMail, you need the following:
o QuickBBS ST, 1.08 or greater
o At least one type of archiver (LZH, ARC, or ZIP)
o £10 (ten UK pounds) (for the registered version)
o To be running a batch file method of accessing QuickBBS
| or:
|
| o QuickBBS ST, 1.10 or greater
| o At least one type of archiver (LZH, ARC, or ZIP)
| o £10 (ten UK pounds) (for the registered version)
| o More than 1 megabyte of RAM
2.2 Installation
2.2.1 First Time Installation
Installation of AMail is very easy. Providing you've unpacked everything in
the archive, you should have the following:
o AMAIL.PRG - The program itself
o AMAIL.DOC - You're reading it..
o AMAIL.DOR - Example .DOR file for QuickBBS ST
| o AMAIL1.DOR - .DOR file method of accessing AMail
o AMAIL.CFG - Example configuration file
o AMAIL.TOM - Example batch file (for TOMSHELL)
o AMAIL.BAT - Example batch file (for PCOMMAND)
o WELCOME.DOR - Example WELCOME.DOR file
o SETUP.HLP - Example set up menu Help file
o MAIN.HLP - Example main menu Help file
o AMREQ.PRG - AMail Key Request Program
o AMUSER.TXT - AMail Users Guide
If any of these are missing, then you can request the full archive from me
at The Hobbit's Burrow, (+44)-[0]245-358667, requestable as the magic name
AMail, or alternatively logon and download it, using option X from the Main
menu.
Once you have all of these items, then follow these steps:
a) Create a directory for AMail
b) Copy AMAIL.PRG, and AMAIL.CFG into it.
c) Add a menu option that executes the .DOR file (example supplied)
d) Alter your start up batch file to execute AMAIL when QuickBBS
exits with errorlevel.
e) Run AMREQ.PRG (see later) to request a key.
AMail is now installed. (simple, wasn't it..)
NB: If you modify your autoexec file (AUTOEXEC.BAT or whatever) from within
Binkley, then please remember to either reboot your computer, or exit
Binkley, and restart it.
The WELCOME.DOR file has a couple of oddities in. The lines that say
something like
IF [odd box]34 ~ ON THEN GOTO
Page 5
are checking to see if a flag is on. See WHATSNEW.106 of QuickBBS for the
full documentation. Basically, the line says
IF flag B4 is ON THEN GOTO
The [odd box] is in fact, a CTRL-F character or ASCII 06. The number
following this is the flag letter (A=2, B=3, C=4, and D=5), followed by the
flag number.
2.2.2 Migrating to AMail v2.0
| If you already have AMail v1.8 installed, then you won't need to adjust
| too much to install AMail v2.0. If you have QuickBBS ST, v1.10 or
| greater, and you have more than 1 megabyte of RAM, you can alter the
| way AMail is executed. Instead of using the exit-with-errorlevel option,
| AMail can be run from a .DOR file, by using two new QuickBBS ST commands
| that are available in release 1.10. These are GETUSER and PUTUSER, and
| they are only available with AMail.
|
| PUTUSER will store the user's record and the lastread pointers, so that
| AMail can retrieve the most up to date information, and GETUSER will
| re-read that stored information, back into QuickBBS.
|
| See the AMAIL1.DOR file supplied for exact details.
2.3 AMail Files
o AMAIL.DAT
AMail has its own control file, called AMAIL.DAT, which it looks after.
This contains the users, their conferences, and their options. When you
run AMail for the very first time, it will create this file, and will
continue to look after it from then on.
o AMAIL.CFG
This is the straight ASCII configuration file, containing details about
your set up. See later for more details.
o AMAIL.KEY
This is your key file. At first, you will be supplied with a demo key,
which will allow you to operate AMail for one month. Once this has
expired, you are allowed to request two more keys before you either
register or cease using AMail. If you don't wish to call The Hobbit's
Burrow using the key request program, you may send me a disk, with
return postage, to the following address:
The Hobbit's Burrow,
27 Laburnum Drive,
Moulsham Lodge,
Chelmsford,
Essex,
CM2 9NR.
If you send me a disk, remember to include your key request (from the
end of this document) on the disk, or printed out.
See later for FULL key requests.
o AMAIL.INF
AMAIL.INF is written out before the new files creation program is called.
It contains the users record number on line 1 and their security on line 2.
Page 6
Page 7
3.0 AMail Operation
3.1 How AMail works
AMail uses its control file and the DORINFO1.DEF file written out by QuickBBS
ST to determine which messages should be packed. When the user selects Pack
messages, AMail will scan the message bases, picking out the messages that
the user hasn't read. Once all the messages have been selected, AMail will
then call the appropriate archiving tool to compress the messages. When the
replies have been uploaded, AMail will check the archive type, and then call
the right archiver to dearchive all the replies, and then add them to the
message base.
AMail will use QCONFIG.BBS to pick up the BBS name, the messages directory,
and other details required by a QWK mailer, and to validate your key.
3.2 The Sequence of Events
When you have set QuickBBS to exit to AMail with an error level, the batch
file should regain control. The batch file should then pass control to AMail.
When AMail is exited, the batch file should then pass control back to
QuickBBS, with the -r option. When QuickBBS is exited again, the batch file
should pass control back to the check above, which checks for an exit to
AMail (in case they exit twice to AMail). A flow chart is included on the
| following page as an example of the flow of control. This only relates
| to the batch file method of accessing AMail. Using the .DOR file works
| in exactly the same way as any other .DOR file.
3.3 Flowchart of Control
+----------------------<---------+
v |
+----------+ | +-------+ |
| QuickBBS | +--+->------| AMail | |
+----------+ exit with | +-------+ |
| errorlevel | | |
+------>------------+ | ^
| v |
v no errorlevel exit | |
| +----------+ |
+--------<-------+ | QuickBBS | using -R |
N / +----------+ | +----------+ option |
o p | |After QBBS| ^ | |
r r | |processing| | | exit with |
m o | +----------+ +-------------<----+-------------->----+
a c | | errorlevel
l e | |
s | +----------+
s | | Binkley | (or whatever)
\ +----------+
3.4 AMail in use
3.4.1 AMail Main Menu
When AMail first runs, it will first issue a little copyright message, and
then validate the key. Once the key has been validated, AMail checks to see
Page 8
if any mail is waiting to be picked up. If it is, you have the option of
downloading the mail straight away, or just skipping the download, to the
main menu. The Main Menu has seven options listed, A-E, H, and Q. Let's deal
with the last two first, as they're the easiest. 'H' merely displays the Help
file specified in the "MainHelp" configuration keyword (see later). 'Q'
will exit from AMail with return code zero.
There may additionally be extra options:
'F', which will allow you to download packed mail, if you skipped it at the
intro.
| 'G', which will allow you to delete the pre-packed mail, if you decide
| you don't wish to download it ever.
'X' if you are the sysop.
The remaining options will be dealt with in sequence on the following pages.
3.4.1.1 Option A: Select Conferences
The "Select Conferences" option from the main menu allows the user to select
which of the message areas that they have access to. AMail checks the
security and the area flags before allowing the user access to the area. If
the user has the required read security and flags, but not the write, then
AMail will use the '#' (hash) symbol to indicate that this is a read only
area. It displays a list of the areas, four to a line, each message area
truncated to 12 characters. If the user has any areas already selected (such
as the default area), then an asterisk will be displayed between the area
number, and the area name. The default area is indicated by a '+' sign,
instead of the '*'.
Eg:
1*General 2 Atari ST 3*IBM PC
and so on. This indicates to the user that they have two active areas.
The user is also presented with a line to enter any conference numbers they
wish to toggle. If they enter a blank line, the next page (if there are any)
is displayed. If there are no more pages, then the first page is displayed
again. If they specify conference '0', they are returned to the main menu.
Multiple areas may be specified by placing a space between the area numbers.
When they press enter, the modified list will be displayed. AMail will also
now let the user select the NetMail area. A range of conferences may be
entered, by separating the begin and end conference with a single '-'.
3.4.1.2 Option B: Pack Messages
The Pack Messages option from the main menu will start the packing sequence.
Each selected area will be processed in turn, having the area name displayed
and the number of messages, and new messages in the area. Each time an area
is completed, the actual number of messages packed is displayed next to the
area. Pack Messages can be aborted by pressing the Escape key twice in
succession.
Eg:
1 General ( 50 msgs, 50 new) (25 packed)
Page 9
2 Atari ST ( 45 msgs, 0 new)
Messages will only be packed for the user if they are either:
a) marked for that user,
b) not private, or
c) later than the oldest message date specified.
Once packing is finshed, AMail will then call the archivers to compress the
mail packet. When everything is completed, a "Press a key" prompt will be
displayed, and once the user responds, they will be returned to the main
menu.
3.4.1.3 Option C: Change Options
Option C allows the user to change his options. See later for more details.
3.4.1.4 Option D: Download packed mail
Option D allows the user to download his packed mail, using one of the file
transfer protocols that have been specified in AMAIL.CFG (see later). Once
the download is completed, AMail will check to see if a reply packet has
been uploaded, if so, the import process will begin.
3.4.1.5 Option E: Upload reply packet
Option E allows the user to upload their replies, using one of the protocols
that has been specified in AMAIL.CFG (see later). Once the reply packet is
received, AMail will unpack the archive, and then import the messages in to
the appropriate areas. Note that AMail will unpack using whatever archiver
has been used at the creating end, so that users can upload mail packets in
a different archive format to that of the downloaded one.
3.4.1.6 Option F: Download Prepacked Mail
Option F allows the user to download their prepacked mail if they aborted
the prepack download chance at the start of AMail.
3.4.1.7 Option G: Delete Held Packet
| Option G will allow the user to delete any held packet that they may
| have waiting. This allows users to clear their held mail, if they decide
| that it's getting too large, for example.
3.4.1.8 Option X: Sysop Menu
Allows access to the sysop menu. See later for more details.
3.4.2 Change Options Menu
The change options menu allows the user to modify their own settings, such
as the line length, or the archiving method used. When the user selects the
Change Options, a further menu is displayed:
A PERSONAL.IDX Generation (ON )
B Archive type (LZH)
C Archive compression (ON )
D Line length ( 72)
E Own message inclusion (OFF)
F Maximium Messages (OFF)
G New Files (ON )
I Bulletins (ON )
J Batch Pack (OFF)
Page 10
K Set Default Protocol (Zmodem)
L Set Oldest Message Date (01/01/93)
| M Ignore Lastread Pointers (OFF)
Each of these options will now be dealt with in turn.
3.4.2.1 Option A: PERSONAL.IDX Generation
This option toggles the creation of a file named PERSONAL.IDX, which is an
index for all the messages to the current user. This is used by readers to
quickly display a list of all the personal messages.
3.4.2.2 Option B: Archive type
This option allows the user to select the archiving method they wish to use.
A further menu is displayed, consisting of:
A LHarc
B ARC
C ZIP
and the user is invited to select the appropriate one.
3.4.2.3 Option C: Archive Compression
This option allows the user to turn off any compression on the archiver.
This option is intended for users who have fast modems, and don't wish to
wait the extra long time taken to archive a large mail packet, but just want
to get the mail without worrying about the time it takes to download.
3.4.2.4 Option D: Line Length
This option allows the user to specify the maximum line width that their
reader uses. (the more intelligent readers wrap the words around). This may
cause messages to be formatted differently to the original.
3.4.2.5 Option E: Own message inclusion
Setting this option On will make AMail include messages from the user as
well as those to him, and those which are public.
3.4.2.6 Option F: Maximum Messages
This option allows the user to specify the maximum number of messages that
will be packed. If this number is exceed, the messages will be packed, and
the user will be informed of this.
3.4.2.7 Option G: New Files
This option allows the user to specify that they would like to receive a
a list of new files in the archive.
3.4.2.8 Option I: Bulletins
This option specifies that the user wishes to receive bulletins with the
mail packet.
3.4.2.9 Option J: Batch Pack
The batch pack option allows the user to select the offline packing mode of
AMail. (see later)
3.4.2.10 Option K: Set Default Protocol
Page 11
The default protocol option allows the user to specify which protocol they
would like to use when downloading. If they select one, it will always be
used until it is either changed, or switched off.
3.4.2.11 Option L: Set Oldest Message Date
This option allows the user to specify the oldest message date that will
be packed. If the user enters a '0', this option will be switched off.
3.4.2.12 Option M: Ignore LastRead Pointers
| This option allows the user to effectively pack every message in the
| selected areas. Using this option without caution will mean a VERY large
| packet. Note that even with this option enabled, the "Set Oldest Message
| Date" option will still take effect, thus allowing the user to pack all
| messages since a certain date.
3.4.3 Sysop Menu
The sysop menu is only available to the first user in USERS.BBS. It looks
like this:
Sysop Menu
A User List
B Mail Waiting Users
C Delete User
D Maintenance
Q Quit
These options will be dealt with in turn.
3.4.3.1 User List
This option displays all the users currently using AMail. Each user will
be displayed, along with a number, and whether or not they are currently
using the batch pack option.
3.4.3.2 Mail Waiting Users
This option displays all the users who currently have mail waiting. It
display the user name, and the amount of mail (in Kbytes) of mail they
have waiting. The number displayed next to the user name is the user
number. Note that this is one higher than the number used in the held
mail directory. (So user 1 actually uses 00000000.QWK)
3.4.3.3 Delete User
This option allows you to remove a user from AMail. It will prompt you
for a user name (any case), and then attempt to remove that user from
AMAIL.DAT. This option also renames any held mail packets that change
number.
3.4.3.4 Maintenance
This option allows you to tidy up AMAIL.DAT, and remove any users who
are no longer users in USERS.BBS. Note that this also renames any held
mail packets.
3.5 AMail parameters
AMail is able to take parameters from the command line for two options.
3.5.1 Import
Page 12
The import parameter that is "-i", which forces AMail to run the import
processing if it finds a .REP packet. This is useful for local purposes,
where mail is not uploaded or downloaded.
3.5.2 Batch Pack
AMail is able to perform a batch pack operartion. This is selected by using
the "-p" option on the command line. When the batch pack mode is triggered,
AMail will scan AMAIL.DAT, looking for users who have the Batch Pack mode
switched on. When it finds one, AMail will look to see if a QWK packet is
already being held for that user, and if so, it will unpack it. Once AMail
has completed this, the users options will be taken, and AMail will pack all
the mail for that user, archiving the packet up again when the packing is
complete. When the user logs on, AMail searches it's held mail area (see
later). If a QWK packet exists, AMail will notify the user and ask them if
they wish to download it.
3.5.3 Sysop Menu
The sysop menu of AMail may be directly entered by use of the '-s' option.
once the sysop menu is exited, AMail is terminated.
3.5.4 Maintenance Mode
AMail's maintenance mode may be invoked by the use of the '-m' command line
option. This mode should be run after any USERS.BBS packing utilities are
used.
3.6 AMail Locally
AMail will work quite happily in local mode, providing the DORINFO1.DEF file
is written out as it would be for an online user.
Page 13
4.0 The Configuration File
This is the bit that you've all been waiting for. How do I configure AMail
so that it works on my system ?? Well, as previously mentioned, it has it's
own configuration file, along the same lines as BinkleyTerm ST, and IOSmail.
The configuration file is called AMAIL.CFG, and must reside in the same
directory as AMail. Each configuration option must be on a separate line,
case is irrelevant.
; This denotes a comment. All data after the semicolon is ignored.
ARCarchive <path> <add_cmds> <extract_cmds> <no_compression> <flags>
Specify where to find an ARC compatible archiver. The <path> must
include the full path specification, program name, and extension of
the archiver. <add_cmds> are the options you would use to add files
to the archive. <extract_cmds> are the options you would use to
extract files from the archive. <no_compression> are the flags used
to tell the archiver to store the files uncompressed. <flags> are
any flags you may wish to specify.
| BadPkt <path>
|
| Specifies a directory to be used as a Bad area, so that problem
| packets that are uploaded are not deleted. This option MUST end
| in a trailing backslash. (\). When a packet is copied to this area,
| it is renamed to DDMMHHMN.QWK, where DD is the date, MM is the
| month, HH is the hour, and MN is the minute.
BinkleyLog
This command tells AMail to use the Binkley style of logging.
Bulletin <path>
This option tells AMail where to find the Bulletin file. A bulletin
file is named BLT-n.nn, where n.nn is the version number. (This is a
QWK standard, not an AMail one) Bulletin specifies the full path and
name.
DefName <area_name>
DefName allows you to specify a default area name. This is used in the
QWK readers to place messages if no other area is specified.
DefNumb <number>
DefNumb is used to tell AMail which QuickBBS message area you are
using for the default area. (see DefName)
DiskSafe <kbytes>
DiskSafe tells AMail to check free diskspace before even starting.
<kbytes> is the minimum amount of free kilobytes that must exist on
the Mail (see later) drive.
DelOkay
If DelOkay is specified, all incoming mail files will be deleted
after they have been successfully imported.
Page 14
Goodbye <path>
Goodbye specifies the text file that you wish to be included as a
goodbye file in the mail archive. <path> must specify full path and
filename. This option MUST be included.
Hold <path>
The Hold keyword defines the directory that AMail will store the
batch packed .QWK packets in. It must be terminated in a trailing
slash. AMail will attempt to create the directory if it doesn't
exist.
Location <town>,<county>
Location specifies the town and county where the mail packet is
coming from. It is placed in the outgoing packet, and will
probably be shown to the user when he/she unpacks the mail packet.
LZHarchive <path> <add_cmds> <extract_cmds> <no_compression> <flags>
Specify where to find an LZH compatible archiver. The <path> must
include the full path specification, program name, and extension of
the archiver. <add_cmds> are the options you would use to add files
to the archive. <extract_cmds> are the options you would use to
extract files from the archive. <no_compression> are the flags used
to tell the archiver to store the files uncompressed. <flags> are
any flags you may wish to specify.
Mail <path>
The Mail keyword is used to tell AMail where it's temporary mail
directory is. AMail will look after this directory. <path> *must*
end in a '\' (backslash) If it doesn't exist, AMail tries to create
it.
MainHelp <path>
MainHelp allows you to specify a file that will be displayed when the
user selects Help from the main menu. It should be a standard text
file, with no special control characters in.
| MaxSecPack <security> <messages>
|
| The MaxSecPack command allows you to set a limit on the number
| of messages that are allowed to be packed at a certain security
| level. If a user logs on with a security that is NOT specified in
| AMAIL.CFG, then the number of messages will be unlimited.
| MaxSpeedPack <speed> <messages>
|
| The MaxSpeedPack command allows you to set a limit on the number
| of messages that are allowed to be packed at a certain baud rate.
| If a user logs on with a baud rate that is NOT specified in
| AMAIL.CFG, then the number of messages will be unlimited.
NewFiles <path>
The NewFiles keyword tells AMail where to find the new files listing.
The filename must be NEWFILES.DAT, but the path can be to anywhere.
AMail does *not* append NEWFILES.DAT to the path.
News <path>
News is used to define a news file that is to included in the mail
packet. Users will be able to view this file when it has been
Page 15
extracted by their reader. This MUST be included.
NFProg <program>
NFProg defines the external program that AMail will call when the user
selects the New Files option. <program> should be the full path, file
and extension for the new files program. To prevent problems with the
mouse disappearing in local mode, it is wise to make <program> a .PRG
extension. If the program you wish to run is not a .PRG, simply rename
it.
NoLog <chars>
This option tells AMail not to log certain types of message when in
BinkleyLog mode. It is ignored otherwise. <chars> can be any of:
+ Major Change
- Minor Change
# Information about packed messages
* Information about messages
% Results
! Warning
? Error
~ External Program information
$ Size information
> Debugging Info
PackSec <security>
The PackSec keyword allows you to define a security below which the
batch pack option will not be visible. <security> should be a number,
and will default to zero.
Phone <number>
Phone is used to define the phone number of the BBS. It will be
placed in the archive file, and probably be displayed to the user
by their reader.
Protocol <key> <name> <path> <upload> <download> <expand> <flags>
The Protocol statement defines a file transfer protocol that AMail
will use to upload and download mail packets. <key> specifies the
key that will be used to select the protocol, <name> will be the
name of the protocol, and is limited to 21 characters. <path> is
the full path and file name of the transfer protocol. <upload>
specifies the options to be used for uploading a file, and
<download> specifies those to be used for downloading a file.
<expand> signifies whether the full path and file name will be passed
to the transfer protocol on upload. (It is always password on for a
download). It should be either "D" or "F". "D" means only specifiy the
directory to be uploaded to, and "F" means specify the full filename.
This is meant for use with file transfer protocols that do not transmit
the filename when in use. (XModem, for example). <flags> are any
additional flags that need to be specified. (these will always be added
to the command line of the transfer program). Up to 20 file transfer
protocols may be defined.
| QuickBBS <path>
|
| The QuickBBS keyword is obsolete, and should be removed. Future
Page 16
| releases of AMail will not allow this command to exist in|
| AMAIL.DAT. AMail v2.0 will issue a warning message, and continue.
| Instead of this command, AMail v2.0 uses the QBBS environmental
| variable.
| Replies <path>
|
| The Replies keyword allows you to specify a directory to where the
| uploaded packets will be sent. It MUST be terminated in a
| backslash. (\)
SetUpHelp <path>
SetUpHelp allows you to specify a file that will be displayed when the
user selects the Help option from the Change Options menu. It should be
a standard text file, with no control characters.
SysId <id>
SysId is used to define a system id for the BBS. It must be in the
range 1-8 characters, and should be descriptive of the BBS name.
TidyQuit
TidyQuit is used to make AMail delete all the files in the Mail direcotry
when the user quits AMail normally.
Welcome <path>
Welcome specifies the path and filename of a text file that will be
included as a welcome file. This may be displayed to the user when
they run their off line reader. This MUST be included.
ZIParchive <path> <add_cmds> <extract_cmds> <no_compression> <flags>
Specify where to find an ZIP compatible archiver. The <path> must
include the full path specification, program name, and extension of
the archiver. <add_cmds> are the options you would use to add files
to the archive. <extract_cmds> are the options you would use to
extract files from the archive. <no_compression> are the flags used
to tell the archiver to store the files uncompressed. <flags> are any
flags you may wish to specify.
Any other keywords will be flagged as an error, but processing will still be
continued.
Page 17
5.0 Key requests
5.1 Demo Keys
To receive a Demo key, simply place AMREQ.PRG in the same directory as
AMail, and run it. If QCONFIG.BBS is not in the same directory as AMail,
AMREQ will ask you where it is. Once you have selected it, AMail will read
QCONFIG.BBS, and display a screen, which you should fill in. Once this
screen is filled in, you should press Escape. AMREQ will then enter a dumb
terminal mode, where you should dial The Hobbit's Burrow, on:
U.K. (+44)-[0]245-358667
Once a connection has been made, AMREQ will take over and you should
receive your key. This process takes about 30 seconds, so it shouldn't
be expensive. If you have problems with this method, then please fill out
the Key Request form and either NetMail it to me on 2:257/403.0 (Fido) or
90:102/103.0 (NeST). If you are unable to do this, then I suggest you either
post it to me, or logon to the board on the above number. I CANNOT ISSUE KEYS
WITHOUT THIS FORM, unless AMREQ is used.
5.2 Payment
To pay for your full key, you need £10, (ten UK pounds). This can either be:
o Cash - Not advised
o Cheque - UK cheques only, payable to "A. Styles"
If you're overseas, then you can send me an International Money Order, made
out to "A. Styles". The address to send payment to is as follows:
The Hobbit's Burrow,
27 Laburnum Drive,
Moulsham Lodge,
Chelmsford,
Essex,
CM2 9NR
5.3 Receiving your FULL key
To actually get your full key, allow as long as it takes the money to get
here, and then run AMREQ.PRG. If your money has been received and cashed,
you will get a Full key there and then. If I have received your payment, but
have not had time to cash it, you will be allowed another Demo key, until
I have cashed it. If this option is not attractive, then include a disk with
your payment, and return postage, and I will put the key on the disk, along
with a few other QuickBBS ST programs I've written.
5.4 FULL key cracks
If you receive a FULL key from someone, then please mail me, as if this sort
of thing happens, I will be forced to implement stronger methods of
protection for AMail. (It might even be worth a FULL key to you!) I reserve
the right to change the format of the KEY file at any time, in any release
thus making all those who have already got a key request a new one. (Free to
those who've paid, of course)
Page 18
5.5 Key Updates
If you wish to update the information held in the key file, AMREQ should be
used, following the same method as in 5.1 above. Although it's an drag, I
would be grateful if all those will keys already would run AMREQ and request
a key, to ensure that both they and I have correct information.
Page 19
6.0 Problems
AMail should not give you any problems, but if you encounter difficulties in
using the program, then I can be netmailed on 90:102/103.0, 2:257/403.0.
If you have problems with packets not being processed correctly, please do
NOT just say "I can't get it to unpack" etc, but send me a detailed
description of the problem, along with the packet and your configuration
files for AMail that are causing you problems.
If you can find a way around the problem then I'd be glad to hear of it, as
I can probably cure it in the next release.
6.1 Known Problems
AMail does not currently pass any environmental information to external
programs. I hope to rectify this in a future release.
Disk full errors are not very clean. Again, I hope to tidy this in a
future release.
Not specifying GoodBye, Welcome, or News will result in all the files in
the AMail directory (including AMAIL.PRG and AMAIL.KEY) being packed into
the archive. GoodBye, Welcome and News are REQUIRED configuration commands.
Page 20
7.0 The Future
What does the future hold ? Well, I'd like to expand AMail, so any comments
would be appreciated. However, here is a list of things that are on my wish
list:
o Automatic log off
o Archivers to be handled like Protocols
o User menus, instead of the built in ones
o DOOR.ID files
If you have any suggestions, then please either contact me at The Hobbit's
Burrow, (number elsewhere in this document) or mail me on NeST 90:102/103.0,
or Fido 2:257/403.0.
Page 21
8.0 Credits
I would like to thank Ian Coates of Skull BBS for his forebearance with the
problems that the beta versions of AMail have caused, and his support for
the writing of it.
Thanks also go to Steve Caple of CyberHome BBS, without whom many of the
bugs would have slipped through the net.
| Thanks are also now due to David Thomas, who has helped with the
| beta-testing of the latest version.
Many thanks go to Keith Jackson, who wrote the user guide.
I would also like to thank all the users who've used the beta versions of
AMail and who have not had quite the results they expected.. Just think, at
least you helped AMail become what it is today.
I would also like to thank the various sysops who've put up with the buggy
v1.2, which didn't quite work... Thanks to Dave Thomas of The Dream Machine,
and Paul Whitaker of Excelsior BBS for being the first two contributors!
Thanks also to Kim Andersen of DK-Soft BBS, who has reported many of the
bugs in v1.2.
Thanks to Mike Oldfield for many great albums, without which I wouldn't have
finished this!!
Finally, thanks to who ever it was who invented comms... we'd never be here
otherwise!
Page 22
9.0 AMail Key Request Form
Name: _______________________________________ Age: __
BBS Name: ___________________________________ Started: __/__/__
Location: ___________________________________
Phone: Voice: ________________
Modem: ________________
Net Address: ___:___/___.___
Note: Please enter the above information as it appears in QCONFIG.BBS.
Failure to do so may result in an unusable key! The information
IS CASE SENSITIVE!!!
Address: ___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
___________________________________________
Type of Key: FULL [ ] (include ten UK pounds)
DEMO [ ]
Please note: DEMO keys will normally be available 24 hours after receipt
of the request, FULL keys as soon as the payment is cashed.
Page 23
