PC Online 1999 April/PCO0499.ISO/filesbbs/os2/irexp117.arj/IREXP117.ZIP/REX.DOC

Text File | 1999-01-11 | 255.3 KB | 6,246 lines

      Internet Rex v1.16 Documentation                   TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────


      Section 1: Introduction .......................................... 2
        1.1  Finding the latest version ................................ 2
        1.2  Copyright information ..................................... 3
        1.3  Acknowledgements .......................................... 4
        1.4  Registration .............................................. 5
        1.5  Contacting the Author ..................................... 6

      Section 2: Quick Setup Guide ..................................... 7

      Section 3: Configuring Internet Rex .............................. 8
        3.1  General Information ....................................... 8
          3.1.1  Sysop Name ............................................ 8
          3.1.2  System Name ........................................... 8
          3.1.3  User level ............................................ 8
          3.1.4  Registration String and Registration Key .............. 8
        3.2  Rex's Behaviour ........................................... 8
          3.2.1  Configure appearance .................................. 9
            3.2.1.1  Use upper ASCII ................................... 9
            3.2.1.2  Colour scheme ..................................... 9
            3.2.1.3  Main screen background ............................ 9
            3.2.1.4  Main screen box colour ............................ 9
            3.2.1.5  Menu normal colour ............................... 10
            3.2.1.6  Menu choice colour ............................... 10
            3.2.1.7  Value colour ..................................... 10
            3.2.1.8  String edit colour ............................... 10
            3.2.1.9  Help keyword ..................................... 10
            3.2.1.10  Highlighted help keyword ........................ 10
            3.2.1.11  String edit background character (upper ASCII) .. 10
            3.2.1.12  String edit background character (lower ASCII) .. 11
            3.2.1.13  Background character (upper ASCII) .............. 11
            3.2.1.14  Background character (lower ASCII) .............. 11
            3.2.1.15  Window border foreground colour ................. 11
            3.2.1.16  Window background colour ........................ 11
            3.2.1.17  Close window box colour ......................... 11
            3.2.1.18  Disabled menu choice colour ..................... 11
          3.2.2  Graphical Tossing .................................... 12
          3.2.3  With Progress Bar .................................... 12
          3.2.4  Echo log to screen ................................... 12
          3.2.5  Processor Friendliness ............................... 12
          3.2.6  Kill Empty Netmail ................................... 12
          3.2.7  Send Crash/Immediate Mail ............................ 13
          3.2.8  Send Mail on Hold .................................... 13
          3.2.9  Send File REQuests (FREQs) ........................... 13
          3.2.10  Honour Return Receipt Requests (RRQs) ............... 13
          3.2.11  Honour FREQs ........................................ 13
          3.2.12  TransX mode ......................................... 13
          3.2.13  Inbound file case ................................... 14
          3.2.14  Swap to EMS/disk .................................... 14
        3.3  Files, Paths and Programs ................................ 14
          3.3.1  Drive Mappings ....................................... 14

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden           i
      Internet Rex v1.16 Documentation                   TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

            3.3.1.1  Map drives to drives ............................. 15
              3.3.1.1.1  Default Map .................................. 15
              3.3.1.1.2  Edit Mapping ................................. 15
                3.3.1.1.2.1  Map Label ................................ 15
                3.3.1.1.2.2  Edit Mapping ............................. 15
            3.3.1.2  Map drives to directories ........................ 15
          3.3.2  Internet Rex files and paths ......................... 16
            3.3.2.1  Log Filename ..................................... 16
            3.3.2.2  Temporary File Directory ......................... 16
            3.3.2.3  Queue Directory .................................. 16
            3.3.2.4  Holding Directory ................................ 16
            3.3.2.5  Semaphore Directory .............................. 16
            3.3.2.6  Received Mail Semaphore .......................... 17
            3.3.2.7  TransX Mail Semaphore ............................ 17
            3.3.2.8  Run BETWEEN.BAT/.CMD ............................. 17
            3.3.2.9  Always Run BETWEEN.BAT ........................... 17
          3.3.3  Frontend Mailer Setup ................................ 17
            3.3.3.1  Mailer Type ...................................... 18
            3.3.3.2  Netmail Directory ................................ 18
            3.3.3.3  Inbound Directory ................................ 18
            3.3.3.4  Inbound files directory .......................... 18
            3.3.3.5  Secure Inbound Directory ......................... 19
            3.3.3.6  Inbound mail directory ........................... 19
            3.3.3.7  Semaphore Directory .............................. 19
            3.3.3.8  Inbound TIC directory ............................ 19
            3.3.3.9  Configure Multinode .............................. 20
              3.3.3.9.1  Enable Multinode Support ..................... 20
              3.3.3.9.2  Session Semaphore Check ...................... 20
              3.3.3.9.3  Wait to Clear ................................ 20
            3.3.3.10  Outbound Directory .............................. 20
            3.3.3.11  Outbound Queue .................................. 21
            3.3.3.12  Filebox Directory ............................... 21
            3.3.3.13  Zones Directory ................................. 21
            3.3.3.14  FIDOQUE.DAT path ................................ 21
            3.3.3.15  QQUEUE.DAT path ................................. 21
            3.3.3.16  Packet path ..................................... 21
            3.3.3.17  FILQUEUE.FD path ................................ 22
            3.3.3.18  Long Fileboxes .................................. 22
            3.3.3.19  Default path .................................... 22
            3.3.3.20  Arcmail path .................................... 22
            3.3.3.21  Binkley Outbound ................................ 22
          3.3.4  File REQuest Setup ................................... 23
            3.3.4.1  Alias File ....................................... 23
            3.3.4.2  Secure Alias File ................................ 23
            3.3.4.3  Directories File ................................. 23
            3.3.4.4  Secure Directories File .......................... 23
            3.3.4.5  Access file ...................................... 24
            3.3.4.6  FREQ Not Found Notice ............................ 24
            3.3.4.7  Delete FREQ Messages ............................. 24
            3.3.4.8  Wildcard FREQs ................................... 25
            3.3.4.9  Configure FREQ Limits ............................ 25

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          ii
      Internet Rex v1.16 Documentation                   TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

            3.3.4.10  Process email FREQs ............................. 25
              3.3.4.10.1  Email FREQs ................................. 25
            3.3.4.11  Matching only through ........................... 27
            3.3.4.12  All messages through ............................ 27
            3.3.4.13  Default encoding ................................ 27
            3.3.4.14  Default chunk size .............................. 27
          3.3.5  TransX Setup ......................................... 27
            3.3.5.1  Send TransX Mail ................................. 28
            3.3.5.2  Send mail via .................................... 28
            3.3.5.3  Receive TransX Mail .............................. 28
            3.3.5.4  Receive mail via ................................. 28
            3.3.5.5  TransX SMTP\In Path .............................. 28
            3.3.5.6  TransX SMTP\Out Path ............................. 28
            3.3.5.7  TransX Robot Name ................................ 28
          3.3.6  Compression Programs ................................. 29
            3.3.6.1  Tag .............................................. 29
            3.3.6.2  Command Line ..................................... 29
            3.3.6.3  List Character ................................... 29
          3.3.7  Decompression Programs ............................... 30
        3.4  Connecting to the Net .................................... 30
        3.5  Email Setup .............................................. 31
          3.5.1  Configure email addresses ............................ 31
            3.5.1.1  Address ID ....................................... 31
            3.5.1.2  Username and Domain Name ......................... 31
            3.5.1.3  Mail Spool Type .................................. 32
              3.5.1.3.1  Configure .................................... 32
                3.5.1.3.1.1  POP3/SMTP setup .......................... 32
                  3.5.1.3.1.1.1  SMTP Host ............................ 32
                  3.5.1.3.1.1.2  POP3 Host ............................ 33
                  3.5.1.3.1.1.3  POP3 Username ........................ 33
                  3.5.1.3.1.1.4  POP3 Password ........................ 33
                  3.5.1.3.1.1.5  Use APOP ............................. 33
                  3.5.1.3.1.1.6  Refetch Mail ......................... 33
                  3.5.1.3.1.1.7  POP3 Timelimit ....................... 34
                  3.5.1.3.1.1.8  Synch Every... ....................... 34
                3.5.1.3.1.2  UUCP Setup ............................... 34
                  3.5.1.3.1.2.1  UUCP Path ............................ 34
                  3.5.1.3.1.2.2  Site Name ............................ 34
                  3.5.1.3.1.2.3  Host Name ............................ 34
                  3.5.1.3.1.2.4  UUCP Grade ........................... 34
                  3.5.1.3.1.2.5  Spool Type ........................... 35
                3.5.1.3.1.3  Gateway / With Packet Setup .............. 35
                  3.5.1.3.1.3.1  Gateway's address .................... 35
                  3.5.1.3.1.3.2  Message Flags ........................ 35
                  3.5.1.3.1.3.3  Use UUCP Addressing .................. 35
                  3.5.1.3.1.3.4  Packet Directory ..................... 35
                  3.5.1.3.1.3.5  Packet password ...................... 36
                3.5.1.3.1.4  KA9Q Setup ............................... 36
                  3.5.1.3.1.4.1  SMTP Inbound Path .................... 36
                  3.5.1.3.1.4.2  SMTP Outbound Path ................... 36
                3.5.1.3.1.5  PMMail setup ............................. 36

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden         iii
      Internet Rex v1.16 Documentation                   TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

                  3.5.1.3.1.5.1  PMMail inbound ....................... 36
                  3.5.1.3.1.5.2  PMMail outbound ...................... 36
                3.5.1.3.1.6  PostRoad mailer setup .................... 36
                  3.5.1.3.1.6.1  Postroad inbound ..................... 36
                  3.5.1.3.1.6.2  Postroad outbound .................... 37
                3.5.1.3.1.7  Soup/Yarn setup .......................... 37
                  3.5.1.3.1.7.1  Queue path ........................... 37
                3.5.1.3.1.8  Eudora setup ............................. 37
                  3.5.1.3.1.8.1  Queue path ........................... 37
                3.5.1.3.1.9  MR/2 Ice ................................. 37
                  3.5.1.3.1.9.1  Queue path ........................... 37
                3.5.1.3.1.10  Nettamer setup .......................... 37
                  3.5.1.3.1.10.1  Queue path .......................... 37
              3.5.1.3.2  Use for outbound mail ........................ 38
              3.5.1.3.3  Use for inbound mail ......................... 38
              3.5.1.3.4  Messages downloaded .......................... 38
              3.5.1.3.5  Stray messages from... ....................... 38
          3.5.2  Time Zone ............................................ 38
          3.5.3  Gateway Address ...................................... 39
          3.5.4  Gate mail via ........................................ 39
          3.5.5  Break lines at ....................................... 39
        3.6  FTP Setup ................................................ 39
          3.6.1  Passive Mode FTP ..................................... 39
          3.6.2  Lock Timeout ......................................... 39
          3.6.3  Restarts ............................................. 40
        3.7  Address Manager .......................................... 40
          3.7.1  System Addresses ..................................... 40
            3.7.1.1  Main Address ..................................... 40
            3.7.1.2  System AKAs ...................................... 40
          3.7.2  Zone Matching ........................................ 40
          3.7.3  Domains .............................................. 41
        3.8  Connection Defaults ...................................... 41
          3.8.1  Maximum Resends ...................................... 41
          3.8.2  Dupe Protection Days ................................. 42
          3.8.3  Default Send Acknowledgements ........................ 42
          3.8.4  Dupe protection on all links ......................... 42
          3.8.5  Default Resend Delay ................................. 42
          3.8.6  Partial Purge Delay .................................. 43
          3.8.7  Purge Known Partials ................................. 43
        3.9  Node Manager ............................................. 43
          3.9.1  Sysop's Name ......................................... 43
          3.9.2  System Address ....................................... 43
          3.9.3  Routing Information .................................. 43
          3.9.4  Use AKA .............................................. 44
          3.9.5  Node Active .......................................... 44
          3.9.6  Mailbox Directory .................................... 44
          3.9.7  Outbound Messages .................................... 45
            3.9.7.1  Don't Toss Outbound .............................. 45
            3.9.7.2  Toss to Mail ..................................... 45
              3.9.7.2.1  Transport Method ............................. 45
              3.9.7.2.2  Encoding Method to Use ....................... 46

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          iv
      Internet Rex v1.16 Documentation                   TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

              3.9.7.2.3  Email Address ................................ 47
              3.9.7.2.4  Subject ...................................... 47
              3.9.7.2.5  Message Length / Chunk Size .................. 47
              3.9.7.2.6  Session password ............................. 48
            3.9.7.3  Toss to Directory ................................ 48
              3.9.7.3.1  Destination .................................. 48
              3.9.7.3.2  Check for Locks .............................. 48
              3.9.7.3.3  Lock Filename(s) ............................. 48
              3.9.7.3.4  Wait to Clear ................................ 48
              3.9.7.3.5  Create Locks ................................. 49
              3.9.7.3.6  Lock Filename ................................ 49
            3.9.7.4  Toss to FTP Site ................................. 49
              3.9.7.4.1  Site Name .................................... 49
              3.9.7.4.2  Username ..................................... 49
              3.9.7.4.3  Password ..................................... 49
              3.9.7.4.4  Site's Hours ................................. 49
              3.9.7.4.5  Lock file size ............................... 50
              3.9.7.4.6  Unique storage ............................... 50
              3.9.7.4.7  Filename case ................................ 50
              3.9.7.4.8  Script Type .................................. 50
              3.9.7.4.9  Scripting .................................... 51
              3.9.7.4.10  Destination Directory ....................... 51
              3.9.7.4.11  Check for Locks ............................. 51
              3.9.7.4.12  Lock Filename(s) ............................ 51
              3.9.7.4.13  Wait to Clear ............................... 52
              3.9.7.4.14  Create Locks ................................ 52
              3.9.7.4.15  Lock Filename ............................... 52
            3.9.7.5  Toss to a BinkP site ............................. 52
              3.9.7.5.1  Site's address ............................... 52
              3.9.7.5.2  Site's hours ................................. 52
              3.9.7.5.3  Connection timeout ........................... 53
              3.9.7.5.4  Block size ................................... 53
              3.9.7.5.5  Default domain ............................... 53
          3.9.8  Inbound Messages ..................................... 53
            3.9.8.1  Don't Toss Inbound ............................... 53
            3.9.8.2  Toss From Directory .............................. 53
              3.9.8.2.1  Source ....................................... 53
              3.9.8.2.2  Check for Locks .............................. 54
              3.9.8.2.3  Lock Filename(s) ............................. 54
              3.9.8.2.4  Wait to Clear ................................ 54
              3.9.8.2.5  Create Locks ................................. 54
              3.9.8.2.6  Lock Filename ................................ 54
            3.9.8.3  Toss From Mail ................................... 54
              3.9.8.3.1  Configure Matching Information ............... 55
              3.9.8.3.2  Post to Netmail .............................. 56
              3.9.8.3.3  Delete Empty Messages ........................ 56
              3.9.8.3.4  Delete File Attach Messages .................. 56
              3.9.8.3.5  Strip Message Headers ........................ 57
            3.9.8.4  Toss From FTP Site ............................... 57
              3.9.8.4.1  Site Name .................................... 57
              3.9.8.4.2  Username ..................................... 57

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden           v
      Internet Rex v1.16 Documentation                   TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

              3.9.8.4.3  Password ..................................... 57
              3.9.8.4.4  Site's Hours ................................. 57
              3.9.8.4.5  Lock file size ............................... 58
              3.9.8.4.6  Auto-delete .................................. 58
              3.9.8.4.7  Script Type .................................. 58
              3.9.8.4.8  Scripting .................................... 58
            3.9.8.5  Toss from a BinkP site ........................... 59
          3.9.9  File Bundling ........................................ 59
            3.9.9.1  Auto-extract Incoming ............................ 59
            3.9.9.2  Bundle Outgoing Files ............................ 60
            3.9.9.3  Archive Name ..................................... 60
            3.9.9.4  Max size ......................................... 60
            3.9.9.5  Archiver To Use .................................. 61
          3.9.10  Connection Information .............................. 61
            3.9.10.1  Packet level password ........................... 61
            3.9.10.2  Encryption password ............................. 61
            3.9.10.3  Encryption Method ............................... 61
            3.9.10.4  Session password ................................ 62
            3.9.10.5  Secure Connection ............................... 62
            3.9.10.6  Send Acknowledgements ........................... 62
            3.9.10.7  Resend Request Delay ............................ 63
            3.9.10.8  Accept Resend Requests .......................... 63
            3.9.10.9  Purge Delay ..................................... 63
            3.9.10.10  Auto-resend Unacked Mail ....................... 63
          3.9.11  Node's Statistics ................................... 63
        3.10  Queue Editor ............................................ 64
          3.10.1  Packet Level - Outbound Packet ...................... 65
          3.10.2  Packet Level - Inbound Packet ....................... 66
          3.10.3  File Level .......................................... 66
          3.10.4  Contents List Overview .............................. 68
          3.10.5  Partial Message Contents List ....................... 68
        3.11  Logging options ......................................... 68
          3.11.1  Fatal Errors ........................................ 69
          3.11.2  Other Errors ........................................ 69
          3.11.3  Files Sent/Received ................................. 69
          3.11.4  Acks/Receipts ....................................... 69
          3.11.5  General Messages .................................... 69
          3.11.6  Trivial Messsages ................................... 69
          3.11.7  Debug Messages ...................................... 69
          3.11.8  Logfile Max. Size ................................... 70
          3.11.9  Autotrim logfile .................................... 70
          3.11.10  Logging mode ....................................... 70

      Section 4: DOS Internet Setup ................................... 71
        4.1  Init String .............................................. 71
        4.2  COM Port ................................................. 71
        4.3  Address .................................................. 72
        4.4  IRQ ...................................................... 72
        4.5  Baud ..................................................... 72
        4.6  Vector ................................................... 72
        4.7  IP address ............................................... 72

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          vi
      Internet Rex v1.16 Documentation                   TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

        4.8  Network Mask ............................................. 73
        4.9  Name Server .............................................. 73
        4.10  Login Name .............................................. 73
        4.11  Password ................................................ 73
        4.12  Phone Number ............................................ 73
        4.13  Dial Attempts ........................................... 74
        4.14  Socket Timeout .......................................... 74
        4.15  Data Timeout ............................................ 74
        4.16  MSS ..................................................... 74
        4.17  Use BootP ............................................... 75

      Section 5: OS/2 Connection Script Setup ......................... 76
        5.1  Inactivity Timeout ....................................... 76
        5.2  Socket timeout ........................................... 76
        5.3  COM Port ................................................. 77
        5.4  Baud Rate ................................................ 77
        5.5  Init string .............................................. 77
        5.6  Redials .................................................. 77
        5.7  Username ................................................. 77
        5.8  Password ................................................. 77
        5.9  SLIP or PPP .............................................. 77
        5.10  Your IP Address ......................................... 78
        5.11  Provider's IP Address ................................... 78

      Section 6: Win95 Dialup Connections ............................. 79
        6.1  Socket timeout ........................................... 79
        6.2  Dialup Networking ........................................ 79
        6.3  Auto Dial ................................................ 79
        6.4  Auto Hangup .............................................. 79
        6.5  Redials .................................................. 80
        6.6  Inactivity Timeout ....................................... 80
        6.7  Login Name ............................................... 80
        6.8  Password ................................................. 80
        6.9  Connection ............................................... 80

      Section 7: Commandline Options .................................. 81
        7.1  Rex Commandline Options .................................. 81
        7.2  Rexcfg Commandline Options ............................... 85

      Section 8: Terms ................................................ 87
        8.1  Full Name or Internet Address ............................ 87
        8.2  File Locking (FTP) ....................................... 87
        8.3  Compatability in Rex ..................................... 88
        8.4  Acks and Receipts ........................................ 88
        8.5  Full Paths, etc. ......................................... 89
        8.6  Standards ................................................ 89
          8.6.1  Internet RFC standards ............................... 89
          8.6.2  Fidonet Standards .................................... 90
          8.6.3  Miscellaneous Standards .............................. 90

      Section 9: Encoding Methods ..................................... 92

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden         vii
      Internet Rex v1.16 Documentation                   TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

        9.1  Base 64 (MIME encoding) .................................. 92
        9.2  UUencoding ............................................... 92
        9.3  XXencoding ............................................... 92
        9.4  FIDS ..................................................... 93
        9.5  TransX ................................................... 93

      Section 10: FTP Commands ........................................ 94

      Section 11: Email Forwarding/Personal Gateway .................. 100

      Section 12: CC email file attaches ............................. 101

      Section 13: Troubleshooting .................................... 102
        13.1  FIDS Messages and Reliable Connections ................. 102
        13.2  ViaMail ................................................ 102





































      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden        viii






















                                  Internet Rex

                                Technical manual

            Copyright (c) 1997-1999 Khan Software and Charles Cruden

                                  version 1.16


      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                           Section 1: INTRODUCTION


      Welcome to Internet Rex!

      So what is Internet Rex, you're asking?

      Internet Rex is a close puppy friend of Fido's.  Fido was designed
      to send mail over phone lines using a modem - Rex is designed to
      send mail over the Internet, using whatever methods are available to
      him.  It's meant to be an easy to use, consolidated method to
      transport mail via email or FTP.  Rex supports the following useful
      features:

        o  The only program currently supporting email, BinkP and FTP
        o  The ability to toss mail to a directory, for use on FTP
           servers
        o  Transport methods can be transparently combined: you can send
           files to a remote site using email, but receive mail via FTP
        o  Uses Internet standard encoding methods (MIME, UUencoding,
           XXencoding) for mail: ensures compatibility with other
           programs
        o  Fully MIME compliant: supports multi-part messages, and
           multiple attached files
        o  Fault tolerant file transmission: a system of manifests and
           receipts ensures files are sent and received once and only
           once
        o  Secure links use encryption to ensure that your mail is read
           only by the intended receiver and no one else
        o  Fully compatible with other FTN to Internet transport
           programs, including Fido2Int, TransX, GIGO, WaterGate and many
           others
        o  Native support for DOS, OS/2, Win95/98/NT and Linux operating
           systems


                       1.1: Finding the latest version


      The most recent version of Internet Rex can be obtained in any of
      the following ways:

      WWW: go to
        http://plaza.v-wave.com/InternetRex
      or
        http://filepile.com (search for Internet Rex)

      FTP: go to the following URL
        ftp://xanadu.v-wave.com/irex



      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden           2
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      File request:
        Request REXW, REXD, REXE, REXP or REXL (for either the Windows,
        DOS 16-bit, DOS 32-bit, OS/2 or Linux version) from any of the
        following addresses:
          1:342/806
          1:342/820

      Email file request:
        Send mail to [e-mail] with the subject FREQ.  In the
        body of the message, put the line
          FREQ <version>
        where <version> is replaced with REXW, REXD, REXE, REXP or REXL
        depending on which version of Internet Rex you would like (Windows,
        DOS 16-bit, DOS 32-bit, OS/2 or Linux).

      Download:
        The most recent version will be available online at the Internet
        Rex support HQ BBS, Xanadu.  The phone numbers are
           1-403-439-8364
        or 1-403-433-3560
        Both lines are 33.6kbps lines.  The BBS can also be reached via
        telnet at xanadu.v-wave.com.


                          1.2: Copyright information


      Internet Rex is copyright (1997-1999) of Khan Software and Charles
      Cruden.  It is distributed with one restriction: the number of nodes
      configurable.  Permission is granted to use Internet Rex for a
      period of 30 days without restriction.  After that time you must
      either register the program or remove it from your system.

      To register Internet Rex, look for REGISTER.ZIP in your original
      Internet Rex archive and use the file appropriate for your country.

      Internet Rex is provided 'as is', with no warranty expressed or
      implied.  The only thing Rex is guaranteed to do is occupy disk
      space.  No technical support is guaranteed, though I will do my best
      to provide help when possible.  See section x.x, contacting the
      author.

      Under no circumstances will Charles Cruden or Khan Software be held
      responsible for damage caused by running Internet Rex or its
      associated problems.  Any loss, financial or otherwise that may have
      been incurred while running, or as a result of not being able to
      run, Internet Rex is the sole responsibility of the person using the
      software.

      Users who chose to register Internet Rex will receive a serial
      number and registration key which are unique to their system.  Under

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden           3
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      no circumstances are these to be distributed to anyone other than
      the user they were originally intended for.  Use of these keys on a
      system other than the original registrand's is expressly prohibited.
      Failure to comply with these limitations may result in the
      registration being revoked.

      Internet Rex and its associated programs may not be hacked, reverse
      engineered, run-time modified, etc.  Distribution of patches, key
      generating or bypassing routines or any similar products is
      expressly prohibited and will result in the revoking of registration
      keys for people caught doing so.  It may also result in legal
      action.

      If you wish to withdraw from the conditions of this agreement after
      registering Internet Rex, you may do so by informing the person
      with whom you registered Internet Rex.  In so doing, the registration
      code you received will be invalid for all future versions of Internet
      Rex; you also forfeit the fees for the registration code.

      Other programs mentioned in this help guide are the copyright of
      their respective owners.


                            1.3: Acknowledgements


      The Blowfish encryption code in Internet Rex is written and
      copyright Eric Young ([e-mail]).

      The DOS version of Internet Rex uses the WATTCP TCP/IP stack for
      packet drivers developed by Erick Engelke.  More details on this
      package can be found at the WATTCP homepage at
      http://dark.uwaterloo.ca/wattcp.html.

      The DOS version of Internet Rex also includes a PPP packet driver
      developed by Antonio Lopez Molero.  More information about this
      package can be obtained by reading the README file in the PPP driver
      archive.  The latest version of this package should be obtainable at
      either http://www.coast.net/SimTel/msdos/pktdrvr.html (dosppp06.zip)
      or ftp://ftp.simtel.net/pub/simtelnet/msdos/pktdrvr/dosppp06.zip.

      I would like to thank the following people for patiently helping to
      test Internet Rex, and providing invaluable comments and suggestions
      on the program:
        Andrea Baitelli
        Craig Box
        Maciek Bukczynski
        Peter Connerty
        Vincent Danen
        Troy Davis
        Tom De Puysseleyr

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden           4
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

        Alec Grynspan
        Daniel Gulluni
        Richard James
        John Johnson
        Gino Lucrezi
        Dana Marshall
        Francois Massonneau
        Jennifer McNitt
        Jason Mroz
        Michael Oliver
        Ben Ritchey
        Steve Steffler
        Sam Voiers
        The people in IREX

      Various and sundry musical inspiration thanks go to Danny Elfman,
      John Williams, No Doubt, J.S.Bach, the composers at Activision
      (Mechwarrior II, Mercs), the contributors to the soundtracks for
      Mortal Kombat and The Rock, and Domenico Scarlatti.

        We are the music makers,
          We are the dreamers of dreams,
        Wandering by lone sea-breakers,
          And sitting by desolate streams; --
        World-losers and world-forsakers,
          On whom the pale moon gleams:
        We are the movers and shakers
          Of the world for ever, it seems.
                    - Arthur O'Shaughnessy


                              1.4: Registration


      Internet Rex is shareware, marketed under the "try before you buy"
      approach.  You are encouraged to test Rex for a period of up to 30
      days to see if it meets your needs.  After that time, you must
      either register Rex or remove the program from your system.

      The shareware version of Rex is not crippled in any way.  All the
      features available in the registered version of Rex are available in
      the unregistered version.  The only difference is the number of
      nodes configurable: unregistered users are limited to 2 nodes,
      whereas registered users can purchase either 50 or 1000 node
      lisences.

      If you would like to register Rex, please fill in one of the registration
      forms in the file register.zip and follow the instructions in it to
      return it to Khan Software.



      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden           5
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                          1.5: Contacting the Author


      If you have problems running Internet Rex, would like details on
      some of the standards implemented in Rex, or have general questions,
      I can be reached at the following addresses:

      Email: [e-mail] (preferred)
             [e-mail] (optional)

      Netmail: FidoNet        :   1:342/806
               BattleNet      :   169:4100/101
               Sysop's TechNet:   111:1200/11

      Snail mail:
        Charles Cruden
        10945 - 90 Avenue
        Edmonton, Alberta
        Canada
        T6G 1A4
































      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden           6
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                         Section 2: QUICK SETUP GUIDE


      Rex requires the following in order to work properly:

        DOS users:
          An 80286 or higher processor.
          DOS 3.31 or higher.
          If you intend to connect to a remote server (FTP or mail) you
            will also need a packet driver interface for your connection.
            A packet driver for PPP connections is provided, along with a
            program to initiate PPP sessions automatically.  (Read
            REXDIAL.DOC for more details.)

        Win95/WinNT users:
          An 80386 or higher processor.
          A correctly setup connection to the Internet via Windows's
            networking.  Rex supports dialup networking on both Win95 and
            WinNT.

        OS/2 users:
          An 80386 or higher processor.
          OS/2 2.x or higher.
          A correctly setup connection to the Internet via OS/2's
            networking.

        Linux users:
          A correctly setup connection to the Internet through Linux's
            networking.
          If you plan on using the configs from Linux on other operating
            systems or machines, you must be using an Intel processor.

      Rex is a powerful program and, as such, has a lot of options you
      may never need to worry about.  The following areas must be
      setup correctly in order for Rex to work with your mailer:
        General information
        Under Files, Paths and Programs:
          Internet Rex files and paths
          Frontend mailer setup
        Connecting to the net (if you're planning on using a dialup
          connection)
        Email setup (only if you're going to receive or send files
          via email)
        FTP setup (only if you're going to receive or send files via
          FTP)
        Address manager
        Node manager: you'll probably want to configure at least one
          node to send stuff to
      Users are referred to the User manual included in this distribution
      for a quick setup guide to Internet Rex.


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden           7
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                     Section 3: CONFIGURING INTERNET REX


      To configure Internet Rex, run the configuration program (REXCFG.EXE
      for DOS 16-bit, REXCFGD.EXE for DOS 32-bit, REXCFGP.EXE for OS/2,
      REXCFGW.EXE for Win95/98/NT or rexcfgl for Linux).  At the main menu,
      you are able to configure Internet Rex.  Each section configures a
      different part of Rex.


                           3.1: General Information


      Here you setup your name, email address (if applicable) and
      registration information.


      3.1.1: Sysop Name

      Enter your name here.  If you have an email connected node, this
      name will be used in the From field of messages generated by Rex.


      3.1.2: System Name

      Enter your BBS's name here.


      3.1.3: User level

      You can set this to any of "Beginner", "Intermediate", "Advanced"
      or "Expert": choose the value which best describes your familiarity
      with Internet Rex.  The higher the user level, the more options
      will be available for you to configure in the setup program.  Be
      careful, as with greater flexibility in configuration comes the
      possibility of setting something up incorrectly.  Read the help on
      any new options when you change user levels, to be sure you
      understand what they do.


      3.1.4: Registration String and Registration Key

      When you register Internet Rex, you'll receive a registration
      string and key to enter here.  These will be keyed to work only if
      the name eneterd in the Sysop name field matches the name sent in on
      the registration form.


                             3.2: Rex's Behaviour



      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden           8
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      Lets you configure aspects of how Rex will toss mail, and what
      messages he'll toss.


      3.2.1: Configure appearance


      This menu is used to setup how the Internet Rex configuration
      program will appear to you while you're using it.


      3.2.1.1: Use upper ASCII


      If this is set to Yes, Rex and its configuration program will use
      IBM PC upper ASCII and lower control characters while it's running.
      This gives a more aesthetically pleasing appearance (because there's
      a wider set of characters to choose from) but may not work on all
      platforms.  Linux users will probably find that turning this on
      results in a lot of garbage characters appearing on the screen.


      3.2.1.2: Colour scheme


      Hitting enter over this field will let you cycle through a number
      of different colour schemes available for Rex to use.  The change in
      colour scheme won't take effect until you've shut down the config
      program and restarted it.

      There is also one option in the list called "custom" which lets
      you define your own colour scheme.  If you've chosen this, the list
      of fields below will be changeable to whatever colour or character
      you choose.  Updates to the screen will happen as parts of the
      screen are redrawn after the custom config is changed.


      3.2.1.3: Main screen background


      This defines the foreground and background colour of the
      characters in the background on the config program's main screen.


      3.2.1.4: Main screen box colour


      This is the foreground/background colour of the box of text at
      the top of the config program's main screen.



      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden           9
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      3.2.1.5: Menu normal colour


      This is the foreground/background colour of the text of
      unhighlighted choices in menus and of the text in the help screens.


      3.2.1.6: Menu choice colour


      This is the foreground/background colour of the text of
      highlighted choices in the menus.


      3.2.1.7: Value colour


      This is the foreground/background colour of the text of values
      in the various screens.


      3.2.1.8: String edit colour


      This is the foreground/background colour used while editing
      strings of text.


      3.2.1.9: Help keyword


      This is the foreground/background colour of the help keywords
      in the help screens.


      3.2.1.10: Highlighted help keyword


      This is the foreground/background colour of highlighted keywords
      in the help screens.


      3.2.1.11: String edit background character (upper ASCII)


      This is the character that will be used to fill in the empty parts
      of strings while they're being edited if you're using the upper ASCII
      character set.


      3.2.1.12: String edit background character (lower ASCII)

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          10
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────



      This is the character that will be used to fill in the empty parts
      of strings while they're being edited if you're not using the upper
      ASCII character set.


      3.2.1.13: Background character (upper ASCII)


      This is the character used to tile the background of the main
      screen in the configuration program if you're using the upper ASCII
      character set.


      3.2.1.14: Background character (lower ASCII)


      This is the character used to tile the background of the main
      screen in the configuration program if you're not using the upper ASCII
      character set.


      3.2.1.15: Window border foreground colour


      This is the colour of the text in the foreground around the
      border of windows.  Note that whatever value you choose here, the
      background colour will be ignored.  Also, only dark colours will
      be used (that includes only colours on the left side of the colour
      selection screen).


      3.2.1.16: Window background colour


      This is the background colour of windows.  Note that whatever value
      you choose here, the background colour will be ignored.  Also, only dark
      colours will be used (that includes only colours on the left side of the
      colour selection screen).


      3.2.1.17: Close window box colour


      This is the colour of the little box in the corner of windows which
      you click on to close them.


      3.2.1.18: Disabled menu choice colour


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          11
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      This is the foreground/background colour of menu choices which are
      disabled.


      3.2.2: Graphical Tossing

      Set this to yes if you would like a full screen informative view of
      what Rex is doing as he processes your mail.  As this takes a little
      more processing time, it may not be for everyone.  Setting it to no
      will tame Rex back a bit so he only provides informational text
      messages as he's tossing.


      3.2.3: With Progress Bar

      If you really like watching stuff as it happens, Rex can make you a
      nifty progress bar which will show how far he's progressed at
      encoding or decoding files.  Only available if graphical tossing is
      on.


      3.2.4: Echo log to screen

      If you've disabled graphical tossing, this option tells Rex whether
      or not it should echo its log entries to the screen as well as to the
      log file.  With this option enabled, you'll get a better idea of what
      Rex is doing in text mode.  Otherwise, Rex will be quiet: the only record
      of its activities will be in the log file.


      3.2.5: Processor Friendliness

      If you're running Internet Rex on a multitasking system such as
      Win95, WinNT, OS/2, Linux or DesqView, you can set how often Rex will
      yield the processor to the OS here.  Going from nasty to sugar
      coated, Rex will yield to the processor more and more.  This will
      make other tasks run faster, but will slow down Rex.  Users on
      single tasking systems like DOS should set this to nasty to get
      better performance.

      Note that this only controls how much Rex will yield to the
      processor: it has no effect on programs Rex may spawn, such as
      archivers, dearchivers or maintenance scripts.

      This setting can be overridden at runtime using the -p command line
      option.


      3.2.6: Kill Empty Netmail


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          12
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      If asked to, Rex can auto-delete any outgoing mail which is an
      empty message. As a lot of mail will fall into this category
      (echomail, inter BBS door game packets, etc.) it is usually a good
      idea to have this set. Otherwise, it will be up to the program which
      processes the attached file to delete the mail at the other node.

      Rex will never delete empty netmail which isn't destined directly
      for the system it's being sent to.


      3.2.7: Send Crash/Immediate Mail

      If you would prefer to send crash or immediate mail through your
      BBS's mailer, set this to no.  Otherwise, crash and immediate mail
      will be tossed along with other mail destined for the node, and may
      take longer to reach its destination.


      3.2.8: Send Mail on Hold

      Set this to yes if mail which is marked "hold" should still be sent
      when Rex is run.  Otherwise, mail marked "hold" will be left in the
      netmail folder until the node it is destined for calls to pick it
      up.


      3.2.9: Send File REQuests (FREQs)

      FREQ messages can be sent through Internet Rex, though it is still
      possible that the mail program at the other end may not want to, or
      may not be able to honour them.  If you would like to send FREQ
      messages using Rex, set this to yes.


      3.2.10: Honour Return Receipt Requests (RRQs)

      If this is set to yes, Rex will generate receipt requests for
      netmail messages that ask for them to be sent.  Otherwise these will
      be ignored.


      3.2.11: Honour FREQs

      Internet Rex can handle incoming FREQs (see also the file setup
      menu).  If you would like Internet Rex to automatically process
      incoming FREQ messages, set this to yes.


      3.2.12: TransX mode

      You can either have Internet Rex run in TransX shuttle mode, or

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          13
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      TransX compatible mode.  In TransX shuttle mode, Rex acts as a shuttle
      mail program to upload and download your TransX messages (basically a
      replacement for TXMailer).  You will need a working copy of TransX
      for this mode to run properly.  Setting Rex to shuttle mode adds an
      extra option to the Files, paths and programs menu, TransX setup,
      where you must tell Rex about the way your copy of TransX is setup.
      You can use email addresses from any type of spool to fetch TransX
      mail, but can upload only to an SMTP mail server.

      In TransX compatible mode, Rex acts like a copy of TransX 1.5: it
      reads TransX messages itself and can generate messages similar to
      those TransX 1.5 would generate.  This mode adds an extra transport
      type to outbound email connections, TransX compatible, which lets
      you setup a TransX connection in Rex.  This mode does not require
      a copy of TransX to work.


      3.2.13: Inbound file case

      This lets you control what case Rex will use to store inbound files.
      Setting it to "as sent" tells Rex to store files using the same case
      as the message/FTP site that sent it (if possible).  Otherwise, you
      can set it to "Upper case" or "Lower case" to have Rex create every
      inbound file with an upper or lower case name.


      3.2.14: Swap to EMS/disk


      This option applies only to users of the DOS version of Rex.
      When launching external programs (such as archivers, dearchivers or
      BETWEEN.BAT processing), by default, Rex swaps into EMS, then to disk
      if it can, leaving a stub of only 2K in conventional memory.  On some
      systems though, this causes problems.  You can turn off swapping by
      setting this to no.  If swapping is off, Rex will stay resident in
      conventional memory while the other programs are executing.  This will
      result in a loss of about 250K of memory while these programs are
      executing: watch for low memory warnings.


                        3.3: Files, Paths and Programs


      Setup Rex's interaction with other programs, such as your mailer,
      compression programs, TransX and more.


      3.3.1: Drive Mappings

      For networked systems which have many disks, the letters of disks
      on one system may not match those on another.  Rex can automatically

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          14
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      remap disks according to the mappings specified here.  Also, for
      systems such as Linux which don't use drive letters, Rex can
      remap drive letters in various files to directories.


      3.3.1.1: Map drives to drives

      This lets you map one drive letter to another.


      3.3.1.1.1: Default Map

      This is the label of the drive mapping Rex will use if the -map
      argument is not used on the command line.  It is also the mapping
      Rex's configuration program will use to check directories to see if
      they exist.


      3.3.1.1.2: Edit Mapping

      Choose this to start editing a new drive mapping, or to modify or
      delete existing ones.


      3.3.1.1.2.1: Map Label

      This is the label Rex will use to identify the mapping you specify.
      It can be up to 8 characters long and is not case sensitive.


      3.3.1.1.2.2: Edit Mapping

      Choose this to start editing the drive mapping itself.  Use the
      insert key to create a new set of drives to map, enter to modify
      one, or delete to delete one.

      You can map several drives to the same letter (eg. map Q to F and
      map R to F) but only the first mapping of any drive will be used
      (eg. if you had map Q to G and map Q to H (in that order), the file
      Q:\REX\REX.LOG would be mapped to G:\REX\REX.LOG, and not H:...).


      3.3.1.2: Map drives to directories

      This lets you map drive letters to directories.

      Simply enter the drive letter you want remapped and the directory
      it should point to.  Once entered, the Linux version of Rex will
      take any reference to the drive letter given and replace it with
      the directory given.  For instance, if you had mapped drive E to
      /usr/driveE, when Rex saw the path E:\MAIL\NETMAIL\1.MSG, Rex

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          15
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      would look for /usr/driveE/MAIL/NETMAIL/1.MSG.


      3.3.2: Internet Rex files and paths

      Setup the various files and directories Internet Rex will use to
      while processing mail.  Files and paths given should be *full*
      file or path names: that is, they must have a drive letter at the
      start (for DOS type filesystems) or start with a / (for UNIX type
      filesystems).


      3.3.2.1: Log Filename

      Put the full name and path of the file you would like Rex to log
      its activities in here.  If no file is specified, Rex will not
      log its activities to disk.


      3.3.2.2: Temporary File Directory

      Rex has to create temporary files on occasion to process incoming
      and outgoing mail.  On these occasions, the files will be created in
      the directory specified here.  This should be the path to a fast
      disk, preferrably a RAM disk if at all possible.  If no temporary
      file directory is specified, Rex will look for the TEMP or TMP
      environment variables and take their values as the location of a
      temporary file directory.  If Rex cannot determine a temporary file
      directory, it will not run.  This must be a full path name: i.e.
      it must include a drive letter at the start.


      3.3.2.3: Queue Directory

      This is where Rex stores information about the current outgoing
      packets for the various nodes defined.  If this directory is not
      specified, Rex will not run.  This must be a full path name: i.e.
      it must include a drive letter at the start.


      3.3.2.4: Holding Directory

      Rex will occasionally have need to create larger files on the hard
      drive for use during its processing activities.  It will try to
      create these files in the holding directory.  If it isn't specified,
      Rex will not run.  This must be a full path name: i.e.
      it must include a drive letter at the start.


      3.3.2.5: Semaphore Directory


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          16
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      If you run a multinode system, it is very advisable that you
      specify this directory so that Rex can create semaphore files.  This
      will prevent other copies of Internet Rex from interfering with each
      other.  Otherwise, some mail may be tossed incorrectly, or not at
      all.  This must be a full path name: i.e.
      it must include a drive letter at the start.


      3.3.2.6: Received Mail Semaphore

      If, at the end of processing, Rex has tossed some mail from one of
      the nodes defined in the node manager, and a file is specified here,
      it will create that file.


      3.3.2.7: TransX Mail Semaphore

      This is like the received mail semaphore, only it will be created
      if Rex has tossed some mail for TransX to process.  If this file
      exists, running tx /noexport afterwards is advisable.  (This field
      only applies if you are running in TransX shuttle mode (see
      Rex's behaviour).)


      3.3.2.8: Run BETWEEN.BAT/.CMD

      If Rex detects that you've received incoming mail and that you're
      about to queue outgoing mail, you can set it up to run a batch file
      between these two events (so that incoming mail can be processed and
      possibly tossed back out again).  Setting this option to yes will
      make Rex run the batch file BETWEEN.BAT when incoming mail is received
      and outgoing mail is about to be queued.

      On OS/2 systems, Rex runs the batch file BETWEEN.CMD, not BETWEEN.BAT.

      On Linux systems, Rex runs the batch file between, not BETWEEN.BAT.

      This setting can be overridden at runtime using the -b command line
      option.


      3.3.2.9: Always Run BETWEEN.BAT

      If you want to, you can have Rex run BETWEEN.BAT or BETWEEN.CMD
      regardless of whether any new mail was received.  Setting this
      value to yes will make Rex run BETWEEN.BAT every time
      Rex queues outgoing mail.


      3.3.3: Frontend Mailer Setup


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          17
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      Lets you configure Rex's interaction with your frontend mailer.


      3.3.3.1: Mailer Type

      Set this to the type of mailer your system is using.

      FrontDoor (up to 2.20) and compatible:
      Should be chosen by people using FrontDoor up to and including version 2.20,
      or version 2.25 and higher if they are not using the advanced queue.

      Binkley and compatible:
      Should be chosen by people using Binkley, Xenia, Argus or any other
      Binkley compatible program.  Portal of Power users should choose the
      Portal of Power mailer, as it functions somewhat differently than
      Binkley, although the queues are similar.

      D'Bridge, Intermail, MainDoor, TMail, AdeptX, ViaMail, KBBS, PCBoard,
      Platinum Xpress, FrontDoor 2.25+ and QFront users should choose the option
      which matches their mailer.  ViaMail users should be aware of how Rex
      works with ViaMail (see the section at the end of the manual) and adapt
      their setups accordingly.

      If your mailer doesn't fall into one of the above categories, but can
      produce Type 2, Type 2+ or Type 2.2 packets for outbound nodes, choose
      *.PKT mailer.


      3.3.3.2: Netmail Directory

      This should match the netmail directory in your mailer.  The
      directory should contain Fido style *.MSG files: it will be used by
      Rex to create incoming netmail messages if email requires it, and
      will be scanned for potential outgoing messages.  ViaMail users
      should set this to match their 'Import .MSG path' in ViaMail's
      mailer options menu.

      If your mailer doesn't have a *.MSG netmail directory, create a
      directory for Rex to put mail in.


      3.3.3.3: Inbound Directory

      Files from insecure systems will be placed in this directory.  This
      includes mail from any unknown system in cases where Rex has been
      told to process any incoming mail.


      3.3.3.4: Inbound files directory

      (only for Platinum Xpress systems)

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          18
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      For Platinum Xpress systems, all inbound mail is assumed to be
      secure.  There can be different directories for inbound file, mail
      and .TIC files though.

      The inbound files directory is where inbound files
      will show up.  This must be a full path.


      3.3.3.5: Secure Inbound Directory

      Files from systems marked as secure in the node manager will be
      placed in this directory.  It should match the secure inbound
      directory of your mailer.  Some systems don't differentiate between
      secure and insecure sessions: in this case, just set the directory
      to match your system's inbound directory.


      3.3.3.6: Inbound mail directory

      (only for Platinum Xpress systems)

      This is the full path to your inbound mail directory.  Rex will put
      *.PKT files and arcmail bundles (*.SA?, *.MO?, etc.) here.  If this is
      the same as your inbound files directory, you can leave this blank.


      3.3.3.7: Semaphore Directory

      If your mailer is directly supported (i.e. listed by name in the
      list of supported mailers) Internet Rex will create semaphore files
      which are compatible with your mailer's semaphores in order to
      ensure that the netmail base is correctly processed and scanned
      before and after Rex is run.  This should match the semaphore
      directory setup in your mailer's configuration program.

      Rex interacts with ViaMail outside the multi-node environment: for
      this reason, Semaphore directory and Configure multinode don't apply
      to ViaMail.


      3.3.3.8: Inbound TIC directory

      (Platinum Xpress systems only)

      This is the full path to your inbound TIC directory.  Rex will put
      *.TIC files here.  If this is the same as your inbound files directory,
      you can leave this blank.


      3.3.3.9: Configure Multinode

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          19
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      If you're running a multinode system, or running Rex in the
      background while your mailer is running, you should fill in the
      semaphore directory and then configure Rex for multinode processing
      here.


      3.3.3.9.1: Enable Multinode Support

      Enabling this will tell Rex to look in your mailer's semaphore
      directory for various files while processing mail to make sure that
      the mailer isn't processing the same mail Rex is.  It will also tell
      Rex to create rescan semaphores when it's done processing mail.


      3.3.3.9.2: Session Semaphore Check

      Rex can check to see whether you are in a mail session on a global
      level or on a per node basis.  Global session checks means that Rex
      will check to see whether the mailer is in a mail session with ANY
      node.  Per node means Rex will only check for session semaphores for
      the particular node it's processing at the time.

      Global mail session checks should be used if your mailer has
      routing setup differently than the setup in Rex, or if you expect
      that one of the nodes routed in Rex may initiate a session with your
      mailer.  Otherwise, per node checking will be sufficient.

      If you don't want Rex to check whether you're in a mail session
      with other nodes, you can set this to none and Rex will skip this
      step.  This may result in loss or duplication of mail packets if
      your mailer is in a session with a node Rex is sending mail for.


      3.3.3.9.3: Wait to Clear

      This determines how Rex will behave if it discovers your mailer is
      in a mail session that conflicts with what it's doing.  If you set
      this to yes, Rex will pause until the session semaphore is cleared
      before proceeding as normal.  If set to no, Rex will skip processing
      for the node the current session is with.


      3.3.3.10: Outbound Directory

      (only for Binkley and Portal of Power systems)

      This should be the path to your Binkley style outbound mail queue.
      Rex will look for .?LO and .?UT packets in this directory, and in
      directories with this name and an extension of .###.  Don't put
      the zone extension on the end of this directory: it should be

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          20
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      something like c:\binkley\outbound, not c:\binkley\outbound.001.


      3.3.3.11: Outbound Queue

      (only for D'Bridge systems)

      This should be the path to your D'Bridge style outbound mail queue.
      Rex will look in this directory for C, H, I, N, and Q type packets.


      3.3.3.12: Filebox Directory

      (only for T-Mail systems)

      This should be the path to the root of your
      filebox directories. Rex will look in this directory for filebox
      directories (eg. zznnnxxx.pp, or zzzz.nnnn.xxxx.pppp).  Rex will only
      scan for file boxes if you fill this field in.


      3.3.3.13: Zones Directory

      (only for KBBS systems)

      This should be the directory where KBBS's ZONE* directories are
      located.


      3.3.3.14: FIDOQUE.DAT path

      (only for PCBoard 15.22+ systems)

      This should be the full path to your FIDOQUE.DAT file.  (Don't include
      FIDOQUE.DAT as part of it.)  Usually this is the directory where you
      installed PCBoard.


      3.3.3.15: QQUEUE.DAT path

      (only for QFront systems)

      This should be the full path to your QQUEUE.DAT file.  (Don't include
      QQUEUE.DAT as part of it.)  Usually this is the directory where you
      installed QFront.


      3.3.3.16: Packet path

      (only for Platinum Xpress and *.PKT systems)


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          21
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      This should be the full path to where the *.PKT files for outbound
      systems are located.  Platinum Xpress users should use PXNet to create
      these packets.

      IMPORTANT!

      Platinum Xpress users should NOT use PXNet to export file
      attach netmails.  They will not work.  Because of the way Wildcat's
      messaging system works, PXNet will not export the full path of the
      attached file, and Rex will not be able to find it.  If you want to send
      file attach netmail, use the *.MSG message base or some other method to
      attach the file, such as a mailbox directory or manually adding the file
      to PX's file queue with PXQEDIT.


      3.3.3.17: FILQUEUE.FD path

      (only for FrontDoor 2.25+ systems)

      This should be the full path to FrontDoor's FILQUEUE.FD file. Usually
      this is the directory where you installed FrontDoor.


      3.3.3.18: Long Fileboxes

      (only for T-Mail systems)

      If your file system supports long filenames and T-Mail is setup to
      use them, turn this on.  Otherwise, leave it off.


      3.3.3.19: Default path

      (only for *.PKT systems)

      Some *.PKT mailers occasionally create *.PKTs without the full path
      to certain files.  Rex will complain about this ("couldn't locate
      attached file") unless you specify the path to where these files are
      located here.  Often this is your the path to your arcmail bundles.


      3.3.3.20: Arcmail path

      (only for Platinum Xpress and QFront systems)

      This should be the full path to where packed mail packets (*.MO#,
      *.TU#, *.WE#, etc.) are stored.


      3.3.3.21: Binkley Outbound


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          22
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      (only for T-Mail systems)

      If you've setup T-Mail to use the Binkley outbound, put the Binkley
      outbound here.  If this field isn't filled, Rex won't look for a
      Binkley outbound.


      3.3.4: File REQuest Setup

      Internet Rex can process file requests from remote systems.  It
      will look through the .PKT files sent from other nodes for messages
      flagged as file requests, and use the settings you've provided here
      to answer those requests.  (This is only done if you've set Rex to
      honour FREQs in the Rex's behaviour part of the configuration
      program.)


      3.3.4.1: Alias File

      This file should be a text file containing the list of FREQ aliases
      on your system.  Each line should be of the form

        <alias> <filename> [!<password>]

      where <alias> is the alias you want <filename> FREQ'able by.  You
      can have the file accessible only if the password <password> is
      presented by adding the string !<password> after <filename>.


      3.3.4.2: Secure Alias File

      This file should be layed out the same as your alias file.  It will
      be accessed if an FREQ is made from a secure system and the alias
      could not be found in the insecure alias file.


      3.3.4.3: Directories File

      This file should be a plain text file containing a list of
      directories which people are allowed to FREQ files from.  If a
      FREQ'ed file cannot be found in the alias list(s), each directory in
      this file will be searched for the filename being FREQ'ed.  If you
      would like to limit access to a particular directory to those
      presenting the password <password>, put !<password> after the
      directory.


      3.3.4.4: Secure Directories File

      Like the alias files, this is the list of directories which are
      only accessible to people with secure connections.  If a FREQ from a

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          23
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      secure connection cannot be found in any of the above areas, one
      last search will be made through the directories listed in this
      file.


      3.3.4.5: Access file

      This file allows you to control file requests limits on an individual
      or class basis.  It's a text file: each line should follow the format
        <address or addresses> [<max. files> [<max. KBs> [day | session]]]
      where <address or addresses> is an address or wildcard which specifies
      the people you want the limits to apply to, <max. files> is the maximum
      number of files they can request, <max. KBs> is the maximum number of
      kilobytes they can request and [day | session] is either day or session,
      depending on what period you want to apply the limits over.

      The addresses specified can be either netmail addresses or email addresses.
      If the incoming file request is from a node in the node manager, Rex can
      assign it a netmail address, and that will be used to check the access file.
      Otherwise, email FREQs will be checked against email addresses in the
      access file.

      Specifying no limits after an address will be taken to mean that that
      address is denied access to file requesting.  Otherwise, Rex will fill
      in unspecified limits with the defaults specified in the Configure
      FREQ limits file.

      A sample access file might look like:
        1:342/806 10000 10000 day
        9999:*
        *@juno.com
      In this example, 1:342/806 is redefined to be allowed 10000 files per day and
      10000 KB of files per day.  All nodes in zone 9999 are deined FREQ access, as
      are any users who send an email FREQ from the @juno.com domain.


      3.3.4.6: FREQ Not Found Notice

      This is the name of a text file which will be mailed to nodes when
      the file they requested cannot be found.


      3.3.4.7: Delete FREQ Messages

      If you would like Rex to delete file request messages (netmail or
      email) when it's done processing them, set this to yes.  Otherwise,
      they will be tossed to your netmail message base like any other
      message.


      3.3.4.8: Wildcard FREQs

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          24
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      If the name of the file requested is a wildcard that ends up
      matching one or more of the files in one of your directories, you
      can set Rex up to either send only the first match against this
      wildcard, or to send all the files matching the wildcard.


      3.3.4.9: Configure FREQ Limits

      This lets you set limits on the number of files someone can request
      from you.

        FREQ limits for known nodes applied each...
        FREQ limits for anonymous nodes applied each...
          Rex can limit requests either on a per day or a per session
          level.  You can set which it will use for both known nodes
          (nodes listed in the node manager) and anonymous nodes.  For
          anonymous nodes, the limits are applied to each email address
          that FREQs files.  In other words, if you had a limit of 10M a
          day for anonymous nodes, and someone with the email address
          [e-mail] FREQ'ed 9M of files, someone else could still
          FREQ the full 10M, provided their email address wasn't
          [e-mail].

        Maximum FREQable Kilobytes
          Here you can limit the size of the files a remote node can
          request in one session.  If you set this to X and the remote
          requests more than X kilobytes worth of files, only the first X
          kilobytes of files will be sent.  If you set this to 0, there is
          no limit to the size of the files remotes can request in one
          session.

        Maximum FREQable Files
          If you would like to limit the number of files a remote node can
          request in one session, set that number here.  Setting this
          field to 0 will allow remotes to request as many files as they
          like in one session.  Otherwise, Rex will only send as many
          files as is allowed by this field.


      3.3.4.10: Process email FREQs

      Set this to yes if you would like to process email FREQs.


      3.3.4.10.1: Email FREQs

      Internet Rex supports processing of email FREQ messages.  If it receives
      a message with the subject FREQ through an address it expects to receive
      FREQ messages over, it will look through it for the following commands.
      Each command should be given on a line by itself.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          25
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      If you setup a dedicated email address for FREQs (using the All messages
      from setting in FREQ setup), any message which DOESN'T have the subject
      FREQ and which doesn't otherwise match some download setting in Rex (eg.
      you have that same address setup to download anonymous Fido2Int messages
      and it's a Fido2Int message) will be replied to as if the message had been
      an FREQ message with the HELP command in it.

        FREQ <a file or wildcard> !<password, if needed>
          This will request the file, or files matching the wildcard given.  If
        you gave a password, that will be used to try to pick up the file.
        For example:
          FREQ ALLFILES
          FREQ BRE*.ZIP
          FREQ SECRET.ZIP !Somepassword
        By default, these files will be sent back, one per message, Base64 (MIME)
        encoded.

        UUENCODE
          Once issued, any files requested after this command will be sent
        UUencoded instead of Base64 encoded.

        XXENCODE
          As for UUENCODE, any files requested after this command is issued
        will be sent XXencoded.

        MIME
          This will set the encoding back to Base64 (MIME) encoded files if it
        was set otherwise.

        SIZE <some number>
          This will set the number of lines used per message to encode files.
        For instance:
          SIZE 1000
        will make each message a maximum of 1000 lines long.  Any file which
        takes more than 1000 lines to encode will be broken up into multiple
        messages and sent that way.  (Broken up messages will be sent as
        multipart MIME messages.)

        HELP
          Will send the contents of the file FREQHELP.TXT from Rex's home
        directory in an email message to the user.

        REPLY-TO
          Will change the destination email address of the files sent after
        the command is issued.  For instance,
          REPLY-TO [e-mail]
        will send any further requested files to the address [e-mail]
        instead of the address which originated the FREQ message.

        QUIT

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          26
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

          Any further commands issued after this one will be ignored.


      3.3.4.11: Matching only through

      This option will become available if email FREQs are turned on.

      If you set email FREQs available, you should select which email
      addresses you would like to receive FREQs through.  Only messages which
      have the subject FREQ will be processed as FREQ messages.


      3.3.4.12: All messages through

      This option will become available if email FREQs are turned on.

      For the addresses chosen here, Rex will process ANY incoming message
      it doesn't recognize as a 'failed' FREQ message.  (Normal FREQ messages
      and messages from other Internet mailers will be processed according to
      the setup in the rest of the config program.)  A help request will be
      sent back to the user explaining how to use the FREQ services.

      Set this to email addresses you would like to be dedicated FREQ
      servicing addresses.

      IMPORTANT!  Be careful when using this option.  ANY message
      received through this address which doesn't match one of the nodes in
      the node manager will be treated as an email FREQ.  If you have also
      turned on Delete FREQ messages, you may end up losing mail.


      3.3.4.13: Default encoding

      If the FREQ message doesn't specify an encoding to use to send the
      requested file, Rex will use the encoding type you specify here to
      send the file.


      3.3.4.14: Default chunk size

      This lets you specify the default size Rex will split messages into
      when sending requested files.  A size of 0 lines means Rex will not
      split messages.


      3.3.5: TransX Setup

      Internet Rex can automatically detect incoming mail which is
      destined for processing by TransX, and can send outgoing mail which
      TransX has queued.  Use this option to setup paths to let Internet
      Rex work co-operatively with TransX.  (This option is only available

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          27
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      if you've set Rex up in TransX shuttle mode in the Rex's behaviour
      screen.)

      In order to use Internet Rex to send TransX's mail, you must
      configure TransX to use the SMTP (In\Out) advanced spool type.


      3.3.5.1: Send TransX Mail

      Turn this on if you want Rex to send mail waiting in TransX
      SMTP\Out directory.


      3.3.5.2: Send mail via

      Set this to the email address you will be sending your TransX mail
      through.  The username and domainname for this address should match that
      for the Receive mail via field (if you're also receiving TransX mail with
      Rex).


      3.3.5.3: Receive TransX Mail

      Turn this on if you want Rex to download any mail waiting for
      TransX and create compatible packets in the SMTP\In directory.


      3.3.5.4: Receive mail via

      Set this to the email address you will be receiving your TransX mail
      through.  The username and domainname for this address should match that
      for the Send mail via field (if you're also sending TransX mail with
      Rex).


      3.3.5.5: TransX SMTP\In Path

      This should be the full path to the SMTP\In directory specified in
      TransX's setup.


      3.3.5.6: TransX SMTP\Out Path

      This should be the full path to the SMTP\Out directory specified in
      TransX's setup.


      3.3.5.7: TransX Robot Name

      This should be TransX's robot name.  It's only needed if you've
      chosen to send TransX's mail using Internet Rex.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          28
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      In later versions of TransX, this field was removed.  It should
      contain the username of the email address you're using to send
      the TransX messages.


      3.3.6: Compression Programs

      Here you can specify the paths to compression programs that can be
      used to bundle mail to nodes with.

      Choose the operating system you are specifying a compression or
      decompression program for.  When you go to configure a new node,
      you can specify a different compression or decompression program for
      each operating system Rex runs under, with your choices being taken
      from the programs you specify here.  Rex will run the program
      appropriate to the operating system it's running under when it goes
      to pack or unpack mail.


      3.3.6.1: Tag

      This is the identifier that will be used when you go to choose a
      compression program in the node manager.  Choose something relevant
      to the program you're using, eg. ZIP for PkZip or UC2 for Ultra
      Compressor II.


      3.3.6.2: Command Line

      This should be the full name (and path if the program is not in
      your path) to the compression program to run, as well as the
      arguments you would need to create a compressed file.  If the
      program requires a command line switch in order to use list files,
      it should also be specified here.  Some examples for commonly used
      programs:

          PkZip 2.04g for DOS   pkzip
          ARJ                   arj a
          InfoZip               zip -9k@D


      3.3.6.3: List Character

      When Rex creates archives, it dumps the names of the files it wants
      to put in the archive to a list file, and passes this new file as a
      parameter to the compression program.  The compression program
      needs to support reading the list of files from the new file.
      (Fortunately, most compression programs do support this.)  The list
      character is the character that should come before the name of the
      list file for your compression program.  For most programs, this

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          29
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      will be the @ character, but for others it may be different.  Again,
      some examples for commonly used programs:

          PkZip 2.04g for DOS   @
          ARJ                   !
          InfoZip               <

      The command line constructed to compress programs is as follows:
      Fields in <>'s are generated by you, fields in []'s are generated
      by Rex:

      <command line> [archive name] <list character>[file with list of files
      to compress]


      3.3.7: Decompression Programs

      And correspondingly, this will let you specify the paths to
      decompression programs which will unpack incoming mail.

      The command line should specify the arguments required to extract
      files from an archive, but not the wildcards to use or switches
      needed for extraction to a particular directory.  For example, for
      PKZip, a good command line might be:

        pkunzip.exe -o

      If the file to be run is not in your path, you will need to specify
      not only the filename but the full path to the file in the command
      line.

      Once the command line is entered, you will be asked to specify the
      correct way to extract files to a particular directory.  If you use
      the default programs, you can just leave this at default.
      Otherwise, you can specify which one of the five methods given Rex
      will use to extract the files in an archive to a particular
      directory.  The info you choose will be added to the command line
      and the archive name to create the full command line passed to DOS,
      OS/2, Win95 or WinNT.  For example, if you chose "*.* #path" and a
      command line of pkunzip.exe -o, Rex might try to execute:

        pkunzip.exe -o archive.zip *.* #c:\inbound

      to extract the contents of archive.zip to the c:\inbound directory.


                          3.4: Connecting to the Net


      DOS and OS/2 users should fill in this screen if they intend to use
      Rexdial and a PPP/SLIP driver to connect to the net.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          30
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      Win95 and WinNT users can setup Rex to use Windows's built-in
      dialup networking here.


                               3.5: Email Setup


      If you're going to transfer mail over email, this is where you can
      configure all the information about how to send and receive email
      on your system.

      You only need to configure the options on this menu page if you are
      planning on sending/receiving mail via email.


      3.5.1: Configure email addresses

      Choose this to setup the email address(es) you would like to
      receive and send mail through.  Use insert to add a new email address,
      enter to modify one and delete to remove one.

      Addresses are listed alphabetically by domain name and then user name.
      Beside each address is given the type of spool it uses.  These are
        POP3  POP3/SMTP server
        UUCP  UUCP spool
        GTWY  Fido/Internet gateway
        GT/P  gateway using packets
        KA9Q  KA9Q compatible spool
        Soup  Soup/Yarn mail queue
        PMMl  PMMail folders
        Post  Postroad mailer
        MR/2  MR/2 Ice mail directory
        Eudo  Eudora mailboxes
        Nett  Nettamer mail spool
      After that are two spaces with either dashes or letters indicating
      whether the address is available for inbound (I) and outbound (O) mail.


      3.5.1.1: Address ID

      This name is used to identify the address elsewhere in Internet Rex.
      It's useful if you are setting up multiple entries for the same
      email address.  The Address ID is also used in the -[x]e<email ID>
      command line option to specify nodes sending or receiving email
      through a particular address.


      3.5.1.2: Username and Domain Name

      Any mail sent out will be listed as coming from user@somehost,

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          31
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      where user is Rex's username, and somehost is the system domain name
      you specify.  In UUCP setups, Rex will also use these fields to scan
      for mail.


      3.5.1.3: Mail Spool Type

      This tells Rex how you send your email.  Choices are:
        Connect to SMTP/POP3 host
          Rex transfers mail to/from SMTP/POP3 servers.  Most SLIP and PPP
          accounts fall into this category.
        UUCP
          Rex reads and writes a UUCP spool from a directory on your hard
          drive.  You'll still need your UUCICO program to upload and
          download mail.
        Gateway
          Rex reads and writes netmail messages to a Fido-Internet gateway
          machine.
        Gateway with packets
          Rex reads netmail messages and writes packets to a Fido-Internet
          gateway machine.
        KA9Q style SMTP spool
          Rex reads and writes messages to a KA9Q style SMTP spool.  This
          spool should have an inbound or RQUEUE directory and an outbound
          or MQUEUE directory.
        Soup/Yarn
          Rex reads and writes a Soup or Yarn mail queue.
        PMMail
          Rex will read and write messages in your PMMail email folders.
        PostRoad mailer
          Rex will read and write messages in your Postroad mailer email
          directories.
        MR/2 Ice
          Rex will read and write messages in your MR/2 Ice email folders.
        Eudora
          Rex will read and write messages from your IN and OUT mailboxes.
        Nettamer
          Rex will read and write messages to Nettamer's mail queue.

      Depending on which spool type you choose, you'll have different
      fields to setup.  Choose Configure to set each up.


      3.5.1.3.1: Configure


      3.5.1.3.1.1: POP3/SMTP setup


      3.5.1.3.1.1.1: SMTP Host


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          32
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      This should be the full machine name or IP address of your mail
      server.  For example:

        mail.somehost.com
        123.234.1.2

      This address or machine name should have been given to you by your
      Internet provider.  An SMTP host entry is required in order for Rex
      to send files out through Email.


      3.5.1.3.1.1.2: POP3 Host

      For many people, this should be the same as your SMTP host.  There
      are some providers though who have separate mail and POP3 servers.
      Put the machine name or IP address of your POP3 server here.  A POP3
      host is required in order for Rex to receive files through Email.


      3.5.1.3.1.1.3: POP3 Username

      This probably matches the first part of your email address, and
      should have been provided to you by your Internet provider.  For
      example, if your email address is [e-mail], your POP3
      username would be joe.blow.


      3.5.1.3.1.1.4: POP3 Password

      This is the password you need to retrieve your mail.


      3.5.1.3.1.1.5: Use APOP

      More advanced POP3 servers allow you to log in without sending your
      password in the clear over your connection by using the APOP login
      sequence.  If your server supports this and you'd like to use the
      feature, turn this on.  If your server doesn't support this and Rex
      is setup to use it, logins should still work, but an error message will
      appear in the log.


      3.5.1.3.1.1.6: Refetch Mail

      Depending on how much mail you typically receive, and how quick
      your mail server is at sending you mail, you may find that new
      messages have arrived in your mailbox while Rex was downloading
      mail.  You can have Rex check for new mail after a first pass by
      setting this option to yes.



      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          33
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      3.5.1.3.1.1.7: POP3 Timelimit

      If you connect to a dialup POP3 host with limited time online, you
      may want to tell Rex to use a POP3 time limit.  If you run into a
      situation where you cannot download all your mail in the time
      allotted by your server, the usual response of a POP3 server is to
      ignore any 'delete message' commands sent after you've been
      disconnected.  By enabling this, and setting the synch time in the
      next field, you tell Rex to periodically log off of the POP3 server
      and log back on again, to make sure that any delete message commands
      are actually applied.


      3.5.1.3.1.1.8: Synch Every...

      If you've set a POP3 timelimit, you need to set how long Rex will
      go before logging off the POP3 server and logging back on again.
      This defaults to 15 minutes, but should be set to something
      reflecting how long you're allowed to be online before you get
      disconnected.  (eg. if you have a 1 hour connection time limit, you
      could set this to 45 minutes.)


      3.5.1.3.1.2: UUCP Setup


      3.5.1.3.1.2.1: UUCP Path

      This should be the directory where your UUCP program stores its
      data files (*.D/*.X) and creates its command files
      (*.DAT/*.XQT/*.CMD on most systems).  Note that Rex creates UUCICO
      type UUCP spool files: UUPC or UNIX style long filename spools are
      not currently supported.


      3.5.1.3.1.2.2: Site Name

      This should be your site name as recognized by your UUCP uplink.


      3.5.1.3.1.2.3: Host Name

      This should be your UUCP uplink's host name.  Note that this is not
      necessarily the same as their domain name.  This field should match
      the "hostname" or "remote name" field in your UUCP spool processor.


      3.5.1.3.1.2.4: UUCP Grade

      You can specify what grade Rex should create its UUCP spool files
      with here.  The default is M.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          34
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────



      3.5.1.3.1.2.5: Spool Type

      There are a few different naming standards for UUCP spool files.
      The problem comes from trying to map the standard UNIX long
      filenames that UUCP has been used to using into the 8.3 format that
      DOS's filesystem uses.

      Rex currently supports creating spool files with either the UNIX
      long filenames, the munged 8.3 files created by programs like
      FX/UUCICO or munged 8.3 filenames without bitmasks (sometimes
      required by some UUCP servers): you can toggle between the three spool
      formats by hitting enter over this field.  Rex does NOT currently
      support spool files created and read by the program UUPC.


      3.5.1.3.1.3: Gateway / With Packet Setup


      3.5.1.3.1.3.1: Gateway's address

      This is the FTN address of your Fido/Internet gateway. (eg. 1:19/60)


      3.5.1.3.1.3.2: Message Flags

      Messages to your gateway will be created with the local and private
      flags set by default.  If you would like other flags set as well,
      you can choose which here.  Available flags are crash, del/sent and
      direct.


      3.5.1.3.1.3.3: Use UUCP Addressing

      Normally, if a message's address can be fit into the To: field of
      the netmail message, it will be.  In cases where it can't, the
      netmail will be addressed to UUCP and a To: field will be put at the
      top of the message showing the real address.  If you turn on UUCP
      addressing, ALL messages generated will be addressed to UUCP with a
      To: field.


      3.5.1.3.1.3.4: Packet Directory

      If you chose Gateway with packets, you need to specify the
      directory where your gateway tosser expects to put outgoing packets
      here.


      3.5.1.3.1.3.5: Packet password

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          35
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      If you chose Gateway with packets, you can optionally specify a
      packet level password to use in each of the packets created for your
      gateway.


      3.5.1.3.1.4: KA9Q Setup


      3.5.1.3.1.4.1: SMTP Inbound Path

      This should be the directory where your mail program creates the
      *.TXT/*.WRK files for inbound mail.


      3.5.1.3.1.4.2: SMTP Outbound Path

      This should be the directory where your mail program creates the
      *.TXT/*.WRK files for outbound mail.


      3.5.1.3.1.5: PMMail setup


      3.5.1.3.1.5.1: PMMail inbound


      This should be the full path to your PMMail inbound folder.  Usually
      this is in a subdirectory of your PMMail folder based on the account's
      name.  For example, if the account were for '[e-mail]', the
      subdirectory might be c:\pmmail\cruden0.act\inbox.fld.


      3.5.1.3.1.5.2: PMMail outbound


      This should be the full path to your PMMail outbound folder.  Like
      the inbound folder, this is in a subdirectory of your PMMail folder.
      The directory is outbox.fld instead of inbox.fld.


      3.5.1.3.1.6: PostRoad mailer setup


      3.5.1.3.1.6.1: Postroad inbound


      This should be the full path to your Postroad mailer inbound
      directory for the address you requested.  Usually this is in a
      subdirectory of your Postroad folder.  For example, if the email address
      were '[e-mail]', the inbound directory might be

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          36
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      c:\postroad\xanadu.


      3.5.1.3.1.6.2: Postroad outbound


      This should be the full path to your Postroad mailer outbound
      directory.  This is a subdirectory of the inbound folder.  Usually it
      is something like c:\postroad\xanadu\sndnotes.


      3.5.1.3.1.7: Soup/Yarn setup


      3.5.1.3.1.7.1: Queue path


      This should be the full path to your Soup or Yarn queue directory.
      Rex checks this directory for the AREAS and REPLIES files to read and
      write to the Soup/Yarn queue.


      3.5.1.3.1.8: Eudora setup


      3.5.1.3.1.8.1: Queue path


      This should be the full path to your Eudora queue directory.  Usually
      this is the directory you installed Eudora to.  Rex reads from the IN.TOC
      mailbox and writes to the OUT.TOC mailbox in this directory.


      3.5.1.3.1.9: MR/2 Ice


      3.5.1.3.1.9.1: Queue path


      This should be the full path to your MR/2 Ice queue.  Generally this
      is the mail subdirectory of your MR/2 Ice installation.  For example, if
      you installed MR/2 Ice to c:\mr2i, your queue path would be c:\mr2i\mail.
      This directory should contain MR2I.NDX and MR2I.OUT.


      3.5.1.3.1.10: Nettamer setup


      3.5.1.3.1.10.1: Queue path



      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          37
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      This should be the full path to your Nettamer mail directory.
      Generally, this is the directory you installed Nettamer to, but it may
      be in a sub-directory of Nettamer if you've set up extra mailbox
      directories.  Rex will read and write MAIL.$## files in this directory.


      3.5.1.3.2: Use for outbound mail


      Set this to yes if you would like to use this email address to send mail.


      3.5.1.3.3: Use for inbound mail


      Set this to yes if you would like to use this email address to receive mail.


      3.5.1.3.4: Messages downloaded

      Hitting enter over this selection will cycle you through the available
      choices for choosing what messages Rex will download.  They move up
      progressively through first only allowing Rex to download messages
      matching the criteria setup in the node manager; having Rex download those
      messages, plus messages from other Internet mailers whose nodes aren't
      listed in the node manager; to allowing Rex to download and post all the
      messages in your mail box.

      When Rex is setup to download all the messages in your mailbox, the
      ones it doesn't recognize will be converted to netmail and posted in
      your netmail message area.


      3.5.1.3.5: Stray messages from...


      If message downloaded is set to "Matching messages plus", you can
      configure whether Rex will download messages from Fido2Int, Internet
      Rex, FIDS compatible mailers, SEAT compatible mailers or Allfix.  If
      you've enablied TransX compatible mode, you can also choose TransX messages.
      A check mark beside the appropriate transport will signal Rex to download
      messages from that program, regardless of whether the message is from
      someone listed in the node manager or not.


      3.5.2: Time Zone

      This is the time difference between your time zone and GMT,
      measured in hours and minutes.  For instance, for mountain standard
      time, 7 hours less than GMT, the entry would be -7:00.


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          38
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      3.5.3: Gateway Address

      For those using POP3/SMTP or UUCP spools, netmail to this address
      will be converted into email.  If the address is empty (or 0:0/0),
      netmail to email conversion will be disabled.

      For those using email through Fido gateways, this is just the
      netmail address of your Fido gateway.


      3.5.4: Gate mail via

      This lets you select which email address to gate netmail to email
      through.


      3.5.5: Break lines at

      If the netmail you gate has lines longer than the number of
      characters given here, Rex will wrap the lines automatically so they are
      short enough to fit.  You can enter any number betwee 45 and 300 though
      it is recommended that you set this to 75 or 80 characters.


                                3.6: FTP Setup


      You only need to configure these options if you are planning on connecting
      to an FTP server using Rex, or if you are running and FTP server and want to
      use Rex to toss files to/from directories on your hard drive.


      3.6.1: Passive Mode FTP

      If your machine is setup behind a firewall which proxies or remaps
      FTP connections, Rex may be unable to download or upload files from
      remote FTP sites, even though it can connect to the sites just fine.
      If this is the case, you need to turn on passive mode FTP.  Since
      this command may not be supported on all servers, it is recommended
      that you do not turn this on if you don't need to.


      3.6.2: Lock Timeout

      Rex has locking mechanisms setup for both FTP tossing and local
      directory tossing.  If you choose to set your connection to check
      for locks and wait for locks to clear, you may find that Rex waits
      indefinitely for locks to clear on occasions when the remote has
      not cleared a lock after ending a session.  To avoid having this
      happen, you can set lock checking to time out after a certain number

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          39
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      of minutes.  If lock timeout is set to 0, Rex will wait until a lock
      is cleared before proceeding.


      3.6.3: Restarts

      Some FTP servers support restarting incomplete downloads from earlier
      failed attempts.  If you'd like Rex to try to use this feature, set this
      to on.  Rex will then keep any incomplete downloads in subdirectories of
      the holding directory and try to reconstruct them at a later time.  If
      this is set to off, incomplete downloads will be deleted.  This will save
      you the hard drive space required to store them, but the time taken to
      download them will be larger the next time around.


                             3.7: Address Manager


      Enter your system's main and alias addresses here and configure how
      they will be matched according to zones.


      3.7.1: System Addresses

      Setup your system's main netmail address and any AKAs you may have.


      3.7.1.1: Main Address

      This is the default address for your system.  Anytime Rex can't
      find a zone mapping which matches the current message, or anytime
      Rex needs a generic net address for the system, this is the address
      that will be used.


      3.7.1.2: System AKAs

      Here you can enter other addresses your system may have.  These
      will also be available in the zone matching area and the address
      selection part of the node manager.  You can specify up to 100
      different AKAs for your system.

      Use insert to create a new entry, enter to modify the currently
      highlighted entry, delete to delete the currently highlighted entry
      and the arrow keys to move up and down through the list.


      3.7.2: Zone Matching

      This defines the default way Rex will present your system to BBSs
      in other zones.  For each net you're in, you should defined the zone

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          40
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      it is associated with and the AKA you want to use for that zone.
      For example, FidoNet has zones 1 through 6, and let's say the BBS
      address is 1:342/806. Then the following entries should be made:

        1   1:342/806
        2   1:342/806
        3   1:342/806
        4   1:342/806
        5   1:342/806
        6   1:342/806

      Now since 4 is zone mapped to use 1:342/806, anytime Rex sees mail
      destined for a node in zone 4, the default address to use will be
      1:342/806.

      Strictly speaking, the zone 1 mapping is not necessary.  If Rex
      cannot find a zone map for a given address, it will search the list
      of AKAs for an address with the same zone and use that one by
      default.  So, if one of the defined AKAs was 100:6520/4, and no zone
      map existed for zone 100, 100:6520/4 would be used by default.


      3.7.3: Domains


      Use this section of Rex to setup matching zones to domains.

      For any net you're in, you can also define a domain which corresponds
      to that net.  This is done by associating a zone, or a number of zones,
      to the domain name you give.  (Consult the NC for your net to find out
      what the proper domain name for your net is before using this.)  Every
      netmail message and packet created by Rex containing mail to or from
      the zones you define will have the domain you give inserted into the
      message or packet.

      Rex also uses the domain as the 'fifth' dimension of addressing, so
      that if you have two nets with the same zone, you can define the domain
      for each net and have Rex export mail correctly.

      Finally, on Binkley-style mail systems (except Portal of Power, which
      doesn't support this feature), the domains you give here can also be used
      as alternate outbound directories.  Rex will first search the directories
      outbound.* in your mail path for outbound mail, then for each different
      domain, it will search the directories <domainname>.*.


                           3.8: Connection Defaults


      3.8.1: Maximum Resends


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          41
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      This is the maximum number times Rex will try to resend a message
      before giving up and deleting it without it being sent.  The only
      time this should come into effect is if a connection between you and
      a remote node is particularly bad, or if the remote node is no
      longer responding to mail.


      3.8.2: Dupe Protection Days

      Connections setup to send and receive acknowledgements
      automatically have a signature of every file logged in a local
      queue.  If for some reason a file is sent and received twice, Rex
      can make sure that only one copy is actually tossed to your inbound
      directory by looking through the queue of signatures and checking to
      see if the file has already been received.  Dupe protection days
      sets how long Rex will keep a signature in the queue before deciding
      the file has been properly received once and only once.


      3.8.3: Default Send Acknowledgements

      Rex can send acknowledgements of received files to nodes not listed
      in the node manager.  If you set this to yes, Rex will send these
      acknowledgements when it receives a file from an unknown Internet
      Rex node.  Otherwise, the file will be decoded, but not
      acknowledged.


      3.8.4: Dupe protection on all links

      If you've enabled dupe protection, you can also set Rex up to extend
      its protection to every link in the node manager.  By default, Rex only
      offers duplicate protection on nodes which have reliable links: reliable
      links ensure each file has a unique identification, allowing Rex to be
      sure that any file with the same ID is a duplicate.  When duplicate
      protection is extended to all links, Rex keeps a 20 byte signature of
      every file received along with its name.  If the name and signature of
      an incoming file matches one in Rex's list, it's considered a dupe and
      removed.  There is still a chance (albeit very small) that a new
      inbound file might have the same signature as an old one, in which case
      it might be removed incorrectly.


      3.8.5: Default Resend Delay

      This is the amount of time Rex will wait before sending a resend
      request for a incomplete multipart message to an unknown Intrenet
      Rex node.


      3.8.6: Partial Purge Delay

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          42
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      This is the amount of time Rex will wait before giving up on
      receiving the rest of an incomplete partial message from an unknown
      node or a node which doesn't have send acknowledgements set to yes.
      If you set this to 0 hours, partial messages will be kept until they
      are completed, no matter how long this takes.  This will ensure that
      partial messages are always completed if possible, but may also mean
      that some partial messages will remain in the queue until you remove
      them yourself.


      3.8.7: Purge Known Partials

      If this is set to yes, the partial purge delay will also be applied
      to nodes which DO have send acknowledgements set to yes.


                              3.9: Node Manager


      This is the menu where you create new connections, see what connections are
      already defined, or delete connections if need be.  Use the insert, enter
      and delete keys respectively to do this.


      3.9.1: Sysop's Name

      Enter the name of the sysop of the node in question.  It will be
      used in the To field of email messages, and is helpful for
      remembering who you're dealing with.  :)  Node must have the field
      filled.


      3.9.2: System Address

      The address of the system you're sending mail to.  Any netmail
      destined to this address will be sent according to the method you
      specify.  You must specify a system address for every node.


      3.9.3: Routing Information

      You may want to route mail to other systems through this node.  If
      this is the case, selecting this will bring up a routing editor
      which will let you specify addresses you want to be routed through
      this node.

      On each line, enter a wildcard or specific node you would like mail
      for routed to this node.  For example, the routing line:

        1:342/*

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          43
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      would cause all mail on the system destined for nodes in net 1:342
      to be routed to this node.

      You can use * or ? as wildcards.  * will match any length string; ?
      will match a single character.  For instance:

        1:342/2??

      would route mail destined for any node served by hub 200 in net
      1:342, but mail to 1:342/22 wouldn't match.

      You can also exclude particular addresses by putting an X in front
      of the addresses you specify.  For example:

        1:342/*
        X1:342/8??

      would route mail destined to nodes in net 1:342, except those nodes
      served by hub 800.

      Order is unimportant.  Exclude commands will be processed after
      include commands.  You can have up to 25 routing commands for a
      single node.


      3.9.4: Use AKA

      You can specify the AKA you want to use when communicating with
      this system here, or leave it on Use default/zone matching to let
      Rex match the AKA according to what has been defined in the zone
      matching part of address management.  If no match can be found in
      your AKAs or your zone matches, your main system address will be
      used.


      3.9.5: Node Active

      You can set whether Rex will process inbound or outbound mail
      for this node here.  Usually, this is set to "yes": Rex will
      process all mail for this node.  Setting it to "receive mail only"
      will make Rex only process inbound mail for the node: outbound
      mail will be left in your mailer's queue.  Similarly, setting it
      to "send mail only" will make Rex ignore any messages or files
      it sees from this node and only send it mail.  Finally, setting
      it to "no" will make Rex ignore this node's mail completely.


      3.9.6: Mailbox Directory

      For each node in Rex's setup, you can also define a mailbox

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          44
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      directory which Rex will search each time mail is queued for the
      node.  If it finds files in that directory, they'll be sent out and
      removed from the hard drive.  McMail users will find this matches
      the behaviour of its mailbox directories.  ViaMail users should be
      using this to specify the location of the files waiting for this
      node.  (See section x.x for more information about using ViaMail
      with Internet Rex.)


      3.9.7: Outbound Messages

      Select this multiple times to rotate through the available options
      for sending mail to this node.

      The available options are:


      3.9.7.1: Don't Toss Outbound

      Mail to this node will be left in your netmail folder.  Rex will not
      try to send mail to this node.


      3.9.7.2: Toss to Mail

      Mail and file attaches to this node will be sent via email.


      3.9.7.2.1: Transport Method

      This lets you choose what type of program Rex will emulate when
      sending mail to this node.

      MIME / none will send mail with only the barest minimum of extra
      text added to allow Rex to use manifests and receipts.  These
      messages should be decodable by anyone using a standard mailer or
      some of the simpler transport programs like Fidonet 2 Internet
      mailer.  If you don't know in advance what type of mailer your
      connection will be using, select this transport method.  In reality,
      MIME / none barely differs from SEAT in its encoding: the main
      difference is that MIME / none creates MIME standard multipart
      messages, whereas SEAT does not.

      SEAT (Rex native) uses the SEAT standard for writing messages.
      Files sent in a single message will still be decodable by most
      standard mail readers.  Files sent in multiple parts can only be
      decoded by SEAT compatible mailers.

      FIDS messages use the FIDS standard for transporting mail.  Single
      part messages will still be decodable by most mailers.  Multipart
      messages will be decodable by programs which use the MIME multipart

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          45
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      message standard.  An important note: the FIDS transport method does
      not currently support reliable connections.  See the help on
      Connection Details for more information on what restrictions this
      imposes.

      If your remote is using Allfix to receive files, Rex can produce
      messages which will be decodable and understandable by Allfix.
      Allfix messages will generally not be decodable by other programs.
      Multipart messages will NOT be decodable by other programs.  If you
      choose to use Allfix to send/receive files and the remote node is
      actually using Allfix to receive files, you should setup reliable
      connection information for this node: Allfix defaults to this, Rex
      does not.

      If you've enabled TransX compatible mode in Rex's behaviour, you'll
      also have the choice of sending messages using the TransX transport
      method.  Use this only if the node you're connecting to is using
      TransX and wants to connect using native TransX encoding.

      One exception exists to the restrictions on programs which can and
      can't read particular transport methods: Internet Rex supports ALL
      of the above transport methods for incoming as well as outgoing
      messages.  Rex will autodetect which method is being used and decode
      the message appropriately.

      Here is a list of various Internet transport programs and the
      transport method you should use for each to ensure maximum
      reliability.  A suggested encoding method follows (where
      applicable).

          GIGO                      MIME / none (UUencoded)
          Watergate                 MIME / none (UUencoded)
          Fido2Int                  MIME / none (Base 64 encoded)
          Internet Rex              SEAT
          SEAT compatible mailers   SEAT (UUencoded)
          PXFIDS                    FIDS
          Allfix                    Allfix
          TransX                    TransX
          TransNet                  MIME / none (Base 64 encoded)

      A special note for those connecting to users of TransNet.  TransNet
      requires a particular subject line in order to recognise its mail.
      That line must be:
        Transport From-(your address) To-(his address) Password
      So if you were 1:342/806, sending mail to 1:342/820, with password
      "Blah", the subject would have to be
        Transport From-1:342/806 To-1:342/820 Blah


      3.9.7.2.2: Encoding Method to Use


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          46
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      You can choose between Base 64 encoding, UUencoding, or XXencoding.
      Base 64, UU and XX encoding are Internet standards and should be
      readable by most mail programs.  For best results, follow the
      transport/encoding pairs suggested above.


      3.9.7.2.3: Email Address

      The email address to send mail to.


      3.9.7.2.4: Subject

      The subject to use in the email sent to the destination node.


      3.9.7.2.5: Message Length / Chunk Size

      If the transport method you've chosen supports multipart messages
      via the MIME standard, this option will be message length.

      Most mail hosts have a maximum message size: any message larger
      than this size will be split into smaller messages.  If your mail
      host is MIME compliant, this splitting process should not damage the
      mail being sent, but to be on the safe side, it is best to set the
      maximum message length to less than that of your mail host.  The
      smallest maximum of any mail host currently known is about 120
      lines.  The smallest value available for this setting is 100 lines.

      If you set message length to 0 lines, Rex will not split messages
      into parts.

      If the transport method you've chosen supports multipart messages
      via its own standard, this option will be chunk size.

      This lets you specify the largest chunk of a file that will be sent
      at once.  Files larger than this number of bytes will be split into
      smaller parts and each part will be mailed individually, to be
      reconstructed by the receiving program at the other end.  If your
      mail host splits one of these parts into smaller parts, it is
      possible the receiving program may not be able to decode the whole
      message.  Therefore, you should set this to something less than the
      maximum message size of your mail host.  The smallest value this may
      have to be is about 10000 bytes: most mailers support larger values.

      If you set the chunk size to 0, Rex will not split messages into
      parts.

      If you're using Allfix as a message transport, you MUST set the
      chunk size to less than 16K, otherwise messages will not be
      correctly decoded by the receiver.  If you're using the TransX

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          47
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      transport, you MUST set the chunk size to less than 60K, or
      the messages may not be decoded by the receive.


      3.9.7.2.6: Session password

      If you're using the TransX transport, you can set the session password
      to use with the node you're connecting to here.  Note that this is not
      the same as the session password field in the Connection information
      menu.


      3.9.7.3: Toss to Directory

      Mail and file attaches to this node will be moved into a directory
      on your harddrive.  This is ideal for people running FTP servers to
      distribute mail: Rex can be configured to check for lock files
      indicating a user is online downloading or uploading mail, and can
      also be configured to create lock files while processing this node's
      mail.

      This option is mainly intended for people running FTP servers.


      3.9.7.3.1: Destination

      The directory where outgoing mail will be placed.


      3.9.7.3.2: Check for Locks

      If turned on, Rex will see if there are any files matching the
      wildcard specified in the lock filename(s) field below it.  If it
      finds any, it will behave according to the flag set in the wait to
      clear field.


      3.9.7.3.3: Lock Filename(s)

      Specify the full name and path of the file to check for before
      processing mail for this node.  The name can contain wildcard
      characters.  For example:

        c:\mail\ftp\outgoing\users\bill\lock*.*

      would check in the directory c:\mail\ftp\outgoing\users\bill for
      any file matching lock*.*


      3.9.7.3.4: Wait to Clear


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          48
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      If set to yes, Rex will wait until the given file no longer exsists
      before tossing mail to this node.  If set to no, Rex will queue the
      mail in its queue directory and try to toss it the next time it's
      run.


      3.9.7.3.5: Create Locks

      Set this to yes if you would like Rex to create a file before
      tossing this node's mail, and delete the file when it's done.


      3.9.7.3.6: Lock Filename

      If you set create locks to yes, you can specify the full name and
      path of the file you'd like Rex to create here.


      3.9.7.4: Toss to FTP Site

      Mail and file attaches to this node will be uploaded to an FTP site
      you specify.

      Selecting configure under the outbound messages option will let you
      configure in more detail the method you've chosen for sending mail.


      3.9.7.4.1: Site Name

      This is the machine name or IP address of the FTP server Rex should
      log on to to upload files to.  If the FTP server you're connecting
      to is on a non-standard port, you can specify it by adding :<port>
      after the server's name.

      eg. xanadu.v-wave.com
          ftp.somewhere.com:1234


      3.9.7.4.2: Username

      Put the username for the FTP site to be used here.


      3.9.7.4.3: Password

      Put the password for the FTP site to be used here.  If no password
      is needed, this entry can be left blank.


      3.9.7.4.4: Site's Hours


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          49
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      If your remote's FTP site is only up certain hours of the day, you
      can specify from when to when the site will be up here.  The times
      are based on local time and use a 24 hour clock.  A check-mark
      beside a time indicates that the site will be available during that
      time.  Leaving all times unchecked, or all times checked will
      indicate to Rex that the site is always available.


      3.9.7.4.5: Lock file size

      You can set the size of the lock files Rex creates to either 0 or 1
      byte.  Some FTP processors won't work with 0 byte lock files.  Some FTP
      servers crash with 1 byte lock files.  Pick your poison....


      3.9.7.4.6: Unique storage

      If you're going to be uploading the same file to a site before the
      remote has a chance to download it, you should turn on Unique storage.
      Rex will try to store each file it sends with a unique filename so no
      files are overwritten.  This setup may not work on some servers.

      The disadvantage of this is that if a transfer is interrupted, the
      incomplete file will stay on the remote site and won't be overwritten
      when Rex tries to upload it on the next connection.


      3.9.7.4.7: Filename case

      By default, Rex will upload files using the case it got from the local
      filesystem.  If you store your files on a FAT file system (i.e. DOS),
      all the files Rex uploads will be sent in upper case.  If you store files
      on an HPFS, VFAT or NTFS file system, Rex will upload files whose names
      match those on the drive, case included.  This means, for instance, that
      the file "Test.zip" would be uploaded as "TEST.ZIP" if it were stored
      on a FAT file system, and "Test.zip" if it were on an HPFS file system.

      You can also have Rex override the file system defaults and upload all
      files either as all upper case or all lower case by toggling the value
      for this option.

      Note that if the FTP site you're uploading to stores files on a file
      system that doesn't preserve case (like FAT), the files will end up all
      upper case, regardless of the value for this option.  Rex will make every
      effort to send files using the case you request, but because the FTP
      server has a say in how the files are stored, it can't guarantee that
      they will end up with the case you request.


      3.9.7.4.8: Script Type


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          50
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      FTP can work either by having Rex automatically send files for you,
      or by you specifying the commands Rex should issue to the FTP site
      to upload the files.  If you select automatic, Rex will log on to
      the site, change to the directory you specify, optionally check for
      lock files or create them, upload the files to the FTP site and then
      log off.  If this doesn't match what needs to be done for your site,
      you should choose manual script type and specify the commands for
      your site.


      3.9.7.4.9: Scripting

      If you choose to use a manual script, you'll be presented with a
      window where you can enter up to 30 commands which will be issued to
      the FTP site after Rex has logged you on.  The set of commands which
      Rex understands can be found in section x.x.

      A sample script might go:
        CD \users\bill
        CHECK lok lock*
        EXCEPT locknot
        FOUND WAIT
        CD inbound
        DEL *
        PUT

      Once the last command has completed, Rex will log off the FTP site
      and continue processing other mail.

      If you choose to do an automatic script, you will have the
      following fields to fill in:


      3.9.7.4.10: Destination Directory

      The directory to which Rex will upload all the files destined for
      this node.


      3.9.7.4.11: Check for Locks

      If set to yes, Rex will check for any files matching the wildcard
      specified in the lock filename(s) field, and if it finds any that
      match, will act according to the setting in the wait for locks
      field.


      3.9.7.4.12: Lock Filename(s)

      Specify the full name and path, with wildcards, of any lock files
      you would like Rex to check for on the FTP site.  For example:

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          51
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


        \users\bill\lock*


      3.9.7.4.13: Wait to Clear

      If this is set to yes, Rex will wait until the lock file no longer
      exists before proceeding to upload files to the FTP site.  If it's
      set to no, Rex will log off the FTP site and upload the files the
      next time Rex is run.


      3.9.7.4.14: Create Locks

      If this is set to yes, Rex will create a zero byte file on the FTP
      site, with the name you specify in the lock filename field.


      3.9.7.4.15: Lock Filename

      Specify the name and path of a lock file you would like Rex to
      create before uploading files to this site.  For example:

        \users\bill\imonline


      3.9.7.5: Toss to a BinkP site

      Mail and file attaches to this node will be sent by connecting to a BinkP
      server and transferring the files.


      3.9.7.5.1: Site's address

      This should be either the hostname or the IP address of the BinkP
      site you want to connect with.  By default, Rex will try to reach this
      site on the BinkP port of 24554.  If the server is setup on a different
      port, you can specify the port after the hostname or IP address by
      separating the two with a colon.
        eg. binkp.myconnection.com
              Connect to binkp.myconnection.com on port 24554.
            binkp.myconnection.com:6666
              Connect to binkp.myconnection.com on port 6666.


      3.9.7.5.2: Site's hours

      Not all BinkP sites may be operational at all times.  If your
      connection only operates during certain hours, you can specify them
      here.  Rex will not try to connect to the site if the local time
      is outside these hours.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          52
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────



      3.9.7.5.3: Connection timeout

      This defines how long Rex will wait before deciding the remote
      has timed out.  If no data is sent or received for this many seconds,
      Rex will drop the connection and try again later.


      3.9.7.5.4: Block size

      BinkP specifies that each file must be broken down and sent in
      blocks of less than 32K each.  You can further specify how small
      you would like these blocks to be: the size must be between 1024 and
      32767 bytes (1K and 32K).  Changing the size of the blocks you send
      can help tune the performance of BinkP for each site you connect to.


      3.9.7.5.5: Default domain

      BinkP operates on a strictly 5D addressing format: all addresses
      presented must have a domain.  If you haven't configured any domains
      in Rex's setup, or some of your addresses don't have associated
      domains, Rex will have to add a dummy domain to the end of each
      non-5D address it sends: this field lets you specify what that dummy
      domain will be.


      3.9.8: Inbound Messages

      Select this multiple times to rotate through the available options
      for receiving mail from this node.

      The available options are:


      3.9.8.1: Don't Toss Inbound

      Rex will not look for mail from this node.


      3.9.8.2: Toss From Directory

      Rex will check a specific directory on your hard drive for new files
      and toss any it finds as if it came from this node.  This option is
      mainly intended for people running FTP servers.


      3.9.8.2.1: Source

      The directory where incoming mail will be searched for.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          53
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────



      3.9.8.2.2: Check for Locks

      If turned on, Rex will see if there are any files matching the
      wildcard specified in the lock filename(s) field below it.  If it
      finds any, it will behave according to the flag set in the wait to
      clear field.


      3.9.8.2.3: Lock Filename(s)

      Specify the full name and path of the file to check for before
      processing mail for this node.  The name can contain wildcard
      characters.  For example:

        c:\mail\ftp\outgoing\users\bill\lock*.*

      would check in the directory c:\mail\ftp\outgoing\users\bill for
      any file matching lock*.*


      3.9.8.2.4: Wait to Clear

      If set to yes, Rex will wait until the given file no longer exsists
      before checking for mail from this node.  If set to no, Rex will
      skip the check for mail for now and try again the next time it's
      run.


      3.9.8.2.5: Create Locks

      Set this to yes if you would like Rex to create a file before
      tossing this node's mail, and delete the file when it's done.


      3.9.8.2.6: Lock Filename

      If you set create locks to yes, you can specify the full name and
      path of the file you'd like Rex to create here.


      3.9.8.3: Toss From Mail

      Rex will search your incoming mail messages for mail which matches
      search criteria you specify.  If it finds some, the mail will be
      downloaded and tossed.

      Selecting configure under the inbound messages option will let you
      configure in more detail the method you've chosen for receiving
      mail.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          54
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      NOTE TO PEOPLE INTERFACING WITH REMOTE NODES NOT USING INTERNET
      REX.  The system of sending and receiving acknowledgements and
      resend requests is currently not standardized across FTN transport
      programs: in fact, it is completely absent in many of them.  Do not
      enable these features unless the remote site is using a program
      which is compatible with Internet Rex in this respect.  Currently,
      the only known programs which will support this feature are Internet
      Rex, Inet2FTN, SEAT level 2 compatible mailers, TransX and Allfix 5.0.


      3.9.8.3.1: Configure Matching Information

      This set of matching rules determines what Rex will use to identify
      a given message as coming from this node.  Each rule comes in two
      parts: a matching field and a string to search for.

      The string to search for is a sequence of characters Rex will to
      try to find.  When Rex looks for strings, case does not matter.  So
      "Bob" would be the same as "BOB" or "bob".

      The matching field is the header field in the message Rex will
      search for the string you give.  Every header field which matches
      the field you choose will be examined.

      Here are some examples:

        Message contains:
          From: "Joe Blow" <[e-mail]>
        You search for:
          From contains Joe Blow
        Result: match

        Message contains:
          From: "Joe Blow" <[e-mail]>
        You search for:
          From contains Joseph Blow
        Result: no match

        Message contains:
          From: "Joe Schmoe" <[e-mail]>
        You search for:
          From contains Joe
        Result: match

      You can have more than one clause to use to match against the
      message.  For instance, if you were receiving mail from both Joe
      Schmoe and Bob Schmoe, just looking for "From contains Schmoe" would
      make all the mail to both Bob and Joe go to whichever of them
      appeared first in your list of nodes.  However, if you were to put
      in:

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          55
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


        From contains Schmoe and
        From contains Joe

      this would find mail for Joe, and not Bob.  You could replace the
      last line with "From contains Bob" to find mail for Bob.  You can
      also put in "or" conjunctions instead of "and"s.  When checking a
      message header, Rex puts brackets around any pair of clauses joined
      by an or conjunction.  So the clauses:

        From contains Bob or
        From contains Joe and
        From contains Schmoe

      would be evaluated as (From contains Bob or Joe) and From contains
      Schmoe.

      It is important to note that before Rex will download a message for
      a particular node, ALL the clauses joined by "and" have to be
      matched.  The reason "From contains Schmoe and From contains Joe"
      doesn't download mail from Bob Schmoe is that while the first clause
      ("From contains Schmoe") matches, the second one doesn't.

      As you can see, Rex isn't particularly bright when it comes to
      matching messages to names, so you need to be sure to give Rex both
      enough info to find the right node, yet not so much info that he
      skips out on messages he shouldn't.  A good way to track down what
      you're looking for is to look at the headers of the messages in your
      mail box before running Rex and see what's in them, then configure
      the matching information according to what you see in the headers.


      3.9.8.3.2: Post to Netmail

      This determines what messages from this node will be posted in your
      netmail message area.  You can select from none, some or all.  If
      you select some, you'll get the further two choices listed below.


      3.9.8.3.3: Delete Empty Messages

      If set to yes, Rex won't post any incoming messages from this node
      which contain no information, either because they contained only an
      attached file, or because there simply wasn't anything there to
      begin with.


      3.9.8.3.4: Delete File Attach Messages

      If set to yes, Rex won't post any incoming messages from this node
      which have a file attached to them.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          56
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────



      3.9.8.3.5: Strip Message Headers

      By default, if Rex saves a message to netmail, it will save the
      ENTIRE message, including the header lines (Subject:, From:, To:,
      Message-ID:,  etc.).  If you would prefer that Rex not save these
      header lines as part of the incoming mail for this node, set this
      option to yes.


      3.9.8.4: Toss From FTP Site

      Rex will log on to the FTP site you specify and look in a specific
      directory there for new files.  If found, these will be tossed as if
      they came from this node.


      3.9.8.4.1: Site Name

      This is the machine name or IP address of the FTP server Rex should
      log on to to download files from.  If the FTP server you're connecting
      to is on a non-standard port, you can specify it by adding :<port>
      after the server's name.

      eg. xanadu.v-wave.com
          ftp.somewhere.com:1234


      3.9.8.4.2: Username

      Put the username for the FTP site to be used here.


      3.9.8.4.3: Password

      Put the password for the FTP site to be used here.  If no password
      is needed, this entry can be left blank.


      3.9.8.4.4: Site's Hours

      If your remote's FTP site is only up certain hours of the day, you
      can specify from when to when the site will be up here.  The times
      are based on local time and use a 24 hour clock.  A check-mark
      beside a time indicates that the site will be available during that
      time.  Leaving all times unchecked, or all times checked will
      indicate to Rex that the site is always available.


      3.9.8.4.5: Lock file size

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          57
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      You can set the size of the lock files Rex creates to either 0 or 1
      byte.  Some FTP processors won't work with 0 byte lock files.  Some FTP
      servers crash with 1 byte lock files.  Pick your poison....


      3.9.8.4.6: Auto-delete

      If this is set to yes, as part of the GET command, Rex will delete
      files as soon as they are downloaded.  If set to no, Rex will not
      delete files on the remote site unless you specifically tell it to
      in a manual script.


      3.9.8.4.7: Script Type

      FTP can work either by having Rex automatically get files for you,
      or by you specifying the commands Rex should issue to the FTP site
      to download the files.  If you select automatic, Rex will log on to
      the site, change to the directory you specify, optionally check for
      lock files or create them, download the files to the FTP site and
      then log off.  If this doesn't match what needs to be done for your
      site, you should choose manual script type and specify the commands
      for your site.


      3.9.8.4.8: Scripting

      If you choose to use a manual script, you'll be presented with a
      window where you can enter up to 30 commands which will be issued to
      the FTP site after Rex has logged you on.  The set of commands which
      Rex understands can be viewed in section x.x.

        A sample script might go:
        CD \users\bill
        CHECK lok lock*
        EXCEPT locknot
        FOUND WAIT
        CD inbound
        GET *

      Once the last command has completed, Rex will log off the FTP site
      and continue processing other mail.

      If you choose to do an automatic script, you will have the
      following fields to fill in:

        Source Directory
          The directory from which Rex will downdload all the files from
          this node.


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          58
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

        Check for Locks
          If set to yes, Rex will check for any files matching the
          wildcard specified in the lock filename(s) field, and if it
          finds any that match, will act according to the setting in the
          wait for locks field.

        Lock Filename(s)
          Specify the full name and path, with wildcards, of any lock
          files you would like Rex to check for on the FTP site.  For
          example:
            \users\bill\lock*

        Wait to Clear
          If this is set to yes, Rex will wait until the lock file no
          longer exists before proceeding to upload files to the FTP site.
          If it's set to no, Rex will log off the FTP site and upload the
          files the next time Rex is run.

        Create Locks
          If this is set to yes, Rex will create a zero byte file on the
          FTP site, with the name you specify in the lock filename field.

        Lock Filename
          Specify the name and path of a lock file you would like Rex to
          create before uploading files to this site.  For example:
            \users\bill\imonline


      3.9.8.5: Toss from a BinkP site

      Mail from this node will be picked up by connecting to a BinkP server
      and tranferring the files.  See the section "Toss to a BinkP site"
      for explanation of the fields in this screen.


      3.9.9: File Bundling

      Rex can optionally bundle all the files for a node into a
      compressed file before sending them, and extract files from incoming
      archives.  You can setup these options for this node by hitting
      enter here.


      3.9.9.1: Auto-extract Incoming

      Use this to automatically unarchive attached files from this node,
      when possible.  If Rex detects an archive it can identify, it will
      call the dearchiving program you've configured in the files, paths
      and programs section and try to extract the files it contains.  You
      should only turn this on if your remote connection is sending your
      mail archived into a compressed file.  Otherwise, you may find

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          59
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      attached files inadvertently unzipped to your inbound file
      directory, or Rex may complain about badly extracted files or
      archivers not present if the file has a signature which matches one
      of the archivers Rex knows about.


      3.9.9.2: Bundle Outgoing Files

      Rex can either send every file it finds for a given node in one big
      archive, or it can send each file individually.  Setting this to
      "no" will make Rex send each file for this node separately.  For
      email nodes, this means each file in a separate message.  For FTP or
      directory nodes, the files will be sent one by one.

      Setting this to "yes" will make Rex bundle all the outgoing files
      for this node into a single compressed file (according to the values
      you choose in Archive name and Archiver to use) and send that file
      instead. This will cut down on the amount of time needed to send
      mail for the node, but "puts all your eggs in one basket": if the
      file is corrupt and has to be resent, all the mail has to be resent
      again, instead of just the one file that might have to be resent if
      you'd bundled the files individually.  You also have to make sure
      that the node you're sending the files to is able to recognize that
      the files are being bundled and extracts them before using them.


      3.9.9.3: Archive Name

      This choice will only be available if you choose "Bundle outgoing
      files".

      Specify the name of the file you'd like to contain all the files
      destined for this node.

      If the file name contains #'s, they will be replaced with a
      different number each time Rex is run.  For example:

        mail###.zip

      mail0.zip will be sent the first time, then mail1.zip, up to
      mail999.zip, then back to mail0.zip.


      3.9.9.4: Max size

      If you gave an archive name with #'s in it, you will have the
      option of setting a maximum bundle size.  Rex will then try to build
      archives where the total size of the files in the archive is less than
      the size you give here.  If you set this to zero, there will be no
      maximum bundle size: all the pending files for the node will be put
      into one bundle.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          60
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────



      3.9.9.5: Archiver To Use

      This choice will only be available if you choose "Bundle outgoing
      files".

      The compression program to use to create the file.  You will be
      asked for choices for each operating system you've defined
      compression programs for.  (See the files menu to define compression
      and decompression programs.)  If you select "none" for the operating
      system you are running Rex under, an error will occur when Rex is
      run and mail for this node is pending.


      3.9.10: Connection Information

      Here you can set up secure and reliable transmission of information
      for the connection.  If you don't want to use a reliable link, and
      you don't want to encrypt the information you're sending, you don't
      need to bother with this.


      3.9.10.1: Packet level password

      Any time Rex exports netmail for a node, it puts it in a .PKT file.
      This field lets you specify the packet password for this node.  If the
      field is empty, no password will be put in.


      3.9.10.2: Encryption password

      This defines a password that will be used to encrypt the files you
      send to the remote site.  The encrypted files will only be readable
      if this password is known at the other site.

      The password can be any word or phrase (any character is acceptable
      as part of the password), but must be at least 8 characters long.

      IMPORTANT!  Currently, the only program which supports sending and
      receiving of files in an encrypted form Rex understands is Rex
      itself.  DO NOT SETUP A SESSION LEVEL PASSWORD OR ENCRYPTION WITH A
      SITE NOT USING INTERNET REX.  Incoming mail from that site will be
      garbled and lost.


      3.9.10.3: Encryption Method

      If you've defined a password for this connection, you can choose
      the encryption method Rex will use to encode your messages.  SCoder
      is a Rex proprietary encryption scheme with OK protection and good

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          61
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      speed.  Blowfish is a standardized encryption method with excellent
      encryption capabilities, but a bit slower than SCoder.  Obviously
      the remote site must have the same encryption method setup in their
      connection, or the files will not be decoded correctly.


      3.9.10.4: Session password

      This password will be used when establishing a session with the
      remote site - BinkP will use it during the connection phase, and SEAT
      level 4 mailers will recognize it in the Ftn-Auth line to authenticate
      incoming files.  The password can be any word or phrase and any length.
      Matching against the remote password is case sensitive.

      If the link you are setting up is a TransX link, note that the
      session password for TransX sessions is not entered here, but rather
      in the Session password field in the Toss to mail configuration menu.


      3.9.10.5: Secure Connection

      If this is set to yes, Rex will consider any connections made with
      this node to be secure.  This means that incoming files from this
      node will be tossed to the secure inbound and that file requests
      from this node will be allowed to access the secure alias and
      directory list files.

      It is important to note that whether a connection with a node is
      secure or not is determined entirely by what this value is set at.
      You could have a session level password defined in Rex, or a packet
      level password defined in your tosser and still have stuff from this
      node tossed to the insecure inbound.  You could have no password
      whatsoever with this node, but if you turn secure connection on, the
      files will be tossed to your secure inbound.


      3.9.10.6: Send Acknowledgements

      If this is turned on, every file that is received from this node
      will generate a reply message saying whether or not the file was
      correctly received.  This should match the remote's setup for accept
      resend requests.  Naturally, you'll only be able to turn this on if
      you're setup to receive mail from the remote site.

      This value can be set to no, yes or batch.  No turns off sending
      acknowledgements, yes turns it on but acknowledgements are sent one per
      message, batch turns it on and sends all the acknowledgements gathered
      in one session in one message.

      IMPORTANT!  In order for the remote site to actually be able to use
      the acknowledgements sent, it must be using Internet Rex, Allfix, Transx or

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          62
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      a SEAT compatible mailer.  Don't bother turning on send
      acknowledgements if the remote site isn't using one of these
      programs.

      If the remote site is using Allfix, you MUST turn on send
      acknowledgements.  Allfix requires that a reliable connection be
      setup.


      3.9.10.7: Resend Request Delay

      This represents the number of hours Rex will wait before sending a
      resend request to complete a incomplete multipart message.


      3.9.10.8: Accept Resend Requests

      If this is turned on, Rex will keep all outgoing mail for a period
      of time before purging it.  If it receives a resent request after
      the mail has been sent, it will be resent.  Resend requests may come
      through if the mail was damaged in transit to the other system, or
      if parts of a multipart message were not received.  Naturally,
      you'll only be able to turn this on if you're setup to send mail to
      the remote site.

      IMPORTANT!  In order for Rex to be able to process requests for
      resends, the remote site must be using a program that sends
      receipts.  Currently this set of programs is limited to Internet
      Rex, Allfix, Transx  and SEAT compatible mailers.  Don't turn on accept
      resend requests unless the remote is using one of these programs.

      If the remote site is using Allfix, you MUST turn on accept resend
      requests.  Allfix requires that a reliable connection be setup.


      3.9.10.9: Purge Delay

      This is the number of hours Rex will keep mail online before giving
      up on sending it.


      3.9.10.10: Auto-resend Unacked Mail

      If this is enabled, Rex will automatically resend mail which has
      not been acknowledged after the purge delay is up.  It will do this
      up to three times before giving up on the message.


      3.9.11: Node's Statistics

      This will show you information about how many files have come

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          63
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      through this node, when they came through and how large they were.

        Last Received On
        Last Queued On
        Last Sent On
          Shows the time mail was last received, queued or sent to this
          node.

        Last Reset Stats
          Shows the last time the statistics for this node were cleared.

        Incoming Mail
          Displays the number of files received from this node, and the
          total size of those files in kilobytes.

        Outgoing Mail
          Displays the number of files sent to this node, and the total
          size of those files in kilobytes.

        Reset Stats
          Choosing this will clear the incoming and outgoing mail
          statistics for this node.


                              3.10: Queue Editor


      This displays information about the packets currently being held in
      Rex's queue directory.  Each entry on the screen represents a packet
      either being held for confirmation/resending purposes or a part of a
      multipart message waiting to be completed.  You will only see
      outbound entries here if you've set up one or more nodes to
      send/receive acknowledgements/receipts.

      The entries displayed have the name and address of the node the
      packet is to/from, the amount of time until the packet expires, and
      a series of flags indicating what the packet's status is.

        o O indicates the packet is outbound
        o I indicates the packet is inbound
        o S indicates the files in the packet have been sent
        o R indicates the files are pending a resend request
        o Q indicates the files have been queued
        o F indicates the files have been marked for forced expiry the
            next time Rex is run

      Selecting a packet and pressing delete will let you delete the
      packet from the queue.  Pressing return on a selected packet will
      bring up more details about it and let you perform various editing
      functions on it.


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          64
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      3.10.1: Packet Level - Outbound Packet

      This packet is outbound.

        Sent
          This tells you the time the packet was last sent to the remote
          node.

        Expires
          This tells you when the packet will expire.  If you have the
          number of available resends higher than the number of resends on
          the packet, it will be resent when it expires.  If the number of
          resends on the packet exceeds the number of resends possible,
          the packet will be deleted next time Rex is run: the files will
          not be sent.

          Hitting enter over this field will expire the packet now.

        To
          This shows which node the packet is for.  If the node it was for
          originally has been deleted, this field will show "Unknown".  If
          the packet is destined to an anonymous node (one not listed in
          the node manager), the email address of the recipient is shown.

          The destination email address of anonymous nodes can be changed
          by hitting enter over this field.

        Contains
          This shows how many files the packet contains at the moment, and
          how many have been acknowledged.  Rex purges acknowledged files
          from the outbound packets when it gets the chance, so the
          acknowledged field may often be 0.  Hitting enter over this
          field will bring up a detailed list of the files in the packet
          and information about them.

        Queue Number
          This tells you which file in Rex's queue directory this entry is
          associated with.  For example, if the queue number is F456,
          there is on of F456.ML, F456.DIR or F456.FTP in the queue
          directory, and you are looking at its contents.  It can't be
          edited.  DO NOT CHANGE THE NAME OF THE FILES IN REX'S QUEUE
          DIRECTORY, unless you feel like making a mess of things.

        Resends
          This tells you the number of times the node this packet is
          intended for requested a resend of one of the files in this
          packet.  This number cannot be edited.


      3.10.2: Packet Level - Inbound Packet

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          65
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


      This packet is inbound.

        Resend
          This tells you when Rex will request from the remote node that
          this file be resent.  Hitting enter over this field will ask Rex
          to send this request the next time Rex is run with the -send
          parameter.

        Expires
          This tells you when Rex will give up trying to complete this
          packet and delete it from the queue.  If the field is blank, Rex
          will keep this packet until all parts of the message are
          received, no matter how long this might take.

          Hitting enter over this field will ask Rex to expire the packet
          the next time Rex is run.

        From
          This shows who the packet is from.  If it is a multipart message
          from an unknown node, the field will show "Unknown".  If it's a
          multipart message from an anonymous node (one not listed in the
          nodelist), the email address of the person who sent it is shown.

          If the message is from an anonymous node, you can change where
          Rex thinks the message came from by hitting enter.  This is only
          useful if Rex is going to send receipts back to the sender.

        Contains
          This shows how many parts of the message have been received so
          far and how many are needed for the message to be complete.  If
          the name of the file contained in the message is known, it too
          is shown.

          Hitting enter on this field will let you look at the list of
          parts received.

        Message ID
          This shows the ID used to identify incoming messages as being
          part of this multipart message.  It is not editable.


      3.10.3: File Level

        Filename
          This is the name this file will be given when presented to the
          remote node.  Usually, changing this is not a good idea, but if
          absolutely necessary, you can do so by hitting enter on the
          field.

          If the file whose name you are changing is part of a multipart

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          66
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

          file, all the names of the other parts will be changed to match
          the name you give this part.

        Location
          This will either say 'Stored in queue' or 'Return to disk
          pending'.  Stored in queue means that the file will be left in
          the queue when you are done editing the packet it is in.  Return
          to disk pending means the file will be removed from the packet
          and dumped to your inbound files directory when you are done
          editing the packet.

          If the file you are editing is part of a multipart file, all
          file parts will have their locations updated when this part's
          location is changed.

        Special
          This provides remarks about the file you are looking at.
          Receipt message means that the contents of the file are a
          receipt being sent to the remote node, either acknowledging the
          proper receipt of a file from that node, or requesting a resend
          of something the node sent.  These types of files should not be
          deleted or returned to disk.  Message to be sent uncoded means
          that the contents of the file will be written directly to an
          email message sent to the remote node: they will not be encoded
          in any way.  So if the file contained "Hail Caesar!", the remote
          would receive an email with the words "Hail Caeser!" in it.
          File split into multiple parts means that this file is a part of
          a larger file that had to be split into chunks in order to be
          sent through your mail host succesfully.

          None of these attributes can be changed: they are there for
          information purposes only.

        Sent
          Is either Yes, No or Resend.  Yes means the file has been sent.
          No means it hasn't.  Resent means the file has been sent, and a
          resend request for it is pending.  You can alter the state of
          this value by highlighting the field and hitting enter.

        Acked
          Is either yes or no: yes means the remote has received the file
          correctly and Rex is waiting to remove it from the queue.  No
          means either the remote hasn't received the file correctly: it
          may not have been sent, may not have been received, or may have
          been received, but corrupted.

          You can trick Rex into thinking the file has been acknowledged
          by highlighting this field and hitting enter.

        Size


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          67
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

        CRC-32

        Confirmation number

        Part size

        Part CRC-32
          The remaining fields provide more information about the file.
          Size shows how large the whole file in question is.  CRC-32
          shows the 32-bit CRC of the file.  Confirmation number is the
          number Rex will check to uniquely identify this file.

          If the file has been split into parts, you'll also see part size
          and part CRC-32 fields.  These provide the size of the part of
          the file you're looking at, and the CRC-32 of the same.


      3.10.4: Contents List Overview

      This list shows the contents of the packet you selected from the
      main list of packets.  Each file or part of a file in the packet is
      on a line of its own.  The line shows the file's name, size in
      bytes, 32-bit CRC and confirmation number.  The remaining 5 spots
      are either -'s or one of the following letters:

        o S - the file has been sent at least once
        o A - the file has been received correctly by the remote
        o R - the file has been queued to be resent
        o T - the file contains receipt information for the remote
        o P - the file is one part of a multipart file

      You can delete a file from the queue by selecting it and hitting
      the delete key.


      3.10.5: Partial Message Contents List

      This list shows what parts of the multipart file have been
      received, and where they have been stored in the queue.

      You can delete a part of the message by selecting the part and
      hitting the delete key.


                            3.11: Logging options


      Determine what information Rex will store in the log file it
      creates, and just how verbose Rex's log files will be.



      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          68
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      3.11.1: Fatal Errors

      A log entry is created every time something occurs that forces Rex
      to abort processing immediately and close down the program.  This
      would be something like not finding its configuration file, or
      having Ctrl+Break pressed.  These should always be logged.


      3.11.2: Other Errors

      Entries occur when an unexpected error occurs that is serious, but
      can be ignored without affecting the rest of the program.  Something
      like losing the connection to the mail server, or running out of
      disk space for a temporary file.  These should be logged.


      3.11.3: Files Sent/Received

      Every time a file is sent to another node or received from another
      node, an entry is created saying what the file was and who it was
      sent or received from.


      3.11.4: Acks/Receipts

      Every time a receipt for a file is sent or received, if this is
      turned on, that event will be logged.


      3.11.5: General Messages

      These give information on what Rex is doing, command line arguments
      passed, anything which might be of interest to the user.


      3.11.6: Trivial Messsages

      These give the minutiae of what Rex is doing, down to connections
      to with remote servers, etc.  Not really necessary, but
      informative.


      3.11.7: Debug Messages

      If these are turned on, Rex will spew information in huge amounts.
      :)  Everything that the program does will be logged and detailed.
      This is useful if there is a problem with Rex that you can't
      diagnose, and may be helpful in finding what errors are left in the
      program should you happen to stumble on any.



      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          69
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      3.11.8: Logfile Max. Size

      You can have Rex automatically trim the log file it generates by
      passing it the -trim command line argument.  This setting determines
      how large Rex will let the log file get before trimming it.  If it's
      set to 0K, Rex will not trim the log file.

      Note that the larger the value you specify here, the longer it will
      take Rex to trim the log file.  For large values (in the megabytes),
      this can take a little while to do.  For this reason, Rex will not
      trim the log file unless you specify -trim on the command line.


      3.11.9: Autotrim logfile

      If you'd like Rex to trim the logfile every time it's run, you can do
      this by setting Autotrim logfile to yes.  By default, this is set to no,
      as trimming the logfile can take a while for larger logfile sizes.


      3.11.10: Logging mode

      Text files can have two types of end of line strings: one is just a
      carriage return, one is carriage return / line feed.  You can toggle
      between these two end of line types by changing the logging mode to
      either Binary mode (CR) or Text mode (CR/LF).


























      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          70
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                        Section 4: DOS INTERNET SETUP


      To configure the information for the internet setup for DOS, select
      the Internet Setup menu from the main menu, and then select
      Configure SLIP/PPP.

      Most of this setup assumes that your connection to the Internet is
      via dial-up PPP or SLIP.  The DOS portion of Rex includes a script
      executing program to dial up and connect to your provider and a PPP
      packet driver to connect via PPP in such a way that Rex will be able
      to communicate with the rest of the Internet.  Using the information
      you enter here, Rex creates three files: pppd.cfg, rex.scr and
      dial.bat.  pppd.cfg is the configuration file for the PPP driver;
      you shouldn't have to modify this file.  dial.bat is a batch file to
      execute to connect to your provider and transfer mail automatically.
      You may want to change this to match how you want Rex to perform.
      rex.scr is a script useable by Rexdial to connect to your Internet
      provider and start a PPP session.  You'll probably have to edit this
      somewhat in order to connect properly, as there are a huge number of
      ways to connect via PPP, and Rex can only guess as to what you might
      use.  Rex will ONLY write this file if rex.scr DOES NOT ALREADY
      EXIST in the current directory (to avoid overwriting changes to the
      file when you make a small change in your setup).

      If your computer is connected to the Internet via ethernet or some
      other method, Rex can still work.  You will need to find a packet
      driver for your particular interface (a large collection of these is
      available on the web at http://www.crynwr.com/crynwr) and install
      that properly. Once done, fill in the parts of this configuration
      screen that are relevant to your driver (i.e. the lower half of the
      screen).


                               4.1: Init String


      The init string you use to initialize your modem.  | will be
      translated to a carriage return, ^ will raise DTR, v will lower DTR
      and ~ will pause 1 second.


                                4.2: COM Port


      The COM port your modem is on.  Rex will automatically set the
      values for your modem's address and IRQ based on your entry here.
      If you have non-typical values for your modem's address or IRQ,
      you'll have to change the next two entries to reflect the correct
      values.


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          71
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


                                 4.3: Address


      The base address of your COM port.  Typical values for this are:

        COM1:  3F8
        COM2:  2F8
        COM3:  3E8
        COM4:  2E8


                                   4.4: IRQ


      The IRQ of the COM port your modem is operating on.  Typical values
      for this are:

        COM1: 4
        COM2: 3
        COM3: 4
        COM4: 3


                                  4.5: Baud


      The speed at which the computer should communicate with your modem.
      Note that this is NOT the speed of your modem.  Usually a value of
      38400 will do well, but you can go as high as 115200.  This value
      must be a divisor of 115200.

      If you're running with a FOSSIL driver, your COM port is locked at
      some speed, and you plan on using Rexdial, you must set this to the
      speed your COM port is locked at, otherwise Rexdial won't work.


                                 4.6: Vector


      The software interrupt vector of the packet driver you're using.
      Most packet drivers, including the one distributed with Internet
      Rex, install themselves at interrupt 60.  You may need to change
      this if you find that another driver is taking that vector.


                               4.7: IP address


      The IP address you are assigned when you dial your provider.  If
      you have a fixed IP address, you'll have been told what it is by

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          72
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      your provider.  It should be something like 128.127.63.45: 4
      numbers separated by dots.

      If you have a dynamically assigned IP address, as is the case with
      many dial up PPP lines, set this value to 0.0.0.0 and use the getip
      command in your dialup script to get your IP address as it's
      assigned to you.

      You can also pass your IP address to Rex when it is run by using
      the -ip command line switch, or by setting the environment variable
      MYIP to be your IP address.


                              4.8: Network Mask


      Your network mask.  Most providers use 255.255.255.0 as the standard
      network mask.  If this doesn't work for you (i.e. you get cannot
      resolve POP3 hostname), you can also try 0.0.0.0.

      You can override this setting at runtime by specifying your netmask
      in the environment variable NETMASK.


                               4.9: Name Server


      Here you put the IP addresses of whatever nameservers you use: you
      can specify two of them if necessary.  Your provider should have
      given you these addresses.


                               4.10: Login Name


      If your provider uses PPP with PAP authentication, this is your PAP
      username.


                                4.11: Password


      If your provider uses PPP with PAP authentication, this is your PAP
      password.


                              4.12: Phone Number


      This is the phone number you dial to connect to the Internet.


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          73
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


                             4.13: Dial Attempts


      This is the number of times Rex will try to dial your provider
      before giving up.


                             4.14: Socket Timeout


      This is the number of seconds Rex will wait before giving up trying
      to establish a socket connection with a given server.  30 seconds
      should do for most connections, but if yours is especially slow you
      can try raising this.


                              4.15: Data Timeout


      This is the number of seconds Rex will wait for data to be received
      from a given server before giving up.  120 seconds should do for
      most connections, but if yours is especially slow you can try
      raising this.


                                  4.16: MSS


        The MSS (or maximum segment size) sets the largest packet of data that
      can be sent through the packet driver at one time.  (For the technically
      minded, note that this does not include the TCP/IP headers.  MSS is
      roughly 40 bytes less than your MTU / peer MRU.)

        You can set the MSS to any value between 50 and 1450 bytes.  Lower
      speed connections or connections with frequent errors should use a
      smaller MSS to allow for faster correction of data.  The default value
      for MSS, 256 bytes, should be ideal for SLIP or PPP users.  Users of
      ethernet connections should try setting this to a higher value, as
      errors are less frequent on these connections, and the smaller MSS
      means more bandwidth wasted on TCP/IP headers.

        IMPORTANT!  You should NOT set the MSS higher than your network's
      MTU / peer MRU.  Doing so may cause crashes or hangs.  The 32-bit
      version of Rex appears to be more sensitive to incorrectly high MSS
      values than the 16-bit version.  Note that although many packet drivers
      claim to negotiate peer MRU, it is frequently just set to a default
      value of 1500.  Check with your provider to find the correct value.


                               4.17: Use BootP

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          74
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────



      Set this to yes or no depending on whether or not you'd like to have
      your net connection automagically configured via bootp.  Note that in
      order to use this successfully, your packet driver must support bootp
      configuration: if it doesn't and you've turned this on, you'll find
      Rex can't connect to any machines or do nameserver lookups.













































      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          75
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                   Section 5: OS/2 CONNECTION SCRIPT SETUP


      To configure the information for the internet setup for OS/2, select
      the Internet Setup menu from the main menu, and then select
      Configure SLIP/PPP.

      Setting up these values is only necessary if you intend to use the
      RexdialP and Wait programs provided with Internet Rex to call your
      provider.  If you have another means of connecting to the Internet,
      you can leave this alone.

      You can choose to either have Rex write connection scripts with
      the values you define, and save them afterwards, or not write
      connection scripts and not save the values.

      If you choose to let Rex generate a connection script for you, it
      will use the values you enter here to write a .CMD file called
      DIAL.CMD.  You can pass parameters to DIAL.CMD the same as if you
      were passing them to Rexp.exe.  For example:

        DIAL.CMD -f m

      connects you to the Internet and fetches you mail using Rex, then
      hangs up.

      Rexcfg will also write a file called rex.scr which contains a
      script to log on to your Internet provider.  This is a generic
      script that may not work for everyone.  Read the file rexdial.doc
      for more information on how to setup scripts for use with
      RexdialP.exe.


                           5.1: Inactivity Timeout


      Rex can send data across the connection on a regular basis in order
      to avoid having the connection timeout.  Setting the inactivity
      timeout to X seconds will make Rex send data once every X seconds.
      If you set it to zero, Rex will not send any extra data.


                             5.2: Socket timeout


      When connecting to remote sites, Rex will timeout and disconnect if
      data isn't sent properly or received for certain period of time.  By
      default, this is set to 60 seconds, but if you are connecting to sites
      a great distance away, you may need to set it higher in order to ensure
      Rex completes succesfully.  On the other hand, if the site isn't
      responding at all, you'll have to wait that much longer for Rex to

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          76
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      decide that.


                                5.3: COM Port


      The COM port your modem is on.  1 for COM1, 2 for COM2, etc.  You
      can set this to anything between COM1 and COM8.


                                5.4: Baud Rate


      The rate you want the computer to talk to your modem at.  If you're
      running SIO and have locked your modem at a particular rate, that's
      the rate you should enter here.  Otherwise, 57600 is a good choice
      for modems running at 14400 or faster.  Allowable values are from
      100 to 57600 baud.


                               5.5: Init string


      Your modem's init string.  This will be sent to the modem, with a
      few modifications.  |'s will be sent as carriage returns, ^ raises
      the DTR, v lowers the DTR and ~ pauses for 1 second.


                                 5.6: Redials


      The number of times Rex should re-dial your provider before giving
      up.  NO CARRIER's and NO DIAL TONE's won't count as redials: BUSY's
      will.  Set this to 0 to have Rex dial until it connects.


                                5.7: Username


      The username to use when logging on to your provider.


                                5.8: Password


      The password to use when logging on to your provider.


                               5.9: SLIP or PPP



      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          77
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      Set it to the method you'll be using to connect to your provider,
      either SLIP or PPP.


                            5.10: Your IP Address


      If you're using SLIP to connect to the Internet, you must provide
      the IP address of your machine when you're connected to the
      Internet. Your provider should have told you what this address is.


                         5.11: Provider's IP Address

      If you're using SLIP, you must also provide the IP address of the
      machine you'll be connecting to.  This is your provider's IP
      address, and should also have been given to you.



































      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          78
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                     Section 6: WIN95 DIALUP CONNECTIONS


      To configure the information for the internet setup for Win95,
      select the Internet Setup menu from the main menu, and then select
      Configure Dialup Networking.


                             6.1: Socket timeout


      When connecting to remote sites, Rex will timeout and disconnect if
      data isn't sent properly or received for certain period of time.  By
      default, this is set to 60 seconds, but if you are connecting to sites
      a great distance away, you may need to set it higher in order to ensure
      Rex completes succesfully.  On the other hand, if the site isn't
      responding at all, you'll have to wait that much longer for Rex to
      decide that.


                            6.2: Dialup Networking


      Set this to yes if you would like to use Windows 95 or WinNT's
      dialup networking to connect to the net.  If you set this to yes,
      Rex will dialup and connect to your server automatically as
      necessary, and hangup when done.


                                6.3: Auto Dial


      If this is set to yes, Rex will check to see if a connection has
      been made to the configured host, and if it hasn't, will
      automatically dial up the host and connect when it needs to send
      stuff over the net.  If set to no, you will have to establish a
      dialup connection yourself beforehand.  Both auto dial and auto
      hangup can be overridden by running Rex with the -autodial or
      -autohangup command line options.


                               6.4: Auto Hangup


      Set this to yes if you would like Rex to hangup the connection to
      your Internet provider when it's done processing.

      IMPORTANT!  Even if you have this set to no, if Rex is the only
      program left on the connection when it shuts down, it WILL hangup.
      This must be done in order to keep Windows from thinking the modem
      is forever in use from then on.  If you have other programs using

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          79
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      the connection to the net when Rex shuts down, the connection will
      not be lost.


                                 6.5: Redials


      This is the number of times Rex will try to connect to your provider
      if the first connect fails.  Set this to 0 to have Rex dial until it
      connects.


                           6.6: Inactivity Timeout


      Rex can send data across the connection on a regular basis in order
      to avoid having the connection timeout.  Setting the inactivity
      timeout to X seconds will make Rex send data once every X seconds.
      If you set it to zero, Rex will not send any extra data.


                               6.7: Login Name


      Set this to the login name you'd like to use for your connection.
      If left blank, the default Windows login name will be used.


                                6.8: Password


      Set this to the password you'd like to use for your connection.  If
      left blank, the default Windows password will be used.


                               6.9: Connection


      This will present you with a list of the configured dialup
      connections on your PC.  Choose the one you would like Rex to use
      when connecting to the Internet.  If you don't have any listed here,
      you can configure a new connection by choosing the DialUp networking
      folder from the My Computer folder and selecting 'Create new
      connection'.

      The connection name, login name and password can all be overridden
      at runtime using the -dun command line option.





      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          80
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                        Section 7: COMMANDLINE OPTIONS


                         7.1: Rex Commandline Options


      Internet Rex's main executable is either RexP.exe, Rex.exe, Rexd.exe
      or RexW.exe depending on whether you're using OS/2, DOS 16-bit, DOS
      32-bit or Win95/WinNT respectively.   The Linux version is either
      rexls for the SOCKS support vesion, or rexl for the non-SOCKS version.
      The generalized syntax for running Rex is:

        <program> [-send  [mail | dir | ftp | transx | [x]e<email ID> |
                     [x]anonymous | [x]<address>]]
                  [-fetch [mail | dir | ftp | transx | [x]e<email ID> |
                     [x]anonymous | [x]<address>]]
                  [-queue [mail | dir | ftp | [x]anonymous | [x]e<email ID> |
                     [x]<address>]]
                  [-runscript <script filename>...]
                  [-map <map label>]
                  [-processor <niceness level>]
                  [-trim]
                  [[+|-]between.bat]
                  [-help | -notify] [<address(s)> | x<address(s)>]...
                  [-daemon]
                  [[+|-] dun] [<connection> [<username> [<password>]]]
                  [-?]

        If you're running the DOS version, there is also
                  [-ip <IP address>]

        If you're running the Win95/98/NT version, there is also
                  [[+|-]autodial] [[+|-]autohangup]

        <program>
          This is the program for your particular operating system:
          rexp.exe, rex.exe, rexd.exe, rexw.exe, rexl or rexls.

        [-send [mail | ftp | dir | transx | [x]anonymous | [x]e<email ID> |
            [x]<address>]]
          This option lets you specify which nodes you're going to send
          mail to.  If you don't specify anything after -send, Rex will
          send waiting mail to every node.  Otherwise, the nodes you
          specify will have their waiting mail sent to them.
            mail:   send to all nodes who receive files via email
            ftp:    send to all nodes for whom you upload files to an FTP
                    site
            dir:    send to all nodes for whom you toss to a directory
            transx: send TransX shuttle mail
            [x]anonymous:
                    send (or don't send if x is specified) anonymous mail,

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          81
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                    i.e. gated netmail or responses to email FREQs
            [x]e<email ID>:
                    send (or don't send if x is specified) mail to nodes
                    who receive files via email, specifically those who
                    receive files via the email address with the ID given
            [x]<address>
                    send (or don't send if x is specified) mail to the
                    node with the given address.  (Wildcards are allowed.)

            -send mail ftp will send mail to any node connected via email
              or FTP.

            -send 1:342/806 will send any waiting mail for 1:342/806.

          You can specify any number of nodes or general classes of nodes.
          You can also exclude specific nodes from being sent mail by
          placing an x in front of their address.

            -send mail x1:342/* will send mail to any email node, but
              not to nodes in net 1:342
            -send mail xanonymous will send mail to any email node, but
              not to anonymous email addresses

          Note that sending mail is distinct from queueing mail.  Queueing
          mail will scan your netmail/outbound areas and toss any waiting
          mail into Rex's queue, to wait until the appropriate send
          command is issued.  Sending mail actually sends the waiting mail
          to the remote node.

        [-fetch [mail | dir | ftp | transx | [x]anonymous | [x]e<email ID> |
            [x]<address>]]
          This option lets you specify which nodes you'll accept/fetch
          incoming mail from.  If you don't specify anything after -fetch,
          all incoming mail will be fetched from wherever it needs to be
          fetched from.  Otherwise, only the nodes fitting into the
          categories you specify will have their mail fetched.

        [-queue [mail | dir | ftp | [x]anonymous | [x]e<email ID> |
            [x]<address>]]
          This option lets you specify which nodes you'll queue mail for.
          Rex will scan your netmail/outbound area and pick messages or
          files for the nodes which fit into the categories you choose.
          If you don't specify anything after -queue, any message or file
          which would be sent to one of the nodes in Rex's node manager
          will be queued for sending.

        [-runscript <script filename> [<script filename>...]
          Runs the FTP scripts specified by the filenames given.  Note that
          these will not have an FTP site, username or password defined by
          default, so you will have to use the USER/PASS/LOGIN commands to
          connect to the FTP site.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          82
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


        [-map <map label>]
          If you want to use a drive mapping other than the default
          mapping you've setup in Rexcfg, you can specify it using it the
          -map command along with the label you gave the map in the setup
          program.

        [-processor <niceness level>]
          This option lets you override the processor niceness level
          specified in Rexcfg.  Replace <niceness level> with a number
          between 0 and 3.  The higher the number, the more Rex will yield
          the processor to other processes.  Under pure DOS, this value is
          irrelevant as there are no other processes to yield the
          processor to.  (This is not true if you're running a multitasker
          like DesqView.)

        [-trim]
          This option will make Rex trim the log file to the size
          specified in Rex's general behaviour section.

        [[+|-]between.bat]
          Use this command line option to turn on or off the running of
          between.bat when Rex receives mail.  This setting will override
          whatever may have been in Rexcfg beforehand.  Giving
          -between.bat or -b will turn off between.bat processing.  Giving
          +between.bat or +b will turn it on.

        [-help | -notify] [<address(s)> | x<address(s)>]...
          This switch will create RexFix help (for -help) or RexFix status
          (for -notify) messages for the nodes you specify after the switch.  If
          you don't specify any switches, help or notify messages will be sent to
          all nodes in the node manager.
            The addresses can be specified using wildcards.  You can also exclude
          particular addresses by putting an x before them.  For instance,
            -notify 169:* x169:4???/*
          will send notify messages to everyone in the node manager in zone 169,
          except those nodes in region 169:4000.

        [-daemon]
          This will put Rex into daemon mode.  In daemon mode, Rex stays
          running all the time.  It checks the events specified in the event
          manager and at the appropriate time, runs with the command line given
          in that event.
            You can run the config program or another copy of Rex while Rex is
          running in daemon mode, provided Rex is waiting for an event.

        [[+|-]dun [<connection> [<username> [<password>]]]]
            The entire dialup networking setup in Rex can be changed using this
          command line option.  If you want to disable dialup networking completely,
          use -dun.  To enable it (and use whatever settings may be in Rexcfg
          at the time: be careful to be sure there are correct settings), use +dun.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          83
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

            Windows users can also specify up to three more words after +dun.  The
          first of these will be interpreted as a new connection to use (instead of
          the one in Rexcfg).  The second will be taken as the username to use while
          logging in, and the third as the password.  You don't need to specify all
          of these, only enough to override the values you want.  Any options not
          specified will have their values taken from Rexcfg.
            If any of the values you specify have spaces in them, be sure to put
          double quotes (") around them, otherwise they won't be interpreted
          correctly.

            +dun "University of Alberta"
            will enable dialup networking using the connection labelled University
          of Alberta.  The username and password used will be taken from Rexcfg.

            +dun MyConnection MyUsername MyPassword
            will enable dialup networking, using the connection MyConnection, the
          username MyUsername and the password MyPassword.

        [-?]
          Giving this argument will cause Rex to list the arguments it
          accepts.  If you give this argument after one of the others Rex
          understands, Rex will give help for the specific argument.  For
          example:
            -send -? will give you help on the -send argument.

      DOS users also have the following option:

        [-ip <IP address>]
          You can override the IP address Rex might have configured from
          the dialup program, or specify one if you haven't already, by
          passing this command line argument.  You should give a standard
          internet IP address after the -ip command:
            -ip 129.128.2.241

      Win95/98/NT users also have the following options:

        [[+|-]autodial]
        [[+|-]autohangup]
          If you want to override the settings in Rex's dialup networking
          for autodialing or autohanging up, you can do so using these
          options.  Using +autodial or +autohangup will turn the options
          on: -autodial or -autohangup will turn them off.

      All of the options can be shortened: you need only specify a string
      long enough to uniquely identify the option you're giving.  For most
      options, one letter will do.  (-autodial and -autohangup are the
      only ones which require more than one letter.)

      The fetch, send and queue arguments can be consolidated so that the
      options following them apply to all the arguments.


      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          84
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      If no command line arguments are given, Rex will run as if it had
      been passed the arguments -send -fetch -queue.

      Here are some example command lines:

        rex -queue -send
          Scans your netmail/outbound queue and sends all the outgoing
          mail.

        rex -sendqueue
          Does the same as rex -send -queue.  The arguments were
          consolidated.

        rex -sq
          Does the same as rex -send queue.

        rex -fetchsendqueue 1:342/806
          Fetches, queues and sends mail for 1:342/806: complete
          processing for that node.


                       7.2: Rexcfg Commandline Options


      Internet Rex's configuration program is called either Rexcfg.exe,
      Rexcfgd.exe, Rexcfgp.exe, Rexcfgw.exe or rexcfgl, depending on
      whether you're running DOS 16-bit, DOS 32-bit, OS/2, Win95/98/NT
      or Linux respectively.

      The configuration program can take a couple of arguments, as
      follows:

        <program> [-stats [reset]] [-dates] [-nodelist] [-original]
                  [-monochrome]

      If no arguments are given, Rexcfg starts up in the standard,
      full-screen interactive setup mode.

        [-stats [reset]]
          If you give the -stats argument, Rexcfg will dump the file
          transfer statistics for all the nodes setup currently to a file
          called STATS.TXT.  If you specify -stats reset, Rexcfg will
          reset the transfer statistics of all the nodes once it's
          finished dumping them.

        [-dates]
          Similar to the -stats command, this tells Rex to put all the
          information about the dates nodes last had mail sent, received
          or queued.  Statistics are put in the DATES.TXT file.

        [-original]

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          85
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

          Tells the configuration program to use the original colour
          scheme for this run.

        [-monochrome]
          Tells the configuration program to use the monchrome colour
          scheme for this run.

        [-nodelist]
          Specifying -nodelist on the command line will cause Rexcfg to
          create a file called NODELIST.TXT, containing all the pertinent
          information about the nodes currently configured in Rex.

      Any of the command line arguments can be shortened to one
      distinguishing letter.  For example:

        rexcfg -stats reset is equivalent to rexcfg -s r




































      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          86
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                               Section 8: TERMS


                      8.1: Full Name or Internet Address


      When specifying a machine on the Internet, you can provide either
      the machine's name, or its IP address.  Machine names may contain
      both letters and numbers: IP addresses contain only numbers.  For
      example:

        Machine names: mail.myhost.com
                       smtp.somewhere.ca
        IP addresses:  129.128.127.125
                       24.108.2.12

      Your provider will usually provide you with the machine names of
      your POP3 and SMTP hosts.  Nameserver addresses will be in IP
      address form (since they are used to translate machine names into IP
      addresses).


                           8.2: File Locking (FTP)


      One problem that frequently occurs when transferring files to and
      from FTP sites is having two programs trying to access files at the
      same time.  For example, while someone is logged on to the FTP site
      uploading files, there may be a program on the FTP site trying to
      move those files elsewhere to be processed.  In order to avoid
      losing files because of this access problem, a good solution is to
      setup locking on the FTP site.

      The "standard" way of doing this is to have the FTP administrator
      setup a unique directory for each user of the site.  This home
      directory has subdirectories where the user can upload and download
      files.  A sample user directory might look something like:

        bill
        +-inbound
        +-outbound

      where bill is Bill's home directory, and inbound and outbound are
      subdirectories.  To lock his directories while uploading and
      downloading files, Bill places a file in his home directory before
      uploading, and deletes the file when he's done.  The FTP site checks
      Bill's home directory before processing any files he might have
      uploaded: if there's a file in the directory, it doesn't process
      stuff because it knows Bill is online uploading or downloading.
      Similarly, the FTP site can leave a file in Bill's home directory
      when it's tossing files to let Bill know that he should wait for a

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          87
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      bit before proceeding with his file transfers.

      Because Rex can act as both the FTP client and the program which
      scans directories on the FTP server, locking has been setup for both
      FTP uploads and downloads and directory uploads and downloads.


                          8.3: Compatability in Rex


      In order to be compatible with FrontDoor (under Internet Rex), a
      mailer must:

        o Store incoming and outgoing netmail in a Fido style *.MSG
          message
        o Create FDINSESS.* semaphores while in a session with a remote
          node (used in multinode setups only)

      Rex will create FDRESCAN.NOW semaphores when done scanning the
      netmail area for a FrontDoor compatible system.

      In order to be compatible with Binkley (under Internet Rex), a
      mailer must:

        o Store outgoing mail in the Binkley standard outbound format
        o Create *.BSY semaphores while in a session with a remote node
          (used in multinode setups only)


                            8.4: Acks and Receipts


      The Internet has evolved from a few computers connected through a
      high speed network to a huge web of nodes from around the world in
      a few short years.  Although it has evolved to meet the needs of the
      increased load it is bringing in, there are still a number of flaws
      inherent in the way it transfers information.

      The methods used by Internet Rex, or indeed by any program
      accessing the net, are subject to the guidelines imposed by the
      various Internet standards in use.  For the moment, only a few of
      these standards have any method of guaranteeing a correct
      transmission.  Although it is getting rarer to lose mail messages
      completely or to have FTP transmissions mangled, it does still
      happen on occasion.  The Internet is NOT a RELIABLE means of
      transport.  To rectify this, Rex can use a system of manifests and
      receipts to ensure that files sent through the net appear at the
      other end in one piece, with all the bits in the right order.
      Manifests specify the projected contents of a transmission
      (filenames, checksums, etc.) and receipts are returned by the
      received to indicate succesful or unsuccesful receipt of the files

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          88
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

      in the manifest.

      Manifest/receipts are by no means required for any link: most
      connections are reliable enough to work without the need for Rex's
      extra level of reliability.  However, if you need to be 100% certain
      your data is getting through to the other end correctly,
      manifests/receipts should be used.


                            8.5: Full Paths, etc.


      For any directory or file in Rex's configuration, you are usually
      required to specify the full path to the file.  This includes the
      drive letter at the start of the file's name.  For example:

        e:\mail\uucp\

      Rex will not accept filenames or paths which are over 80 characters
      long.  This is to keep it compatible with all operating systems.

      After specifying a directory, Rex will usually check to make sure
      the directory you've given actually exists.  To do this, it first
      applies any drive mappings you may have setup, and then checks the
      disk.  If the directory isn't found, you'll be prompted to create
      it.  Be wary of leaving directories uncreated: Rex will not run
      unless the directories you've specified are present.


                                8.6: Standards


      Internet Rex is designed to be compatible and compliant with the
      following Internet, Fidonet and other miscellaneous technical
      standards:


      8.6.1: Internet RFC standards

        RFC 821
          The Simple Mail Transfer Protocol (SMTP).  Communication with
          mail servers.

        RFC 822
          This describes the proper format for an email message.  Rex
          implements an additional X- field, X-Mailer.

        RFC 959 and 1123
          The File Transfer Protocol (FTP).  Describes the minimal command
          set required for implementation on FTP servers and the proper
          method of transferring files.  Rex uses the STOR, RETR, CWD,

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          89
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

          PASV, PORT, USER, PASS, TYPE, MODE, NLST, MKD, RMD, DELE and
          QUIT commands.  The ALLO, REIN, REST, SIZE and STOU commands are
          used on servers that support them.

        RFC 1939
          The Post Office Protocol version 3 (POP3).  How to retrieve mail
          from mail servers.  Rex uses the USER, PASS, STAT, RETR, DELE
          and QUIT commands.  Where the server supports them, the TOP and
          APOP commands are also used.

        RFC 2045, 2046, 2047, 2048, 2049, 2183
          A description of the MIME mail transfer standard.  This includes
          descriptions of Base 64 encoding, proper headers for
          international character sets, multi-part messages and more.
          RFC 2183 describes the Content-Disposition header line for MIME
          messages.


      8.6.2: Fidonet Standards

        FTS-0001
          Specification for the creation and exchange of messages in an
          FTN compatible network.  In particular, specifies the format for
          Fido style *.MSG messages and for type 2 mail packets.

        FSC-0045
          Specifies the format for type 2.2 mail packets.

        FSC-0048
          Specifies the format for type 2+ mail packets.


      8.6.3: Miscellaneous Standards

        FIDS (Fidonet/Internet Distribution System)
          A standard developed by Hector Santos for incorporating FTN
          information into RFC 822 compliant messages so that Fido file
          attaches can be sent over email. Rex is FIDS compliant, both for
          reading and writing messages.  Rex uses the X-FIDS-Agent,
          -Fido-From, -Fido-To, -File-Name, -File-Size and -File-CRC
          headers when generating FIDS compatible messages.

          Hector Santos can be reached at [e-mail].

        SEAT (Simple Email Attachment Transfer)
          SEAT is an open mail transport standard for moving Fido style
          messages and files over email.  It was developed by a number of
          contributors in the Sysop's TechNet echo STN.STANDARDS, and is
          meant to be a reliable, easy to use method for attaching files.
          Rex uses the SEAT standard when sending messages in its native
          format and is SEAT level 4 compatible with SEAT001.004.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          90
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


          For more information on SEAT, contact Brent Shellenberg at
          [e-mail] or join the SEAT mailing list by sending
          mail to [e-mail] with the line 'subscribe seat'
          in the body of the message.

        Allfix
          Versions of Allfix higher than 5.00 incorporate a transport
          method for Fido style messages over email.  It offers some
          advantages, and some disadvantages over other methods.  Rex
          makes full use of the specs released in the Allfix developer's
          package for version 5.00 and can read and write Allfix style
          messages.

          Information about Allfix can be obtained from http://www.allfix.com.

        Packet 2000
          Packet 2000 is a design for a new, year 2000 compatible format for
        transporting messages over Fido technology networks.  Like SEAT, it was
        developed through the input of a number of contributors from the STNet
        echo STN.WG.DEV and Fido's NET_DEV and FTSC_PUBLIC echos.
          For more information on Packet 2000, contact Brent Shellenberg at
        [e-mail] or visit the Sysop's TechNet webpage at
        http://stnnet.home.ml.org.

        BinkP 1.0
          BinkP was developed as a replacement to simply trying to pump FTN
        style mailer connections over a telnet line.  It is designed as a true
        Internet protocol for exchanging files between automated mailers.  Its
        source is the BinkD mailer daemon for Binkley outbounds.


      If you would like more details on making your program compliant
      with Rex under any of these standards, you are encouraged to contact
      the author.

















      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          91
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                         Section 9: ENCODING METHODS


      Internet email has evolved so that it can only reliably transmit a
      certain set of characters without the risk that they will be changed
      to some other character along the way, or that they might be lost
      altogether.  Because standard files on your hard drive usually don't
      have all their bytes in this 'invariant' set, any program sending
      files over email has to translate from the format files are stored
      on disk with to a format that can be sent through mail.  To this
      end, a few different formats have appeared:


                         9.1: Base 64 (MIME encoding)


      This is the format used by most mailers, including, amongst others,
      Eudora, Netscape and Fido2Int.  Usually if you can attach files to
      your email, this is the format they'll be sent in.  Files sent with
      this format can usually be recognized by the headers that preceed
      the file itself: there should be a line starting with Content-Type,
      and one starting with Content-Transfer-Encoding.  MIME was designed
      from its outset to be transfer invariant, and hence, safe to be sent
      through any mail gateway.  MIME encoding (or Base 64 encoding) is
      described in the Internet RFC 2045.


                               9.2: UUencoding


      This is an older format popular mostly on UNIX machines as part of
      UUCP's file transfer protocol.  Its character set is not transfer
      invariant, but will pass through all but the most obscure gateways
      without problems.  You can identify files encoded with this transfer
      method by a line beginning with begin ### <filename>, where ### is
      some number.


                               9.3: XXencoding


      Designed as a replacement for UUencoding, XXencoding is transfer
      invariant.  XXencoding was made to allow a number of different
      possible translations (indeed, UUencoding could be viewed as a
      subset of XXencoding).  It does this using charset and table lines
      before the begin line used in UUencoding.  Although it is a better
      translation method than UUencoding, XXencoding is not seen anywhere
      near as often as UUencoding.


                                  9.4: FIDS

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          92
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────



      FIDS (Fidonet Internet Distribution System) is a standard developed
      by Hector Santos (Plantinum Xpress/Silver Xpress) for use with FTN
      to Internet transport agents such as Internet Rex.  It provides a
      method for encoding information about the Fido messages in the
      header fields of RFC 822 compliant email messages.  FIDS compatible
      mailers can interpret these headers and reconstruct the Fido
      messages and their attached files, regardless of which mailer sent
      the original message.  There are currently only two FIDS compatible
      mailers available that the author knows of: Internet Rex and PXFIDS.
      Nevertheless, as the Internet becomes a more viable alternative for
      transferring mail, there are sure to be more such mailers appearing.


                                 9.5: TransX


      TransX encoding is a proprietary encoding used in the program TransX,
      created by Multiboard Communications.  The method itself does not
      currently have a publicly released standard; Internet Rex considers the
      messages generated by versions of TransX which have been superceeded as
      defining a standard for those versions.  As TransX 2.6 is the current
      version and it superceeded TransX 1.5, the messages which Rex generates
      are based against the standard of messages generated by TransX 1.5.



























      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          93
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                           Section 10: FTP COMMANDS


      Rex FTP scripts have the following macros built in:

        %min     expands to the current minute (0-59)
        %hour    expands to the current hour (0-23)
        %wday    expands to the current day of the week
                 (Sunday = 1, Monday = 2, etc.)
        %mday    expands to the current day of the month (1-31)
        %status  the return status of the last command
                 (commands generally set %status to 0 or higher if succesful,
                  less than zero if an error occurred)

      Rex FTP scripts can use any of the following commands:

        CD <directory>
          Change to the specified directory on the FTP site

        CREATE <filename>
          Creates a 1 byte file with the specified filename.  Used for
          making lockfiles.

        CHECK <wildcard> [<wildcard> <wildcard> ...]
          Check for any file in the current directory matching the
          wildcards specified.  The CHECK command can be followed by an
          EXCEPT command.  The CHECK command (or its EXCEPT command if
          there is one) must be followed by a FOUND command which will
          tell the script what to do if there is a file which matches.

        EXCEPT <wildcard> [<wildcard> <wildcard> ...]
          If the EXCEPT command is put after a DEL or CHECK command, any
          files which matched the wildcards in the DEL or CHECK command
          and which also match the EXCEPT's wildcards will NOT be included
          in the delete or check.

        FOR <variable> IN <wildcard> [<wildcard>...]
        LFOR <variable> IN <wildcard> [<wildcard>...]
          [commands]
        END
          The FOR and LFOR constructs run through the list of files you specified
          using the wildcards and execute the instructions between FOR and END.
          This is done once for each file in the list of matching files: each
          time it's done, the variable you give is filled with a different file
          name.  The FOR command fills the variable with the names of files in
          the current directory of the FTP server.  The LFOR does the same thing
          with files in the current directory on the hard drive.  For example,
          you could download and scan files from an FTP site like this:
            LGET *
            LFOR file IN *
              RUN scan.exe %file

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          94
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

            END
          FOR and LFOR commands can be nested.

        GOTO <label>
          Use this command to jump to another point in the script.  You define a
          label in the script the same way you would a label in a DOS batch file,
          by putting the label name followed by a colon (:) on a line by itself.
          For instance:
            IF ERRORLEVEL >= 0
              (do some stuff)
            ELSE
              GOTO END
            ENDIF

            (do some more stuff)
            END:
            ; The end of the script is here
          You can't use GOTO to jump into the middle of a FOR loop that wasn't
          already active when the label was defined.

        IF <conditional>
          [commands]
        [ELSE IF <conditional>
          [commands]]...
        ELSE
          [commands]
        ENDIF
          The IF-ELSE-ENDIF "command" lets you do some branch in your script,
          based on the conditional you give.  The conditional can either test
          for the existence or non-existence of files, or look at the errorlevel
          a command run from the DO command returned.  The valid conditionals
          are:
            EXIST <wildcard> [<wildcard>...]
            LEXIST <wildcard> [<wildcard>...]
            NOTEXIST <wildcard> [<wildcard>...]
            LNOTEXIST <wildcard> [<wildcard>...]
            ERRORLEVEL [== | >= | <= | > | <] <number>
            string [== | != | >= | <= | > | <] string
          EXIST and NOTEXIST test for the existence of files matching the
          wildcard(s) you gave in the current directory of the FTP site.  LEXIST
          and LNOTEXIST test for the existence of files matching the wildcard(s)
          given in the current local directory (as set by the LCD command).  The
          ERRORLEVEL conditional compares the errorlevel returned by the DO
          command with the number you give.  The last conditional compares the
          strings on the left and the right of the == or != signs to see if
          they're equal (==) or not equal (!=): use this to test values of
          variables or parameters.  If both strings are numbers, <=, >=, > and <
          can be used to compare the size of the two numbers.
            For instance, if the file LOCK was on the FTP site in the current
          directory, and your script read
            IF EXIST LOCK

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          95
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

            PUT FILEONE*
            ELSE
            PUT FILETWO*
            ENDIF
          then, the files matching FILEONE* that were queued for the current
          node would be sent.  If LOCK wasn't there, the files matching
          FILETWO* would be sent.  IF-ELSE-ENDIF commands can be nested, up to
          10 levels deep.  You can also have repeat IF-ELSE-IF-ELSE-IF...
          commands.  For example:
            IF EXIST UPLOAD1
            PUT FILES1*
            ELSE IF EXIST UPLOAD2
            PUT FILES2*
            ELSE IF EXIST UPLOAD3
            PUT FILES3*
            ENDIF

        GET <wildcard> [<wildcard> <wildcard> ...]
        GETDEL <wildcard> [<wildcard> <wildcard> ...]
        RGET <wildcard> [<wildcard> <wildcard> ...]
        RGETDEL <wildcard> [<wildcard> <wildcard> ...]
          Downloads files in the current directory which match the given
          wildcards.  If auto-delete is turned on, each file is deleted
          from the remote site once it has been succesfully downloaded.
            RGET and RGETDEL additionally download all the files in the
          subdirectories of the current directory on the FTP server.  All the
          files are put in the current inbound directory: no new subdirectories
          are created.  GETDEL and RGETDEL delete files or directories from the
          FTP server regardless of the current auto-delete setting.

        LCD [<directory>]
          Changes the current directory for downloads.  If no directory is
          given, the appropriate inbound directory is used.

        LDEL <wildcard> [<wildcard> <wildcard> ...]
          Deletes the files given in the wildcards from the current directory.
          Note that there is no path resolution: you can't specify directories
          in the wildcards.

        LGET <wildcard> [<wildcard> <wildcard> ...]
        LGETDEL <wildcard> [<wildcard> <wildcard> ...]
        RLGET <wildcard> [<wildcard> <wildcard> ...]
        RLGETDEL <wildcard> [<wildcard> <wildcard> ...]
          Downloads files in the current directory on the FTP server to the
          current local directory.  If auto-delete is turned on, each file is
          delete from the remote site once it has been succesfully downloaded.
            The RLGET and RLGETDEL commands also download the subdirectories
          of the current local directory and create new directories on the
          hard drive to put them in.  The LGETDEL and RLGETDEL force deletion
          of the remote files or directories once they've been downloaded,
          regardless of the auto-delete setting.

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          96
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────


        LOGIN <FTP site>
          Logs you in to the FTP site given using the username specified in the
          USER command and the password given by the PASS command.  If USER
          wasn't set, it defaults to anonymous.  If PASS wasn't set, it defaults
          to your first email address, or if you haven't entered any email
          addresses, your name.  (Note that the latter may not work at some FTP
          sites.)  You can specify a port to connect to by adding a colon to
          the end of the FTP site's name, then adding the port.  For example:
            LOGIN ftp.somewhere.com:2100
          would log in to the FTP server running on port 2100 of
          ftp.somewhere.com.
            If you are already logged in to another FTP site, the LOGIN command
          first logs you out of that site.

        LOGOUT
          Logs you out of the FTP site you're currently logged in to.  Not
          strictly necessary, as Rex will log you out of the current site before
          trying to log into another one, and closes any FTP connections once
          sending to FTP nodes is done, but here for the sake of having a
          complete set of commands.

        LPUT <wildcard> [<wildcard> <wildcard> ...]
        LPUTDEL <wildcard> [<wildcard> <wildcard> ...]
        RLPUT <wildcard> [<wildcard> <wildcard> ...]
        RLPUTDEL <wildcard> [<wildcard> <wildcard> ...]
          Uploads files from the current directory on the hard drive to the
          current directory on the FTP site.  The RLPUT and RLPUTDEL commands
          additionally upload the files in the subdirectories of the current
          directory, creating new directories on the FTP site.  The LPUTDEL
          and RLPUTDEL commands additionally delete the files (or directories)
          once they've been uploaded.
            You cannot use ant of the LPUT commands in a script setup in the
          Toss From FTP menu.

        LWAIT <wildcard> [<wildcard> <wildcard> ...]
          This waits until there are no files matching the given wildcards in
          the current directory of the hard drive.  If there is a timeout set
          for FTP, it will wait until the timeout is over, then abort the
          transfer.  If no timeout is set, it will wait indefinitely.

        MIRROR [column]
        RMIRROR [column]
          The MIRROR command updates the current directory to reflect the
          contents of the FTP directory.  This means files that are present
          but older or a different size than the ones on the FTP site will be
          replaced with the versions on the FTP site.  Note that this `doesn't``
          apply to directories: to have Rex update subdirectories (and their
          subdirectories, and their subdirectories, etc.), use the RMIRROR
          command.
            The optional parameter for this command is the column (number of

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          97
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

          characters from the left of the screen) where the files' group is
          located.  This should be the column of text to the left of the files'
          sizes.  If the FTP server is reasonably well behaved, you shouldn't
          need this option, but some servers don't use the usual format for
          listing files in long form: for those cases the option will be
          needed.

        MKDIR <directory name>
          Creates the directory of the specified name in the current
          directory.

        PASS <password>
          Specifies the password to be used the next time the LOGIN command is
          called.  The scope of the PASS command is limited to the script or
          script file it's called in.

        PUT [<wildcard> <wildcard> <wildcard> ...]
          This will upload the mail the destination node is getting to the
          current directory.  This command can only be used in scripts which
          upload files to the remote site.  If no arguments are given, all
          files waiting for the current node are sent.  Otherwise, only those
          files matching the wildcards given are sent.  `IMPORTANT!  `Be sure
          to either have at least one PUT command which sends all remaining
          files, or make sure that the wildcards you give will match ALL
          POSSIBLE outbound mail for the node, otherwise files may remain in
          the queue indefinitely.

        QUIT
          This aborts the FTP script immediately.

        QUOTE <command>
          The command given is sent to the FTP server directly.  Rex does no
          interpretation of the command, and ignores any return codes.  Note
          that since there is no interpretation of the command, wildcard
          commands (like DEL *, GET *.*, etc.) will not match against the
          wildcards.

        RETURN [errorlevel]
          This aborts the current script and returns to the one that called it.
          If this is issued in the main script, the connection is aborted.
            You can optionally add an errorlevel to this command.  Upon return
          to the higher script, that scripts errorlevel will be set to the value
          you returned.

        RMDIR <directory name>
          Removes the directory of the specified name in the current
          directory.

        RUN <command> [<arguments>]
          Runs the command given in separate shell.  The errorlevel the program
          returns is captured and can be tested for using the IF ERRORLEVEL

      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          98
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

          commands.  A negative errorlevel indicates there was a problem running
          the command.

        SCRIPT <file name> [<parameter>...]
          Opens the file pointed to by <file name> and runs it like a script.
          Lines not beginning with a letter of the alphabet are ignored.  (Spaces
          at the start of a line are ignored.)  You can call other scripts from
          within a script file.  Scripts can return a testable errorlevel using
          the RETURN command.
            After the name of the file to run, you can pass in parameters to a
          script.  These values will be available within the script using the
          macros %1, %2, %3, etc., where %1 represents the first parameter.

        UPDATE <wildcard> [<wildcard>...]
        RUPDATE <wildcard> [<wildcard>...]
          This command provides a means of maintaining a current version of a file
          or directory from an FTP site.  Using UPDATE, any of the files on the
          FTP site which match the wildcards given will be updated to the current
          local directory.  This means that if a more recent or changed version
          of the file is listed on the FTP site, it will be downloaded over the
          current file.  UPDATEing a directory is equiavlent to changing to
          that directory and issuing a MIRROR command.
            RUPDATE is similar to UPDATE except that when applied to directories,
          the directory's subdirectories will also be updated to the hard drive.

        USER <username>
          Specifies the username to be used the next time the LOGIN command is
          called.  The scope of the USER command is limited to the script or
          script file it's called in.

        WAIT <wildcard> [<wildcard> <wildcard> ...]
          This waits until the files matching the wildcards given are no longer
          present in the current directory of the FTP server.  If you have a
          timeout set for FTP connections, it will wait that long, then abort,
          otherwise, it will wait indefinitely.

















      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden          99
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                Section 11: EMAIL FORWARDING/PERSONAL GATEWAY


      Internet Rex can convert your netmail into email messages for those
      using Rex under POP3/SMTP or UUCP.

      Any netmail written to the gateway address setup in Internet Setup
      will have the subject and to fields used to write an email message.
      For instance, if you had the gateway address 1:342/806.1 setup and
      you wrote a message to [e-mail], 1:342/806.1, the text
      of the message would be made into an email message to
      [e-mail].  The message will come from the
      username/domainname email address you specified in the Email Setup.

      If the email address you want to write to is too long to fit in a
      standard netmail header, you can write the message to Internet Rex
      at your gateway address, and put the email address in a To: line in
      the first line of the message.  The To: line MUST be the first line
      of the message in order for this to work.

      Files can be sent in this way too: simply create a standard file
      attach netmail and send it to the person you want.  The files and
      the text attached will be sent in separate messages.

      Finally, Rex can also interpret CC: and BCC: lines at the top of
      the message (though each must contain only email addresses).  So if
      you sent a message to [e-mail] and the first lines were:

        CC: [e-mail], [e-mail]
        BCC: [e-mail]

      Sally and Tom would receive the same message, as would Bill (though
      Joe, Sally and Tom wouldn't know Bill had been sent the message).
      An advantage to using this system is that the message will only be
      uploaded once, not once for each person.

















      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden         100
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                      Section 12: CC EMAIL FILE ATTACHES


      CC email file attaches is a feature currently only available in
      Internet Rex and Fido2Int.  While scanning your mail queue for outbound
      files and mail, Rex keeps track of the various files being sent.  If the
      same file is being sent to multiple nodes, Rex might be able to CC the
      message to one node to another node.  The message only gets uploaded to
      the server once, but it goes to two or more different people.  Conditions
      do have to be right for this to happen though.  Specifically, for mail for
      one node to be CCed to another:
        - if you have more than one email address setup in Rex, you must use
          the same address to send mail to both nodes
        - the file being sent must be exactly the same for each node
        - the two nodes must use the same transfer method (SEAT, MIME/none) and
          encoding (UUencode, MIMEencode, etc.)
        - the chunk sizes for the two nodes must be the same
        - if the nodes are using a reliable connection, the settings for
          "Accept resend requests", "Purge delay" and "Auto-resend" in the
          Connection information menu must be the same
        - the nodes cannot be using Allfix, TransX or FIDS - these transport
          methods cannot work with CC email
        - the encryption for the two nodes must match: either they must be
          using no encryption, or the encryption methods and passwords must be
          the same
        - if the nodes are using the SEAT transport, the session passwords must
          also match
        - the subjects for the two nodes need not be the same, but it is
          recommended that they be similar, in case the receiving nodes are
          using subject to screen out mail

      These conditions may seem restrictive at first, but as many connections
      don't support encryption those settings will often match.  As many also
      don't use session passwords in email, those will probably also match.
      Applying a little organisation to nodes can arrange that reliable
      connection settings match across many nodes, and so on for the rest of
      the settings.















      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden         101
      Internet Rex v1.16 Documentation
      ────────────────────────────────────────────────────────────────────

                         Section 13: TROUBLESHOOTING


                 13.1: FIDS Messages and Reliable Connections


      You've configured this node to send FIDS compatible messages and
      setup a reliable connection (accept resend requests, send
      acknowledgements or both).  Unfortunately, the FIDS standard does
      not currently support reliable connections: although the settings
      you've entered are acceptable, the messages created won't have the
      information needed to send acknowledgements or accept resend
      requests, so the advantages these offer will be lost.  You can hit
      "Yes" to continue with these settings, or "No" to go back and change
      them.


                                13.2: ViaMail


      Internet Rex doesn't interact directly with ViaMail, as trying to
      read/write directly to its queues would require rather complex
      code, and ViaMail itself already offers an easier way.  For each
      node you would like Rex to export mail for, setup the node in
      ViaMail's node manager.  In the echomail options for the node, under
      Output format/mode, select Raw PKT/Alt path or Compressed PKT/Alt
      path, and choose a directory for Alternate mail path.  Now, setup
      the same node in Rex's node manager, and in Mailbox directory put
      the directory you selected for alternate mail path.

      It is very important that you allow ViaMail to export the mail to
      the given path, and not have other programs move attached files or
      netmails.  Otherwise, the messages will remain in ViaMail's queue
      and will have to be purged manually.


















      ────────────────────────────────────────────────────────────────────
      (c) Copyright 1997-1999 Khan Software and Charles Cruden         102