
                             PCB-MHS   README.TXT
                             --------------------



Addressing messages:

   There are a couple of methods that people can use to send MHS messages from
   other systems to your BBS.


   Method 1:

   Their MHS administrator needs to add a workgroup route entry for your host.

   Example:
        Your Host: yourhost
        Your PCB-MHS Workgroup: yourbbs

        Their MHS entry: yourbbs GTW <via yourhost>

   This is accomplished by their MHS administrator adding an intermediary
   workgroup (yourbbs) that is routed via your host (yourhost).

   Addressing a message to a user on your system (joe smith), would look like
   this:

        jsmith@yourbbs

   We strongly advise that you name your PCB-MHS workgroup something other than
   PCBOARD or PCB-MHS.  It should be your BBS's name, but be different from
   your host name.


   Method 2:

   You need to add a user route in your MHS configuration.

   From the above example, you would create a user route with a username of
   your PCB-MHS workgroup name (yourbbs) or PCBOARD, that would be routed to
   your PCB-MHS workgroup (yourbbs).

        user-route: pcboard  ->  yourbbs

   From another system, addressing a message to a user on your system (joe
   smith), would look like this:

        pcboard@merlin {Joe Smith}
        or
        pcboard@merlin {jsmith}

   Please note the use of the extended address.  You may also use this form:

        pcboard@merlin (Joe Smith)
        or
        pcboard@merlin (jsmith)

   With this method, MHS will route all mail addressed to pcboard to the
   PCB-MHS gateway (yourbbs).


   Method 3:

   You can set up a user route for every user that will receive MHS mail.
   Example:
        User: Joe Smith

        user-route: jsmith  ->  yourbbs

   This would allow any messages that were addressed to jsmith@yourhost routed
   to jsmith@yourbbs once your MHS processed the mail.


   Method 4:

   They can include your host name in your address.

   Example:
        jsmith@yourbbs [yourhost]

   Some email packages might not be able to address MHS messages this way.


Addressing users from PCBoard:

   When entering a message in PCBoard in the MHS conference, a user can
   address the message in a couple of ways.

   Method 1:

   Placing a valid MHS address, with or without a workgroup, application,
   comment, and extention.

   eg.

   jsmith
   jsmith @ workgrup
   jsmith.applicat @ workgrup
   jsmith @ workgrup {/C=CA/ADMD=Telecom Canada/G=John/S=Smith}


   Method 2:

   Placing a regular user name in the destination field will cause PCB-MHS
   to format it according to standard naming conventions.

   eg.

   JOHN SMITH  -> JSMITH



Adding more than one workgroup for PCBoard:

   You can add more than one workgroup for your PCBoard by installing
   PCB-MHS multiple times.  Each installation must have a different workgroup
   name and reside in a different conference.


-------------------------------------------------------------------------------
PCB-MHS Instructions for Direct Opeartion with cc:Mail
-------------------------------------------------------------------------------

You will need to create the following directory structure:

  MHS
    SW (1)
    MAIL
      GATES
        PCBMHS (2)
          IN
          IPARCEL
          OUT
          OPARCEL
          PUBLIC (3)

NOTES:
  (1) This is usually the temporary directory.  This isn't needed and you can
      use any other temporary directory or a RAM disk. This directory is sent
      to both INPOST.EXE and OUTPOST.EXE as the third parameter.

  (2) You should change the workgroup name of PCBMHS to something more unique
      for your BBS.  If you will only be using PCB-MHS between cc:Mail and
      PCBoard, then you can call it anything you like.  This is always the
      workgroup name that you chose upon installation of PCB-MHS.

      This directory is the directory you will give as the address for the BBS'
      cc:Mail postoffice in cc:Mail's Admin program.

           eg.  SMFLINK c:\mhs\mail\gates\pcbmhs

      SMFLINK is used instead of MHSLINK because SMFLINK delivers mail directly
      to the local mailbox, thus not needing MHS.

  (3) This directory is where you will need to copy all of the files found on
      the distribution disk.  After which you will need to run the SETUP
      program.  This directory should also contain all of your log and pointer
      files.

  (4) You must NOT set PCB-MHS' "Allow Local Delivery" option to On/Yes


cc:Mail's Router/Gateway manual also has examples of sample MHS setup's.  Since
you will not be using MHS's Connectivity Manager to execute PCB-MHS, you will
have to create a batch file to run both INPOST.EXE (PCBoard to cc:Mail) and
OUTPOST.EXE (cc:Mail to PCBoard).  You will find an example in the manual.


Upgrading to Version 1.3
------------------------

  Their are minor differences between version 1.3 and previous versions.
  The PCBMHS.CFG configuration file has been renamed to PCB-MHS.CFG.
  There is no longer a need for a message pointer file.
  The other minor visible changes are in the setup program, but they are
  documented in the online help.

