HOW TO INSTALL, CONFIGURE, AND USE
                    ECHOMAIL AND GROUPMAIL WITH TELEGARD
         By Martin Pollard - SysOp, The I/O Bus (FidoNet 1:120/187)

                         Revision 1  -  29-Sep-1990


EchoMail and GroupMail capability is one of the long-awaited features that
Telegard versions 2.5 and higher provide.  EchoMail and GroupMail are, in a
nutshell, public message conferences that are transmitted to different BBSes
around the country and across the globe.  You could write a message in
Michigan, and see a reply (a few days later) from someone in California,
Ontario, or even Europe!  (These conference are transmitted via the FidoNet
electronic communications network, or by networks that use the same
technology as FidoNet.)

(From here on, EchoMail will be referred to as EM, and GroupMail will be
referred to as GM.  Saves wear and tear on the fingers!)

For all their advantages, EM/GM have one glaring disadvantage:  They can be
a pain to set up.  This document is an attempt to alleviate some of that
pain, by presenting a step-by-step guide to configuring EM/GM for use with
Telegard.  Note that this document only goes over installation of EM/GM; it
does not attempt to be a tutorial on how to use a mailer, how to set up mail
events, etc.  Other texts have been written on those subjects, and will not
be presented here.

Also note that in order to effectively process EM/GM, you should have AT
LEAST ONE MEGABYTE FREE on your hard drive (two or more is recommended,
however).


REQUIRED SOFTWARE

You will need the following software:

        *  A front-end mailer.  BinkleyTerm, D'Bridge, FrontDoor, and SEAdog
           are the most popular mailers in use within FidoNet and other
           networks.  (This document will assume you are using FrontDoor;
           alterations to these procedures may be necessary for other
           mailers.)

        *  An EchoMail processor.  There are too many available to list,
           though ConfMail, Qmail, and Zmail are the most popular of the
           Shareware programs.  (This document will assume you are using
           ConfMail, which works well with FrontDoor; as above, alterations
           to these procedures may be necessary for other EM processors.)

        *  A GroupMail processor.  There are currently two available, GROUP
           and GMAIL, though the latter is geared towards the QuickBBS
           program.  (This document will assume you are using GROUP.)

        *  The ARC file archiving program.  This is necessary for using GM;
           no other archiver will do.

        *  The TeleMail program.  This is necessary to place incoming EM/GM
           messages in Telegard's message bases, and to take messages from
           Telegard's message bases and create the necessary outgoing
           message files.

Most of the programs listed here are available at The I/O Bus (for both
downloading and file request [for those that know how to file request]).  A
list at the end of this document gives the programs, their current versions,
and the filenames of these programs.


INSTALLING AND CONFIGURING TELEMAIL

We will get the installation of TeleMail out of the way first, as its use is
common to both EM and GM.

1.  Unpack the TeleMail distribution archive into your main BBS directory.
    The only file needed is TELEMAIL.EXE; you may delete the other files
    that came in the archive.

2.  Create a file called TELEMAIL.CFG using your favorite text editor.  The
    file should look like this:

        ECHO_TOSS CONFMAIL IMPORT AREAS.BBS -K -D 1000 -A ARC X
        ECHO_SCAN CONFMAIL EXPORT AREAS.BBS -D C:\FD\PACKET -A ARC A
        GROUP_TOSS GROUP IN
        GROUP_SCAN GROUP OUT
        POST_PROCESS GROUP ASK

    This configuration file defines the commands that TeleMail will execute
    to import and export EM/GM messages.  TeleMail is "smart" enough to do
    the necessary steps automatically, leaving you one less thing to worry
    about.

    (If you aren't going to be processing EM, take out the ECHO_TOSS and
    ECHO_SCAN lines.  Likewise, if you aren't going to be processing GM,
    take out the GROUP_TOSS, GROUP_SCAN, and POST_PROCESS lines.)

    TeleMail keeps a log file of all activity, which can grow rather large.
    If you don't want to use the log file, add the line NO_LOG to the end of
    the TELEMAIL.CFG file.

3.  Unpack the ARC distribution archive into the main BBS directory, or in
    any directory in your PATH.  The only file needed is ARC.EXE; you may
    delete the other files that came in the archive.

That is all there is to it.  However, this was the easy part; the hard stuff
is yet to come.


INSTALLING AND CONFIGURING ECHOMAIL

For simplicity, the required EM files and directories will be set up in your
main BBS directory (we will assume it is C:\BBS for these examples).  As was
noted earlier, we will assume that you are using ConfMail as your EM
processor; alterations will be required for other processors.

You should print and examine the documentation that comes with ConfMail, to
get a better idea of its features and capabilities.

1.  Unpack the ConfMail distribution archive into your main BBS directory.
    The only file needed is CONFMAIL.EXE; you may delete the other files
    that came in the archive.

2.  Create a directory called ECHO by using the MKDIR command ("MKDIR
    ECHO").  The use of this directory will become clear shortly.

3.  Create a file called CONFIG.DOG using your favorite text editor.  The
    file should look something like this:

        NODE 1:120/187
        NAME Martin Pollard
        MAIL C:\FD\MAIL
        FILES C:\FD\FILE

    Note that this is ONLY an example.  You will need to place your FidoNet
    address on the "NODE" line, your name on the "NAME" line, and the
    pathnames of your mailer's mail and file directories on the "MAIL" and
    "FILES" lines.

4.  Again using your favorite text editor, create a file called AREAS.BBS
    that will look something like this:

        The I/O Bus ! Martin Pollard
        ;-------------------------------------------------
        C:\BBS\ECHO\BAD_MSGS   BAD_MSGS
        C:\BBS\ECHO\TELEGARD   TELEGARD   120/45
        ;-------------------------------------------------

    Again, this is only an example.  You will need to put your BBS name and
    your name on the first line (the "!" is mandatory; it separates the
    two).  The line for the TELEGARD conference is only an example, but if
    you wish to receive the conference, you will need to talk to your Net
    Coordinator (NC); the line for BAD_MSGS will be explained shortly.

    The lines that describe each conference are set up as follows:

        *  The directory that will hold the individual messages for that
           conference.  Each conference must have its own separate
           directory, or else the conferences will get mixed up (which is
           NOT good!).

        *  The conference "tag".  This is the unique name that identifies
           each conference.  A list of available conferences should be
           available from your NC.

        *  Each system that you are feeding the conference to.  The first
           address is usually your "feed" (i.e. the system that you are
           picking up the conference from), while subsequent addresses are
           the systems that are picking up the conference from you.  I would
           not recommend getting involved in multiple feeds until and unless
           you are comfortable with EM.

    The exception to this is the BAD_MSGS conference.  This is not a real
    conference; rather, it is a special feature of ConfMail.  It is where
    bad messages (duplicate messages, or messages from conferences that you
    aren't receiving) are placed.  You can later examine and delete these
    messages, or whatever.

5.  Create a BAD_MSGS directory inside the ECHO directory with the MKDIR
    command ("MKDIR ECHO\BAD_MSGS").  The other directories for EM
    conferences will be created with Telegard (described later).

The concept of EchoMail is "delivery-based", in that you will deliver
messages to the systems receiving the conference.  Obviously, this can be
cost-prohibitive, sending the conference to every system receiving it
(especially if any systems are long distance), which is why EchoMail can
also be "pickup-based" (you hold the messages for the other systems to pick
up).

If you are not going to be using GroupMail, skip to "Configuring Telegard";
otherwise, proceed to the next section.


INSTALLING AND CONFIGURING GROUPMAIL

For simplicity, the required GM files will be set up in your main BBS
directory (we will assume it is C:\BBS for these examples).  As was noted
earlier, we will assume that you are using GROUP as your GM processor;
alterations will be required for other processors.

You should print and examine the documentation that comes with GROUP, to get
a better idea of its features and capabilities.

1.  Unpack the GROUP distribution archive into your main BBS directory.  The
    only file needed is GROUP.EXE; you may delete the other files that came
    in the archive.

2.  If you are using ConfMail for EM processing, you will have already
    created a CONFIG.DOG file (which is also used by GROUP) and you can
    proceed to the next step.  If not, you will have to create it; refer to
    step 2 in the EM setup instructions, then proceed to step 3 below.

3.  Enter the GROUP configuration screen via the "GROUP EDIT" command.  Once
    there, use the arrow keys to move back and forth between the various
    YES/NO options.  The following options should be set to YES; all others
    should be set to NO (to set an option to YES or NO, just press "Y" or
    "N" when the cursor is at the appropriate option):

        Scan for duplicates
        Strip VIA lines on a PACK

    The next portion will require some typing.  On all of the lines that
    look like requests for pathnames or filenames, you must insert the
    pathname of your main BBS directory (i.e. "C:\BBS\").  If this is not
    done, GROUP will not work properly.  These lines are:

        Name of areas file
         .
         .
         .
        Group mail staging area #1

    Leave all other options alone.  After you have finished, press [ESC] to
    save the changes and exit to DOS.  You will see a file called GROUP.CFG
    in your main BBS directory; this file holds the configuration you just
    set up.

4.  We will now set up a sample conference.  Type the following command:

        GROUP ADD TG_DEVEL Telegard Software Development ; 120/187

    This command will add a new conference to the GroupMail system.  Here is
    what each portion means:

        ADD             The GROUP command to add a conference.
        TG_DEVEL        The area tag for the conference (see the EM
                        configuration instructions for more information on
                        area tags).
        Telegard...     An optional description of the conference.  It can
                        be anything.
        ;               A required separator.
        120/187         The system you will pick up the conference from,
                        which is known as the "star".

    You will see a file called AREAS.DOG in your main BBS directory.  This
    file is analogous to EM's AREAS.BBS file, in that it keeps track of each
    conference and where it's coming from.  You will not normally need to
    edit this file by hand; GROUP's commands will do all of the work in
    almost all cases.

Unlike EchoMail, the concept of GroupMail is "pickup-based", in that systems
pick up conferences from the feeding system (the "star").  Also unlike EM,
GM accomplishes this via the mailer's file update request feature (in which
the conference files themselves are requested, and if any are dated earlier
than the last one obtained in the previous session, it is not sent).  There
are other advantages to GM, but they will not be dealt with here; instead,
see the text file GRP-ECHO.TXT, enclosed in this archive.


CONFIGURING TELEGARD

At this point, you should have EM and/or GM configured properly, with all
necessary files in place.  In your main BBS directory, you should have
ECHO and/or GROUP directories.  If anything is not present that should be
present, go over the installation instructions.

Configuring Telegard is now simply a matter of setting defaults and
installing new message bases.  Ready?  First, we'll cover the defaults:

1.  Load up Telegard.  Use the "-K" switch on the command line to go into
    local mode; that way, you won't have to deal with the modem.

2.  At the WFC menu, select "P" (System Configuration); at the System
    Configuration menu, select "I" (FidoNet Configuration).

3.  Select option "A" to set your FidoNet address.  In most cases, the zone
    will be 1 (North America) and the point will be 0.  The net is the net
    number your system falls in, and the node is assigned by your NC.

4.  If the default origin line looks fine, leave it; otherwise, select
    option "B" and create a custom origin line.  Usually, you'll want to put
    your system name, phone number, and location (try to fit in as much as
    you can).  Don't put in the network address, as that will be added
    automatically when messages are imported/exported.

5.  Review options "C" through "I".  All except "E" (strip origin lines)
    should be set to YES; "E" should be set to NO.  If this is not right,
    make the appropriate changes.

6.  Similarly, review options "1" through "4".  In most cases, the colors
    specified here are quite pleasing under the default color set.  (An
    alternate set is 1, 9, 4, and 3 for options "1" through "4".)  If you
    have changed the default color set, you might want to experiment with
    these colors to get the most pleasing combination.

7.  If you are using version 2.5, skip to step 8.  Otherwise, review options
    "J" and "K".  These are the default pathnames for EM and GM directories,
    and must be changed for your setup.  These should be:

        J - "C:\BBS\ECHO\"              K - "C:\BBS\GROUP\"

    Remember to plug in the pathname of YOUR main BBS directory in place of
    "C:\BBS".

8.  Press "Q" at the FidoNet Configuration and System Configuration menus to
    get back to the WFC menu.

Now, we'll install two message bases based on the examples given in the EM
and GM configuration sections.

1.  At the WFC menu, select "B" to enter the Message Base Editor.

2.  Use the (I)nsert command to insert two new message bases, then use the
    (M)odify command.  Select the first base that was inserted.

3.  First, we'll tackle an EM base.  Configure the following:

        Name:           Telegard Support Conference
        Filename:       TELEGARD
        Base type:      EchoMail
        Message path:   C:\BBS\ECHO\TELEGARD\
        ACS:            <your choice>
        Post/MCI ACS:   <your choice> / "%"
        Max messages:   <your choice>
        Anonymous:      No
        Password:       <your choice, or "">
      * Address:        Default
        Colors:         <your choice, or use defaults>
        Mail flags:     KS-/CBMT
        Origin line:    <your choice, or use default>

        *  If you are using version 2.5, this option does not exist.

    A few words of explanation.  Since non-Telegard systems don't recognize
    Telegard's MCI codes, setting the MCI ACS to "%" will disable them (you
    should do this on all conferences).  On conferences with a lot of
    traffic, you'll want to set the maximum messages value to a high number
    (200 or more) so that you don't miss messages.  Also, since most
    conferences don't allow anonymous messages, you should leave the
    anonymous setting at NO.

4.  Now, we'll tackle a GM base.  Use the "]" command to go to the next new
    base, then configure the following:

        Name:           Telegard Software Development
        Filename:       TG_DEVEL
        Base type:      GroupMail
        Message path:   C:\BBS\GROUP\TELEGARD\
        ACS:            <your choice>
        Post/MCI ACS:   <your choice> / "%"
        Max messages:   <your choice>
        Anonymous:      No
        Password:       <your choice, or "">
      * Address:        Default
        Colors:         <your choice, or use defaults>
        Mail flags:     KS-/CBM-
        Origin line:    <your choice, or use default>

        *  If you are using version 2.5, this option does not exist.

    As you can see, things are slightly different.  For one, the base type
    is "GroupMail" instead of EchoMail.  (If you are using a version later
    than 2.5, you will be asked if your system is a TopStar for this base;
    answer NO.)  For another, the "T" flag is missing from the mail flags.
    "T" tells Telegard to add tear and origin lines to the bottom of
    messages.  They are required for EM, but not for GM (although they are
    harmless if added; if you want them, just re-enable the "T" flag).

5.  If you have other EM/GM bases you need to configure, repeat the above
    procedure for as many bases as you need.

6.  Once you are satisfied that everything is configured correctly, press
    "Q" to go back to the main editor menu, "Q" again to return to the WFC
    menu, and "Q" yet a third time to exit to DOS.

That does it for Telegard.  Now... one last thing...


CONFIGURING THE MAILER TO PROCESS MAIL

This one is tricky, as no two mailers configure this the same way.  You will
have to refer to your mailer's documentation; find the sections that
describe how to make your mailer exit when mail is received.  Usually, it
involves a configurable ERRORLEVEL value.  Then, edit your main batch file
(RUNBBS.BAT, or similar) to jump to a section when that ERRORLEVEL is
returned by the mailer.  Add this section to your batch file:

        :MAIL
        CD C:\BBS
        TELEMAIL ALL
        GOTO FD

(The GOTO statement will need to be modified to jump back to the portion of
your batch file that enables the mailer.  Also, the CD statement may need to
be changed to YOUR main BBS directory.)

Yes, it's that simple.  TeleMail will take care of the business of importing
and exporting the mail; you don't have to do a thing.

You should also set up an event to call this section once a day; that way,
even if there is no incoming mail, outgoing mail will still be processed.
(In FrontDoor, for instance, this can be done via an "external" event; such
an event should be configured to be "forced", so that even if external
activites cause the event to be missed, it will be executed anyway.  Again,
check your mailer's documentation to see how this is done.)


USING ARCHIVING PROGRAMS OTHER THAN ARC FOR ECHOMAIL

GM requires the use of ARC for its mail bundles, but EM is not so limited.
Certain EM processors (like Qmail and Zmail) have built-in capabilities to
handle mail in multiple archive formats.  ConfMail does not, but it can be
added with the assistance of external utilities.  For outgoing mail, a
program called ARCA*Simulator will allow configuring of different systems
for different archive formats.  For incoming mail, programs like PolyXarc
and GUS (General Unpack Shell) will examine the mail bundle, determine which
archiver created it, and use that archiver to extract the mail.  All three
of these programs are available from The I/O Bus (1:120/187); check the list
below for filenames and current versions.  Follow the documentation included
with each to determine how to install and configure them.  (Hint:  You will
probably need to modify the command lines in TELEMAIL.CFG...)


CURRENT PROGRAMS AND FILENAMES

These programs and filenames are all available for download (and file
request) from my system, though you might be able to find them locally.

        FrontDoor v1.99c                FD199C.ZIP
        ConfMail v4.00                  CONF_400.ZIP
        Qmail v1.00                     QM_100.ZIP
        GROUP v2.19                     GROUP219.ZIP
        ARCA*Simulator v2.01            ARCA05.ZIP
        GUS v1.20m                      GUS_120M.ZIP
        PolyXarc v2.00                  PXDOS_20.ZIP
        ARC v6.02                     * ARC602.EXE
        TeleMail v1.20                  TMAIL120.ZIP

*  ARC v6.02 is a self-extracting archive.


CONCLUSION

I've tried to be as thorough as possible, while making this document as
general as I could.  EchoMail and GroupMail can be confusing things, and no
one document can hope to cover all their aspects.  If you have any
questions, or find problems with anything presented here, I can be reached
at The I/O Bus (9pm to 9am Eastern time only) directly, or via NetMail to my
FidoNet address (1:120/187).  My system supports 1200/2400/9600/14,400 bauds
(HST and V.32).