||||
0000029A  1 Import Internet Mail
00000D68  2 Crash Contact a BBS
00001194  3 After Importing Descriptions...
00001587  4 UUDECODE A File
000019D3  5 Outbound Node Setup
0000239B  6 Multiple Net Attaches
00002ED6  7 Import AREAS.BBS
000031AC  8 Import .QWK Packet
000034B9  9 ANSI Optimizer
000037EE 10 Remove Lines From A Text File
00003C00 11 ANSI Slow Viewer
000041ED 12 <alt>d/Terminal Program/Dialer
0000532E 13 Zone/Network Configuration
00005B31 14 Message Area Designer
00006101 15 External Door Program Setup
000064AD 16 File Area Designer
0000686E 17 Import a NODEDIFF File
--------------------------------------------------------58

                   Import Internet Mail
First let me say that this is not UUCP or TCP/IP related.
By itself it provides no Internet mail capabilities.  But
what it does provide is a useful ability: to import
Internet messages.

For this to work, you must Save the messages using one of
the mail readers you use to read Internet mail when you
are on the Internet.

Examples of the Save commands for some readers:

  RN:   .-$ s destfile.txt
        will save all messages from the current one, to
        the last one in that area to "destfile.txt".

  VN:   s   will append that message to a file.
        S   will append all messages on the screen to a
            file.  (this is the most convient)

Once you have a file with one or more messages, you can
use this command to import those messages into your
message areas.

As you can see, there is nothing automatic about getting
the mail.  But look into Robot Agents for ways of making
the process more automatic.

All the messages from a single file will be tossed into
one of your Message Areas (of your choosing).

If you want, you can keep the original Internet message
header information--the lines will be marked up similar to
Net Mail--so you can safely re-Echo these messages back
out if you wish.  And just like Net Mail, you can choose
"S" from reading messages to toggle on/off showing of
hidden information lines.

Note: you can specify a wildcard for the pathname, then
all messages from multiple files will be tossed into the
same area.

For best scanning/listing of Internet messages, you should
designate the area an Internet Area when setting up your
Message Areas.

In GLOBAL\MESSAGES you may specify a Kill file for each
Internet area.  This Kill file has the name:

    KILL<area number>.LST

    example: KILL0048.LST  for Message Area #48.
             KILL0002.LST  for Message Area #2.

This is a standard text file.  On each line you put a
string.  When importing messages, if the Subject contains
one of these strings, we do not import the message.

This is VERY useful.  Since Internet Areas are best
managed by you, the sysop or message-op, killing messages
rather than an automatic "only keep newest 200" type
system that works best for EchoMail areas.  This is
because Internet messages have long threads.

For these Kill-file strings, case doesn't matter, and
spaces do matter.  Example: " ani " will properly not
exclude a Subject like "animals are cute", but will for
"Need ANI for 603".

You should also avoid the temptation to make this file
overly long (a couple hundred entries max, depending on
your CPU)--as we loop through them for each message, and
that can really cause importing to slow down.

                   Crash Contact a BBS
This command will set up a special event to call out to
another BBS and try and do a net mail exchange with them.
"Crash" means to try to do it immediately rather than
waiting until a pre-determined mail exchange period.  For
more leisurely Net File Attaching and FREQ'ing do it from
the entering messages screen.

With this Crash Contact command, we can immediately give
messages, give files, or get files from the BBS we
contact.

We try to dial a BBS's number (you can do this for
multiple BBSs) during normal event checks.  Which is
after a user logs off, or after every 5 or so minutes of
inactivity.

When we successfully obtain a carrier (even if the mail
exchange fails) we remove the number from dialing
considerations.

Please note: edit CRASH.$$$ to manually remove an entry.
If you run this on the same net address more than once,
each will be considered to be a separate dialing event.
You can mix and match file sending and FREQ'ing together,
so try and set it up right the first time.

After Importing Descriptions...
You should now do the following steps for New Entries:

 List the contents of each area that you added, or all
  areas if you imported a full list.  This will allow the
  software to match the files it has on-line with what you
  added, and let it fix the size/date/area fields of the
  file entries.  Including discovering files not in the
  file list(s).

 For large/complex imports:
  Exit the BBS, and restart it with the /RESCAN parameter.
  This step will eliminate any extra entries that were
  added for which there are no files in the area.

 If you have just created CD areas, or HD areas that you
  will not be changing when in DOS, you should set File
  Area: "Do Auto-Fixing" off, which will "lock-down" the
  area against future internal adjustments.  But do not
  alter this before the List step above.

 Finally, use Oust Files to remove any undesirable
  entries (such as previous/multiple releases of the same
  program on CD's).

                      UUDECODE A File
This command provides a method to decode files that have
been converted to ASCII-only form using UUENCODE.

These files contain a distinctive structure:

    <anything>
    begin <number> <filename.ext>
    <a long evenly lengthed block of text>
    end
    <anything>
    begin <number> <filename.ext>
    <a long evenly lengthed block of text>
    end
    <anything>
    etc.

Where <anything> is any miscellaneous (ignored) text.  If
any of the interior block lines start with an ANSI
sequence (such as you may if you trapped it with a MORE
reader) these lines are ignored.

We use the <filename.ext> and store the decoded file in
a path you specify.

We do not delete the original file you specify.

Warning: some blocks may be too long for one file, and may
be split into multiple files--merge these if that is the
case (there won't be an "end" on the file parts).

This does handle multiple encoded files in a single text
file.  It also handles unix-formated files where lines
are separated by only a LF (vs. a CR/LF).

                   Outbound Node Setup
This defines how we are to interact with certain nodes and
net addresses.

For any address, we change change a variety of things:
  Their password, type of packet compression to use, type
  of routing to use, and which of our EchoMail areas they
  are to receive.

           <UP>, <Down> to move selection bar.
         PgUp/PgDn (or <Left>, <Right>) to page.
           [Enter] to select.  <esc> to quit.
               <ins> to create an entry.
               <del> to delete an entry.

The entries are sorted when displaying, so the point at
which you do <ins> does not matter.  If you are a Hub
already:  you can convert a large number of addresses (to
save a lot of work) with the Import AREAS.BBS command.

After you have selected an address, you will be taken to a
screen which lets you change things like password and
preferred compression type.

The password you specify is the one THEY must use when
THEY CALL YOU.  When you call them, we use YOUR password
as setup in Passwords & Your Address(es).  When they call
you with multiple addresses, we check each address to see
if it requires a password.

When you are done with this screen, you can (optionally)
to to the Message Area toggle screen which will allow you
to toggle areas ON/OFF for that address.  This only
controls which areas we should check to see if we have any
mail to send them--it has no control or limits over how we
handle mail they send us (inbound mail).

The "Last Read" pointers are the last message number, in
that area, that has been seen by that address.  If you
were to change it to 0, for example, the software would
examine all messages in that area.

When we exchange net mail with the specified net address,
they will be given all new messages in that area from the
first message which has a message number greater than the
last-read pointer, through to the last message in the
area.

When you toggle a message area ON for them to receive, the
last-read pointer is automatically set to the current last
message in that area.  So if you were to poll them
immediately, there would be no mail to send.  This is the
way its normally done.  But you can set the last-read
pointer to zero, and that address will get all the
messages in that area when you/they first poll.  This is
less-used, because the messages are usually real old, or
come in too fast as it is.

The "Security Level" field is not yet implemented.

                  Multiple Net Attaches
This command allows you to "Net File Attach/Send" files to
multiple net addresses in a single operation.

It works as follows: You tell me a net address, or a list
of net addresses, to use.  You tell me a pathname, or a
list of pathnames, to use.  I then will make a note to
myself that each of those pathnames specified are to be
sent to each of those net addresses.

When you next Net contact one of those net addresses, they
will be given a copy of the file(s) you specified.  In
addition to their normal mail (if any).

Note: this is an update utility.  It updates the list of
file attaches to send to a net address.  So feel free to
run it multiple times on any net address to add new/more
files to what you want them to receive.  When specifying
a list of files, the list need only contain changes since
the last list you specified.

The first question you are asked is for a net address to
use.  You may specify a net address (zone:net/node) or use
"@pathname" to tell me to use a pre-created list of net
addresses.  This list file should be a normal text file
with one net address per line.

  Example:   1:154/42
             200:200/1
             200:503/0
             @c:\bbs\friends.lst

The next question you are asked is for a pathname to use.
You may specify a pathname (d:\dir\filename.ext) or use
"@pathname" to tell me a pre-created list of pathnames.
You may use wildcards.

  Example:  C:\DNLOADS1\JDRBBS??.*
            C:\WP\LETTER.TXT
            @C:\BBS\TOSEND1.LST

The pathname(s) you wish to send should not be moved or
deleted until all the receipients have gotten their copy.

This command is useful when you want to distribute one or
more files in a single pass to multiple net addresses.

Example: you just created a beta update, and you want all
your beta sites to get a copy of it.

Example: you provide a GIF file distribution service.
A user uploads a GIF, and each night you run this to net
that GIF to all subscribing nodes.

Example: you want another BBS to get all the files
uploaded to you each day.  You just make a list of new
files, run this, and then either poll that second BBS or
wait for them to poll you.  Can be done on both BBS's so
each sends the other new files nightly (or weekly, etc.).
The best way to do this is to have an Uploads area, then
specify path\*.*, then after the exchange is done, move
all the files in this Uploads area to an Old Uploads
area--so that is clean for the next day.

That's it.  I make a bunch of notes to myself, but the
files are not copied so no extra disk space is used.

These file attaches are sent whenever that net address
contacts you, or you contact them.

In some cases, this is a lot more convienent then calling
up and downloading, or setting up FREQ'able files.

                     Import AREAS.BBS
This command allows you to import/convert a AREAS.BBS file
to the Outbound Node Setup format we use.

This command is mainly meant as a one-time conversion
utility to change-over large/complex net mail setup's.
Like those of Host's or Hub's.  Faster than doing Outbound
Node Setup by hand.

Before using this, however, your message areas must be set
up on this system as they were under your old BBS--area
for area.  Or you will just end up with a conversion that
points addresses to the wrong EchoMail areas.

The new data is appended to what you already have done in
for Outbound Node Setup.  You can also run this more than
once to import multiple AREAS.BBS files.

                    Import .QWK Packet
This provides you a method to import a single .QWK mail
packet into one of your Message Areas.

.QWK packets are packs of messages you downloaded from
another BBS.

Usually viewed using an off-line reader, you can use this
command to import the messages, and later view them
on-line as normal messages (or to make them available for
other users to view).

ALL messages from the .QWK file will be tossed into a
Message Area of your choosing.  So even if you downloaded
messages from numerous areas on another BBS, they will all
still be put into a single one of your areas.

If you frequently do this command, it might be better to
set youself up a "mini-net" between you and that BBS and
exchange messages as Net Mail.

                      ANSI Optimizer
This will reduce the size of most ANSI's.  Resulting in an
increase in speed and faster transfer speed.

This allows you to quickly cut the size of large ANSI's,
including animated ANSI's.  It does a good job, and is
useful for preparing an ANSI for further hand optimization
with a text editor.

What it will not optimize is ANSI's that have already been
optimized in some manner.  Doing the optimizations by hand
will always produce the best results.

If an ANSI comes out of this process displaying
differently than how it went in, then something went
wrong.  Drop me a copy of it so I can modify this routine
to handle it properly.

Going into TheDraw and re-saving the ANSI (one line
format) then running this on the result can reduce the
size even more.

               Remove Lines From A Text File
This command will let you remove all lines from a text
file which contain any one of a variety of strings you
input.  When entering the exclusion strings, you can use
spaces as part of the string, and case is ignored.

I created this command to make my processing of the Erotic
Binaries Internet areas more efficient.

Specifically, I would use this as so:

  Using RN:

  I would change to alt.binaries.pictures.erotica.

  I would then do a <alt>t (trap all on) and "=" and page
  through the summary listing of all messages.

  I would then run this on that trap file, removing all
  lines with "re:", "repost", "index", and "twink".

  The resulting file is much faster for me to look over,
  as it doesn't include the "junk" entries (a large
  number usually).

  I then re-login to my Internet account, and jump around
  getting those binaries I want, and then use "C"atchup.

Note: the text file must be a standard text file with
lines ending with a CR/LF.

                     ANSI Slow Viewer
--------------------------------------------------------58
This is an ANSI file displayer.  Useful for displaying
such things as the trap file and stuff which is too long
for one screen, and too fast with DOS's TYPE command.
25/50 line modes are supported (/USEVGA or /USE50 forces
50 line mode, otherwise you can use F5 to toggle 25/50).

This is not recommended for reading messages.  For that, I
recommend using the Strip ANSI/Avatar filtering command.
Then View A File from the WFC screen--as this lets you do
lots of reading while not tieing up the BBS (it
automatically exits when a RING is detected).

You will be asked for a delay factor.  0 is no delay, 1
short, 2 a bit longer, etc.  This will delay the specified
value in 18ths of a second before displaying each ANSI
sequence.

Wildcards are OK and ecouraged.  It also does a great job
with ASCII files (both art and literature).

Some special coding allows this command to be used as a
normal menu command:  if the user is not the sysop, and
not at the console, instead of a path we ask for a
downloadable file name.  This lets you create special
file areas with nothing but .ANS's.

If an ANSI is believed to have hidden text, this routine
will tell you so, and then redisplay the ANSI with the
hidden text flashing.

I personally use this command to view Art Packs.  Just
give it path\*.ans etc. and it does it very quickly.

When viewing: [Space] to pause, [Enter] to quit.

              <alt>d/Terminal Program/Dialer
This command provides 3 different systems.  The first is
Command Mode access to your modem, the second is a Dialer
system you can use to call other BBS's, and the third is a
Terminal Program which you can use to talk to BBS's (and
works pretty good with Unix/Internet systems too).

When you first do this command, you get the Command Mode
display.  From this you can do <ins> to access the Notepad,
<del> to access the menu, and <esc> to exit back to WFC.

You can also:

    ATDT<phone number> to dial a phone number.
    n netaddr          to call the BBS that the netaddr
                       (net address) belongs to.
                       Example: n 1.154.7020
    d <string>         to call the BBS which has <string>
                       as part of its Dialer record.
                       Example: d immortal

<del> and <ins> also work when on-line with another BBS.

The Notepad is a simple system for sending common strings.
You edit it by using a text editor on the
GLOBAL\TEXT\NOTEPAD.TXT file.  You can insert ASCII 1 or 2
(the face characters) to tell the software to insert a
CR/LF at certain spots (for multi-line string sends).

<del> brings up the following menu:

    The Dialer         <alt>D
    Get Files (download)
    Send Files (upload)
    Poll them for Net Mail
    Clear/Reset screen <alt>C
    25/50 line mode    <alt>5
    Hang Up            <alt>H
    Trap All On/Off    <alt>T
    Shell to DOS       <alt>S
    Log them into your BBS
    ASCII send a file
    Select Comm Port
    Begin in the Dialer: ON/OFF
    Cmd Line RING->exit: ON/OFF

Most are self-expanatory.

"Poll them for Net Mail" is a lot like F10 Crash Contact,
but what happens is it dials, connects, and then you
select this command and it will attempt to exchange mail
with them (you need to execute this command very early
after connecting).  What its mainly useful for is testing
problem BBSs to see what's wrong, or for contacting BBSs
to exchange mail whom you don't have a nodelist entry
for and only want to contact a couple times (and thus need
to dial manually instead of making a menu command or using
Crash Contact).

"Log them into your BBS" only works when calling other
Juggernaut BBS's.  What it does is "turn the tables" and
let that BBS's sysop log into your BBS without
disconnecting/etc.  Useful for debugging or showing
another sysop your BBS.  For instance, if you call another
Juggernaut BBS and say "Help--call my BBS and see this..."
He doesn't have to call, but can just tell you to call
with <alt>d.  Then you chat, agree to do this, exit chat,
and both do <alt>d on each end.

"Begin in the Dialer" controls whether you want <alt>d to
first start in Command Mode, or in the Dialer.  It is
usually more convienent to start in the Dialer.

"Cmd Line RING->exit" controls whether you want a RING
while in Command Mode to trigger an exit back to WFC.
This gives your callers higher priority than your dialing
efforts.  However, you want this off if you're in the
middle of doing a call-back verification with a BBS.

The phone Dialer system works as follows:

There are two types of entries: Topics and non-Topics.

Topic entries have a "->" in the Password, and when
selected will move you to another selection screen.  You
can grow whole trees of selection screens.

When you select non-Topic entries, that phone number will
be dialed as-is.  Non-Topic lines do not need to have a
phone number--allowing you to store additional information
about a BBS in the Name/Notes lines following the primary
entry.

    Arrow keys to move about.
    [Enter] to dial that number once.
    <ins> to edit that slot.
    <del> to delete that slot.
    To move entries around, use <tab> to both pick-up and
    drop-down entries.
    F5 to edit your IEMSI definitions.

IEMSI (supported by some BBSs) provides a faster more
automatic login when you call that BBS.  The three IEMSI
configurations are useful for when you want Real/Real,
Real/Alias, Alias/Alias, etc. combinations.  For IEMSI:
the password used is the dialing password field.

Put a "+" after the phone number itself (in phone number
field) to have the software switch to 50 line mode when
you call that number.  Very useful for those BBSs that
like 20 line file descriptions.

                Zone/Network Configuration
This defines how you interact with various zones.

None of the entries on this data form are required.  Use
it as you need it.

For any network/Zone, there are 3 things one usually has:

    An address of their own (Primary Net Address).
    A nodelist for that network.
    And a Hub (unless you are the Hub).

Additional things are multiple addresses in that Zone
(AKA's) and session-level passwords (also used for
AreaFix and TIC passwords).

The first Zone entry you create is used as the "filler
template" to complete partially entered addresses.  For
such things as when entering a destination net address for
Private NetMail.  So this first Zone entry should be your
most common/popular network.

The "Hub" field tells the software that when that Hub
address calls, give them ALL mail for that Zone unless
that mail (or its destination address/etc.) explictly says
to not route via the Hub (route directly).  Otherwise the
Hub field is not used/needed.

A net address does not need to be given a "Hub"
designation unless you yourself are acting as a hub for
routing other node addresses mail through you.  For most,
it serves as a reminder field.

The nodelists should remain in standard text-list format.

To include a new nodelist, just put the nodelist file
where you want it, and add/change the entry and restart
the BBS.  Each time you change the nodelist (text file),
these changes are detected when you restart the BBS and it
will automatically rebuild the nodelist indexes.

You cannot use wildcards for the pathname.  This was done
because too many people were keeping indexes or old
nodelists in that same path.  However, rather than update
each entry when you get a new nodelist, I recommend you
simply keep it a common filename, and just rename each new
nodelist to this filename.  Example: FIDONET.NET

If you do enter a wildcard, the software will locate the
first matching file and update the entry with that name
before saving it.

                  Message Area Designer
This will allow you to configure/alter your message areas.

Multi-node: if change, restart all nodes so they learn the
changes.

 Attributes, when ON 
  1  if all messages are to be FROM: ANONYMOUS.
  2  if this is a private messages area (otherwise
     public).
  3  if this is a net mail area.
  4  if should record the packed messages in DEL_MSGS.TXT
     historical archive.
  5  if users are NOT allowed to delete messages in this
     area.
  6  if all messages are to be forced TO: ALL always.
  7  if should show ^A NetMail hidden/control lines.
  8  if should automatically delete NetMail msgs after
     [Sent] to BBS's.
  9  if this is an EchoMail area (also set 3 ON).
  0  if should maintain a MSGSTUFF\<area>.TXT file of all
     messages.
  A  if should append the Origin line (SHORT.TXT line 6)
     to the end of outbound EchoMail that this BBS
     created.

     Note: " * Origin: <text>" is the correct format for
     an origin line, you should not ingore each space.

  B  if FROM: <real name> always (some Echo's require
     this).
  C  to NOT include source name at top of quote bracket
     when replying.
  D  to report non-user status for TO/FROM for non-net
     areas.
  E  to allow long-form net addresses (like Internet).
  F  if this is an Internet mail area (creates a special
     index, Scan Messages uses a special interface, etc.)

               External Door Program Setup
Use this to design your door access system.

From the menu system, you may call up any of the doors by
using the commands:

   DOOR _doornum   To execute door #doornum
                   (ie. _1 = #1 = your 1st defined).

   DOOR _g##       To execute a door from an internally
                   generated menu consisting of only
                   those doors in Door group number ##.

   DOOR            To execute a door from an internally
                   generated menu of ALL doors.

Simply "DOOR" for a menu command is the best when just
starting up.  After a while sysops usually like to do
their own door menus, and use the "DOOR _#" command for
that.

For extremely complex and sophisticated door menus, one
usually uses "DOOR _#" with its own menu system.

The "Door" (not "DOOR") command is useful also when all
you want to do is a quicky shell to DOS.

                    File Area Designer
Use this to design/define your upload/download file areas.

Multi-node: if change, restart all nodes so they learn the
changes.

Most of the parameters are self-explanatory.  However, I
just want to touch on a couple:

  Also Paths

    These are directories that are to be folded into this
    area when we list the contents of this area.  Very
    useful for merging CD-ROM directories.

    You can have up to 6 of these.

  Echo Tags

    These are for those of you subscribing to a File Bone
    that sends you files via Net Mail.

    When the BBS receives a TIC file attachment, we look
    at these Echo Tags to determine into which area we
    toss the file.

    You can have up to 4 different File Echos tossed into
    any one area.

  File Listing Format Templates

    These are stored in GLOBAL\TEXT\LISTING.TXT.

    Very flexible.  Pick one you like or make your own.

                  Import a NODEDIFF File
This command will merge/update your old text nodelist file
with the new information/changes provided in a NODEDIFF
file provided to you from your Hub.

We first ask you for the pathname of this NODEDIFF file.
You can specify a wildcard--it will use the first one
matching (these NODEDIFF files all have oddball hard to
remeber filenames).

We then ask for which network it belongs to.  For this
to work properly, your Zones & Your Addresses setup must
not have a wildcard for the nodelist pathname.

We then unpack it if necessary, and obtain the changes.
If there is more than one file in the archive, then we
only use the first file.

We do not delete the NODEDIFF file you specify.

NODEDIFF files must be imported in sequential order.
These files have special checks to allow us to import them
in proper order.  Should you try to import one out of
order, we simply won't allow it.  You will be given a
"NODEDIFF file is invalid for this date" message.  This
also happens if you mix up your NODEDIFF files and try
to import them in the wrong order, or in the wront net.

If you do miss a NODEDIFF, you have no choice but to
re-get a complete copy of the nodelist again from your
Hub or other sources.

After importing the NODEDIFF file, we will rebuild the
nodelist index.


