PPoint Reference Guide

for Windows and DOS

FTS Compatible Email System

Reference Guide
Copyright (c) 1998 Harvey Parisien, all rights reserved

Fidonet: 1:249/114
Internet: parisien@alcuf.ca
Web: www.alcuf.ca/parisien

(DRAFT HELP FILE FOR BETA RELEASE)

TOPICS...

                  HOST: TRANSFER MAIL
                  HOST: ACTIVITY REPORT
                  HOST: Repeated File Requests
                  HOST: EXIT

                  MAIL: SELECT MESSAGE AREA
                  MAIL: SELECT MESSAGE
                  MAIL: CHECK FOR YOUR NEW MAIL
                  MAIL: FIND & READ MESSAGES
                  MAIL: EXPORT A MESSAGE
                  MAIL: PRINT A MESSAGE
                  MAIL: PURGE OLD MAIL

                  SETUP: DISPLAY INTERNAL NETWORK INFO
                  SETUP: AUTOMATIC MAINTENANCE
                  SETUP: EDIT AREA ADDRESS/DELETE DAYS
                  SETUP: ADD NEW MESSAGE AREA
                  SETUP: DELETE A MESSAGE AREA
                  SETUP: USER/HOST/MAILER INFO
                  SETUP: ADVANCED SETTINGS
                  SETUP: SETUP REPORT
                  SETUP: EDIT NODELIST

                  INTERNET ADDRESSING
                  FIDONET ADDRESSING FROM INTERNET
                  FAKENET ADDRESSING INFORMATION
                  MULTIPLE NETMAIL AREAS
                  BINKLEY SETUP INFORMATION
                  ADDRESS BOOK AND CARBON COPY MESSAGES
                  NODELIST SETUP INFORMATION
                  HOW TO SEND FILES OR FILE ATTACH NETMAIL
                  MESSAGE ENCRYPTION FEATURES
                  TWIT LIST (INBOUND MESSAGE FILTER)
                  REMAPPING OF THE TO FIELD
                  MISC STUFF



HOST: TRANSFER MAIL


    This connects you to your HOST system (or boss node) to collect new
    mail/files, and send any outstanding mail from your system.  It is not
    necessary to have mail to send in order to connect to your host.  You
    can Poll for mail when ever you wish to see if there is anything
    waiting for you on the host system, or to request or send files.



HOST: ACTIVITY REPORT


    This displays your systems log, which shows details on processing mail
    into and out of PPoint, and information on transfers to your host.



HOST: Repeated File Requests


    This allows you to request files FROM YOUR HOST on every poll.

    This is handy if your host has an updated file continually waiting.

    To test this, request a file called ABOUT.  Usually the host will have
    a file called ABOUT which is a very small text file containing
    information on your host.

    TO REQUEST FILES DIRECTLY from other nodes in your network, you need
    a nodelist.  This is a more traditional way of requesting a file.  You
    send a netmail message to the source node (just use SysOp if you don't
    know his or her name) of the file and put the file to be requested on
    the subject line like this:

    /freq bexe_256.zip

    ... and the file will be requested.  This is often referred to as
    FILE REQUESTING or FREQING.

    Some systems require additional passwording security for file
    requests.  When freqing using a password, the format is:

    /freq filename.ext!password

    (see also: Setup: Edit Nodelist)



HOST: EXIT


    This exits PPoint



MAIL: SELECT MESSAGE AREA


    This displays a list of all the current message areas (or sometimes
    called conferences) on the system.  As PPoint receives new areas, they
    are automatically setup (no need to fuss with configuration files).
    This function allows you to select an area to read mail in.



MAIL: SELECT MESSAGE


    This displays a list of all the current messages in the current
    message area.  This function allows you to select a specific message
    in a specific area to read.



MAIL: CHECK FOR YOUR NEW MAIL


    This searches all messages areas for mail sent to you that have not
    yet been read.

    Once a FIND/SEARCH has been requested, just use the NEXT button to
    read all finds.



MAIL: FIND & READ MESSAGES


    This allows you to search one or all message areas for a match to your
    search text in the message header (the To, From, and Subject fields),
    or complete message.

    Once a FIND/SEARCH has been requested, just use the NEXT button to
    read all finds.



MAIL: EXPORT A MESSAGE


    This allows you to send a message to a disk file of your choice.



MAIL: PRINT A MESSAGE


    This allows you to send a message to the windows printer.



MAIL: PURGE OLD MAIL


    This deletes old messages based on how many days old they are.  Each
    area can be set for a different number of days.  After messages are
    deleted, the system will automatically Pack the Databases.

    Messages that are NEW (ahead of your book mark) will not be deleted.

    Messages that are FROZEN, using Alt-F in the read area, will not be
    deleted.

    (see also: Setup: Automatic Maintenance)
    (see also: Setup: Edit Message Areas/Delete days)



SETUP: DISPLAY INTERNAL NETWORK INFO


    The message display can be toggled to show internal network addressing
    information.  This can be annoying to most users, and is by default
    turned off.

    (see also: Operational Keys in the Reading Area)



SETUP: AUTOMATIC MAINTENANCE


    PPoint can automatically perform it's maintenance after your first
    HOST poll of the day.  This deletes messages after they are over age,
    and packs the database.

    This function will only operate once a day.

    (see also: Mail: Delete old mail)
    (see also: Setup: Edit Message Areas/Delete days)



SETUP: EDIT AREA ADDRESS/DELETE DAYS


    This is where you can edit details on each individual message area.

      AREA DESCRIPTION: General Point Support
         HOST AREA TAG: POINT
    DATABASE FILE NAME: 00000004
           DELETE DAYS: 10
      AREA ORIGIN LINE: OFFLINE Systems
          AREA ADDRESS: 1:249/114.1
     AREA HOST ADDRESS: 1:249/114
    AREA ROUTE ADDRESS: 1:249/114
    USE ON ORIGIN LINE: 1:249/114.1

    The AREA DESCRIPTION is by default the same as the HOST AREA TAG.
    These names are sometimes not as descriptive as you may like, so this
    allows you to rename them.

    The HOST AREA TAG and DATABASE FILE NAME are created by PPoint and
    can not be changed.

    The DELETE DAYS entry is the number of days of mail to be kept when
    PPoint deletes old mail.  The age of your mail is determined by the
    message date, not when it was received.  Messages that are NEW (ahead
    of your book mark) will not be deleted.  Messages that are FROZEN,
    using Alt-F in the read area, will not be deleted.  If set to 0,
    PPoint will remove everything in the area except for messages marked
    as FROZEN, and messages that are below your book mark.  If set to -1,
    PPoint will delete everything in the area no matter what the age or
    status of the messages are, but it will preserve the area setup
    information.

    The ORIGIN LINE is usually the name of your system, or your name.
    This can be edited to whatever you like for each area.

    The AREA ADDRESS defaults to the address you entered in setup under
    User/Host/Mailer Info.

    If you are using multiple HOST systems, you can change each area to
    individually use this address and link to an individual AREA HOST
    ADDRESS and AREA ROUTE ADDRESS as well.  In this case, you will have
    to implement a nodelist with your various alternative Host/Boss nodes
    details in it.

    (see also: Multiple Netmail Areas)

    Finally, the USE ON ORIGIN LINE address has to do with fakenet
    addressing, see help in that area for details.

    CAUTION!!

    Most systems are used for ONE HOST, so be very cautious if you change
    the AREA ADDRESS, AREA HOST ADDRESS, AREA ROUTE ADDRESS, or USE ON
    ORIGIN LINE settings.

    (see also: Mail: Purge old mail)
    (see also: Setup: Automatic Maintenance)
    (see also: Setup: User/Host/Mailer Info)
    (see also: NodeList Setup Information)
    (see also: Setup: Edit Nodelist)
    (see also: FakeNet Addressing Information)



SETUP: ADD NEW MESSAGE AREA


    This is where you can add new areas manually.  In case you want to
    enter a message in an area you don't yet have.  Otherwise, areas
    are automatically added as mail is received, so this is usually
    not required.



SETUP: DELETE A MESSAGE AREA


    This is where you can remove an area, and the associated message
    databases.



SETUP: USER/HOST/MAILER INFO


    This is where you setup your user name, and point addressing.  Your
    host will provide you with the addressing details.

    This is where your configuration file for BinkleyTerm is created or
    updated.  See Binkley Setup Information.



SETUP: ADVANCED SETTINGS


    PPoint has been designed to be as simple as possible to use and
    configure.  However, for more advanced users, and more advanced
    features, we have adopted the Windows style INI file format to
    make future development easier, and to support third party setup
    parameters.

    PPoint.INI is a text file that contains Advanced Settings for PPoint.
    Note the format is KEYWORD=SETTING.  Here are some optional settings.
    Note, lines starting with a ; are comment lines and ignored by the
    program.


    Note: This document only refers to the commands relevent to the 
    Windows version of PPoint.  See DOS manual for other details.

     _ _ _ PPOINT.INI _ _ _


    ; Defines your Internet Browser (or other HTML file reader) for help
    ; files.  Note 8 chr name conventions.  This is user selectable under
    ; the SETUP menu.

    BROWSER=c:\progra~1\intern~1\IEXPLORE.EXE

    ; By default your outbound packet password is the same as your ppoint 
    ; session password.  You can change the outbound packet password as
    ; required using this keyword.

    PKTPWD=MOMMY

    ; Specific outbound packet password, no matter what pktpwd is if
    ; implemented (the 00000010 in the example is the message area
    ; filename - see edit areas).  This is only of interest for users
    ; with multiple boss nodes.

    PKTPWD-00000010=xxx

    ; User definable Binkley.cfg settings.  These keywords will cause new
    ; lines to be added before the PORT setting when binkley.cfg is reset.

    BINKCFG1=
    BINKCFG2=

    ; You can now have different footer files for each message area.  The
    ; default footer.txt will still work with all and any areas that are
    ; not defined specifically as follows.  Under advanced settings define
    ; the following keyword...     format:  areaname_FOOTER=textfile.ext
    ; Files must be in your ppoint directory.  Do not enter drive or path.

    POINTS_FOOTER=HP.TXT
    FS_FOOTER=Flightsm.TXT
    SHAREWRE_FOOTER=share.TXT
    TESTAREA_footer=footer2.txt



SETUP: SETUP REPORT


    PPoint will create a text file report called REPORT.TXT which will
    contain complete information on your PPoint setup.  It will be
    presented to you in your editor for review.  It can be imported into
    a message with your editor for support purposes or printed.



SETUP: EDIT NODELIST


    PPoint will compile a nodelist version 6 from a text file that
    contains manually entered listings as follows.  Third party tools
    can create other versions and handle other nodelist management tasks.

         zone:net/node , system , phone , password , baud , cost

    Selecting Edit Nodelist causes PPoint to place your raw nodelist text
    file in your editor for editing or reviewing.  When you exit, PPoint
    will compile the data into a VERSION 6 type nodelist. This is the
    default nodelist binkley requires if you use a nodelist.

    Here's a sample raw nodelist text file...

    ;------------------------------------------
    ; Private Nodelist Text for use with PPOINT
    ;------------------------------------------

    ;Entries must be in ZONE order, ie zone 1's first, zone 2's next.

    ;zone:net/node,system,phone,password,baud,cost

    ; All lines in this text file that start with a ; are just comment
    ; lines and are ignored by all processors.  Feel free to make any
    ; notes in this file as long as you start the line with a ;.

    ; zone:net/node - this is a standard fidonet address
    ;        system - this is the system name you are listing
    ;         phone - this is the exact phone number for the system you
    ;                 are listing including a 1 or area code if it's long
    ;                 distance.
    ;      password - this is the session password which must be
    ;                 prearranged with this system you are listing.  This
    ;                 can be left blank, but the commas are still required
    ;                 ie...
    ;                 1:249/114, Harvey Parisien,  1-613-555-1212,,9600,30
    ;          baud - this is the baud of the system you are listing
    ;          cost - this is an estimated cost per minute in cents to call
    ;                 the system you are listing.  If the listing is local,
    ;                 use a 0 for cost.
    ;
    ;zone:net/node,system,phone,password,baud,cost

    ;
    1:128/77,  Preston Smith,    1-719-555-1212,piano,9600,0
    1:249/114, Harvey Parisien,  1-613-555-1212,,9600,30


    (see also: Binkley Setup Information)
    (see also: NodeList Setup Information)



INTERNET ADDRESSING


    To send a message to someone on the INTERNET, just simply use their
    address in the To: field, and send the message netmail to a valid
    INTERNET/FIDONET Gateway address.

    For more information on FIDONET/Gateways, ask your local sysop.

    (see also: FIDONET ADDRESSING FROM INTERNET)



FIDONET ADDRESSING FROM INTERNET


    The address of a FIDONET Node looks like this: 1:107/309.0. Usually
    the .0 is left off, but they are there by default. That address can be
    translated as "Zone 1, Net 107, FidoNode 309, Point 0." or
    f309.n107.z1.fidonet.org - the "Fully Qualified Domain Name" of a
    FidoNode.

    Another example is 1:107/309.2 which would be written as
    p2.f309.n107.z1.fidonet.org (since there is a point number other than
    0, we have to specify it). 

    Note that FIDONET systems usually use a "Firstname Lastname" logon.
    You will need to express that as  First.Last, using a DOT in place of
    the SPACE.

          Addresses can be interpreted as:

          First.Last@[p###.]f###.n###.z#.fidonet.org.       where:
            ^     ^     ^     ^    ^   ^   ^      ^
            |     |     |     |    |   |   `------`--- domain
            |     |     |     |    |   `---- Zone number (IMPORTANT)
            |     |     |     |    `-------- Net number
            |     |     |     `------------- Node number
            |     |     `------------------- Point number (optional)
            |     `------------------ User's LAST Name
            `------------------------ User's FIRST Name

                The Point number need only be used if non-zero.

    Example:

    William Bradley at 1:249/114.8 in FIDONET is...

                  william.bradley@p8.f114.n249.z1.fidonet.org

    ... if addressed from INTERNET.




FAKENET ADDRESSING INFORMATION


    Older FidoNet compatible systems may require you to use 3d addressing
    as opposed to the standard 4d addressing.  To accommodate this, PPoint
    supports FakeNet addressing.

    4d means an address has 4 parameters ie ZONE:NET/NODE.POINT.
    3d means an address has 3 parameters ie ZONE:NET/NODE.

    For example, you may have a HOST with an address of 1:249/114, and you
    are to use 1:24914/2 as a fake address.  Your HOST's system will then
    translate your incoming and outgoing mail from a fake address of
    1:24914/2 to a real world address of 1:249/114.2 since it's system can
    not handle the fourth dimension in the address, being the point
    number.

    If your HOST requires that you use a fakenet address, this means it
    will not have the proper .x at the end of your address.  To make your
    message origin lines display exactly what you want, go to the setup
    menu and Edit Area Address information.  Edit the USE ON ORIGIN line.

      AREA DESCRIPTION: General Point Support
         HOST AREA TAG: POINT
    DATABASE FILE NAME: 00000004
           DELETE DAYS: 10
      AREA ORIGIN LINE: OFFLINE Systems
          AREA ADDRESS: 1:24914/1
     AREA HOST ADDRESS: 1:249/114
    AREA ROUTE ADDRESS: 1:249/114
    USE ON ORIGIN LINE: 1:249/114.1

    The last line is the origin address that will show in your messages.

    (see also: Edit AREA Address/Delete days)



MULTIPLE NETMAIL AREAS


    Basically, you could just ask your other network hosts to send you a
    netmail message at the address you want, and then poll that boss.  The
    area will be automatically setup correctly.

    To do this, just send a netmail message (from the default or any other
    existing netmail area) to each other address you wish to have a
    netmail area for. Ask that site to send you a netmail message at your
    new netmail address relating to that site (in other words not just a
    reply to your current netmail message).  PPoint will automatically
    handle the setup for each new netmail area(s) when the return mail
    comes in.

    OR, manually ADD an area using this naming format (NETMAIL_net_node):

    NETMAIL_249_114

    This would represent a netmail address for a host being 249/114. This
    could be any zone (I didn't think there would be a conflict between 2
    address exactly the same with different zones).

    Your default or main NETMAIL area is related to your default or main
    address as setup in your user/info details.  That area doesn't need
    the extended info in the name, and should already be setup in any
    case. Don't forget to add your alternate boss/host address info to
    your node list.

    (see also: NodeList Setup Information)
    (see also: Setup: Edit Nodelist)



BINKLEY SETUP INFORMATION


    All setup information related to BinkleyTerm is found in the file on
    your PPoint directory called BINKLEY.CFG which is automatically
    created by PPoint.

    Some of the settings in Binkley.cfg CAN NOT be changed except by
    PPoint in order to insure the settings are exactly the same as
    contained in PPoint's setup files.  These are identified in the
    Binkley.cfg file, and referred to here as part 1 of your Binkley.cfg
    file.

    However, there are times when you might need to change some of the
    settings for example a common one is your modem INIT string.  For more
    details on modifying your Binkley.cfg file, refer to the documentation
    provided with that system.

    In order to allow you to change some of the settings, PPoint allows a
    file called BINKLEY.ADD to be changed by the user.  Binkley.add will
    contain the contents to be included as part 2 of your Binkley.cfg
    file when PPoint updates it.

    If you have special configuration requirements, use your text editor
    to edit Binkley.add and change or add as necessary, then update your
    Binkley.cfg file.

    To update your Binkley.cfg file, choose "User/Host/Mailer Info" on the
    Setup Menu and then press SAVE.  This rebuilds your Binkley.cfg file.

    (see also: Setup: User/Host/Mailer Info)
    (see also: NodeList Setup Information)
    (see also: Setup: Edit Nodelist)



ADDRESS BOOK AND CARBON COPY MESSAGES


    OPTIONAL ADDRESS BOOK:

    If you have an address book in place (the system creates this for you)
    it can be accessed for NETMAIL or ECHOMAIL by pressing F4 when you are
    ENTERING a message, placing text in the TO: field.  Your address book
    is built by the system.  Every time you enter a NETMAIL message, it
    prompts you as to whether or not you would like to add the current
    entry to the address book.  It will only prompt you for entries that
    do not currently exist.  This way you build an address book while you
    use the system, as opposed to sitting down and typing in 50 names.

    The address book is stored in a text file called PPoint.NOD.  You can
    edit this file using a plain text editor.  The format at one time was
    a 55 character line for each entry.  Those entries will still be
    recognized by PPoint.  Newer entries will be in a simple name, address
    format.  You can also optionally add a subject line with this format.

    name,address{,subj}


    OPTIONAL CARBON COPIES:

    To send a message to several people you can have a continuous list of
    names in a text file in the format: first last,zone:net/node{.point}.

    For example...

    Bill Cassidy, 1:249/1
    Harvey Parisien,1:249/114.7
    Scott Dudley, 1:249/106
    Don Laverdure, 1:249/124.2

    Entering CC:filename.ext in the TO: field causes carbon copies to be
    sent to all people/addresses in your list.

    Advanced use...

    The CC:FILENAME.EXT feature described above, can also be listed
    in your address book (PPOINT.NOD) by adding the CC:+FILENAME.EXT
    and the , which does not require an address after it.  Example:

    CC:FILENAME.EXT,

    Another example shows a list file with a subject line:

    CC:ZENITH.cc1,,Zenith Marketing Group
    CC:ZENITH.cc2,,Zenith Administration Group

    (see also: How to Send Files or File Attach Netmail)



NODELIST SETUP INFORMATION


    To send netmail directly to other nodes or directly to other networks,
    you will need a nodelist.  By default, PPoint is designed to route all
    mail via your host.  However, if you need a more advanced setup, you
    need a nodelist.  To compile a nodelist, look for a nodelist manager
    like XLAXNODE or QNODE.  For a SMALL simple nodelist, PPoint has an
    option under the Setup menu called Edit Nodelist.  This works just
    fine for smaller nodelist requirements.

    (see also: Setup: Edit Nodelist)
    (see also: Setup: User/Host/Mailer Info)
    (see also: Binkley Setup Information)



HOW TO SEND FILES OR FILE ATTACH NETMAIL


    Request/Send Files using a message

    To send (attach) or request (freq) a file, enter a netmail message to
    the SysOp (just use SysOp if you don't know his or her name) and on
    the subject line, put...

    /send c:\trash\oldstuff.lzh
    ... and the file will be sent.

               -or-

    /freq bexe_256.zip
    ... and the file will be requested.



MESSAGE ENCRYPTION FEATURES


    It is important to understand that FIDONET and some other networks do
    not allow encrypted messages.  This feature was implemented for use in
    private networks where encrypted message are permitted.  Also for
    situations where "local" (same net/node) points can send encrypted
    messages to each other, working within their local boss' system only.

    In order for this feature to work, your boss node must have the
    ability to route file attaches.  Many modern processors like SQUISH
    handle this with ease.

    (PPoint uses the fido packet format for the actual message and an
    empty body, putting the encrypted message in a file attached to the
    message.  This is virtually seamless to the user, but I thought many
    of you would like to know the mechanics behind the feature.)

    The encryption routine was written by Cresent Software of Connecticut,
    USA, and is a medium secure algorithm.  It is seeded by your password, 
    so even I (or Cresent) as the author can not decode your mail.  For 
    optimum encryption security see note at end of this section.  While this
    is a seamless and simple to use system, more secure systems are available.

    The way it works is simple.  When sending a message to someone that
    you have ascertained to be a network legal recipient of an encrypted
    message, you do the following:

    1. Both users must use PPoint.

    2. You must agree on a mutual password to be used between the two of
       you for this purpose.

    3. When you enter a message, put /ENC on the subject line.  It is ok
       to put more than the /ENC control on the subject ie you might want
       to have a subject line line: /ENC Meeting Agenda.  As long as the
       first 4 characters are /ENC it will work.  This is not case
       sensitive, ie /enc or /ENC are both ok.

    4. When PPoint does a host transfer, and the message is processed from
       your message database to an outbound packet, you will be prompted
       for the recipients password.  This will only happen the first time
       you send encrypted mail to a specific person.  It won't prompt you
       in the future for other encrypted messages, so the process becomes
       totally transparent to the users.

    5. When your recipient receives mail on his/her PPoint system, they
       will be prompted for the senders password.  This will only happen
       the first time they receive mail from you.  It won't prompt you in
       the future for other encrypted messages, so the process becomes
       totally transparent to the users.

    This was developed for users on private networks who needed maximum
    mail security.  This way mail sitting on a dedicated server remains
    totally secure.  Once the mail is received into your personal PPoint
    system, it is decrypted.  Likewise, when you reply to a message that
    was originally encrypted, the /ENC control marker remains on the
    subject line, so the rest of the conversation, via ongoing replies,
    remains encrypted. The concept is to keep mail encrypted while in
    transit.