PC Online 1997 March/PCO3_97.ISO/filesbbs/dos/mcm10.arj/MCMAIL.DOC

Text File | 1996-11-15 | 210.8 KB | 5,402 lines

                                                            │
                                                           ─·───
              ┌────┬────┌──────┌────┬────┌────────┌────┌────┐
              │    │    │   ┌──│    │    │  ────  │    │    │
              │  │   │  │   └──│  │   │  │  ┌──┐  │    │    └──┐
              └──┴───┴──└──────└──┴───┴──└──┘  └──└────└───────┘
                                 Version 1.0

        Copyright (C) 1994-1996 by Albert Freriks and Gordian Schuermann
                              ALL RIGHTS RESERVED

      ────────────────────────────────────────────────────────────────────

                      The HYDRA protocol was designed by
                Arjen G. Lentz, LENTZ SOFTWARE-DEVELOPMENT and
                            Joaquim H. Homrighausen
                 COPYRIGHT (C) 1991-1993; ALL RIGHTS RESERVED

      ────────────────────────────────────────────────────────────────────

                   Documentation (C) 1996 by Vincent Danen

      McMail v1.0                                        TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────


      Section 1: Introduction .......................................... 2
        1.1  Legal Disclaimer .......................................... 2
        1.2  Distribution .............................................. 3
        1.3  License ................................................... 3
        1.4  Files in the Distribution Archive ......................... 3

      Section 2: Getting Started ....................................... 5
        2.1  Minimum System Requirements ............................... 5
        2.2  How McMail Handles Mail ................................... 6
          2.2.1  The Outbound Directory ................................ 6
            2.2.1.1  ?LO Files ......................................... 7
            2.2.1.2  ?UT Files ......................................... 7
            2.2.1.3  REQ Files ......................................... 7
          2.2.2  Multiple Zones ........................................ 7
          2.2.3  4D Points ............................................. 8
        2.3  Commandline Parameters .................................... 8
        2.4  Environment Variables ..................................... 9
        2.5  Semaphore Files ........................................... 9
        2.6  Files Used or Created by McMail .......................... 11
        2.7  Batchfiles ............................................... 12
        2.8  Converting from ARCmail Systems .......................... 12

      Section 3: MCMAIL<task>.CFG ..................................... 14
        3.1  Macros ................................................... 14
        3.2  Environment Variables .................................... 15
        3.3  Keyword Definitions ...................................... 15
        3.4  Modem Keyword Definitions ................................ 16
          3.4.1  ComPort .............................................. 16
          3.4.2  Baudrate ............................................. 16
          3.4.3  PortLocked ........................................... 16
          3.4.4  NoFossil ............................................. 16
          3.4.5  FosHot ............................................... 17
          3.4.6  UseFifo <#> .......................................... 17
          3.4.7  ComReadSize <#> ...................................... 17
          3.4.8  ComWriteSize <#> ..................................... 17
          3.4.9  FosDebugline [last] .................................. 17
          3.4.10  FosDbglineChar <char> ............................... 17
          3.4.11  SlowModem ........................................... 17
          3.4.12  CommandDelay <#> .................................... 17
          3.4.13  SlowDisk ............................................ 18
          3.4.14  NoModem ............................................. 18
          3.4.15  ModemReset <string> ................................. 18
          3.4.16  ModemInit <string> .................................. 18
          3.4.17  Terminalinit <string> ............................... 18
          3.4.18  ModemDeInit <string> ................................ 18
          3.4.19  ModemAnswer <string> ................................ 18
          3.4.20  ModemHangup <string> ................................ 18
          3.4.21  ModemReject <string> ................................ 19
          3.4.22  RejectResponse <string> ............................. 19
          3.4.23  ModemBusy <string> .................................. 19

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                   i
      McMail v1.0                                        TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

          3.4.24  ModemDial <string> .................................. 19
          3.4.25  ModemSuffix <string> ................................ 19
          3.4.26  ModemOk <string> .................................... 19
          3.4.27  ModemInfo <string> .................................. 19
          3.4.28  ModemIgnore <string> ................................ 20
          3.4.29  MaxRinging <#> ...................................... 20
          3.4.30  RingCounter <default> [v1] [s1] [v2] [s2].. ......... 20
          3.4.31  RingTimer <#> ....................................... 20
          3.4.32  WaitCarrier <#> ..................................... 20
          3.4.33  CallCollision ....................................... 20
        3.5  Modem/FAX Keyword Definitions ............................ 21
          3.5.1  FaxResponse <string> ................................. 21
          3.5.2  FaxLevel <#> ......................................... 21
          3.5.3  AfterFax <string> .................................... 21
        3.6  Modem/Voice Keyword Definitions .......................... 22
          3.6.1  VoiceResponse <string> ............................... 22
          3.6.2  VoiceLevel <#> ....................................... 22
        3.7  Modem/External-Mail Keyword Definitions .................. 22
          3.7.1  ExternalMail <string> <errorlevel> ................... 22
        3.8  BBS Keywords ............................................. 23
          3.8.1  BBSLevel <#> ......................................... 23
          3.8.2  BBSBanner <filename> ................................. 23
          3.8.3  InEventBanner <filename> ............................. 23
          3.8.4  WaitBBSCaller <#> .................................... 23
          3.8.5  NoBBSNext ............................................ 23
        3.9  Terminal Mode Keyword Definitions ........................ 24
          3.9.1  DefaultIEMSI <string> ................................ 24
          3.9.2  +ExtTerminal <#> or <file> ........................... 24
          3.9.3  PhoneBook <file> ..................................... 24
        3.10  Path/Filename Keyword Definitions ....................... 24
          3.10.1  +EventFile <filename> ............................... 25
          3.10.2  +Outbound <dir> ..................................... 25
          3.10.3  FaxOutbound <dir> ................................... 25
          3.10.4  +Inbound <dir> ...................................... 25
          3.10.5  +SecureInbound <dir> ................................ 25
          3.10.6  +UnKnownInbound <dir> ............................... 25
          3.10.7  +FaxInbound <dir> ................................... 25
          3.10.8  +DownloadPath <dir> ................................. 25
          3.10.9  +NetMail <dir> ...................................... 25
          3.10.10  +PersMail <dir> .................................... 25
          3.10.11  +RouteInfo <filename> .............................. 26
          3.10.12  +Semaphore <dir> ................................... 26
          3.10.13  +DefTransDir <dir> ................................. 26
          3.10.14  TranslatFile <filename> ............................ 26
        3.11  Nodelist Keyword Definitions ............................ 26
          3.11.1  +Nodelist <dir> ..................................... 26
          3.11.2  Version7 ............................................ 26
          3.11.3  OldStyle ............................................ 26
          3.11.4  V7Flags <flag> <flag> ... ........................... 26
          3.11.5  V7NodeFlags ......................................... 27
          3.11.6  Domain <name> <index> <zone> ........................ 27

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  ii
      McMail v1.0                                        TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

          3.11.7  MaxCallBaud <#> ..................................... 28
          3.11.8  MinCallBaud <#> ..................................... 28
          3.11.9  NoCallFlags <string> ................................ 28
          3.11.10  OnlyCallFlags ...................................... 28
          3.11.11  FlagTrans <nodeflag> <dialprefix> <dialsuffix> ..... 28
          3.11.12  NoNodelist ......................................... 28
        3.12  Site Information Keyword Definitions .................... 29
          3.12.1  AKA <address> ....................................... 29
          3.12.2  AkaMatching ......................................... 29
          3.12.3  Sysop <name> ........................................ 29
          3.12.4  Site <string> ....................................... 29
          3.12.5  Location <string> ................................... 29
          3.12.6  MaxSpeed <#> ........................................ 29
          3.12.7  Flags <string> ...................................... 29
          3.12.8  Phone <string> ...................................... 29
          3.12.9  Ticker <string> ..................................... 30
          3.12.10  TimeZone <#> ....................................... 30
          3.12.11  Dial <string> <new string> ......................... 30
        3.13  Cost Keyword Definitions ................................ 30
          3.13.1  +CostDatFile <filename> ............................. 30
          3.13.2  CostTimeOffset <#> .................................. 31
          3.13.3  FosChargeUnit <#> ................................... 31
          3.13.4  NoFosCharge ......................................... 31
          3.13.5  Currency <dec-del> <tho-del> <div> <dec-dig> ........ 31
          3.13.6  Scottishmode <#> .................................... 31
        3.14  Mail Keyword Definitions ................................ 31
          3.14.1  +MailFlag <filename> ................................ 31
          3.14.2  MailExitExt <def> ................................... 32
          3.14.3  ScaredMode .......................................... 32
          3.14.4  PWOverride .......................................... 32
          3.14.5  HandshakeFailureTries <#> ........................... 32
          3.14.6  SessionFailureTries <#> ............................. 32
          3.14.7  NoCarrierTries <#> .................................. 32
        3.15  InfoText Keyword Definitions ............................ 32
          3.15.1  +KnownInfoText <filename> [nodedef1] .. ............. 33
          3.15.2  +ProtectInfoText <filename> [nodedef1] .. ........... 33
          3.15.3  +UnknownInfoText <filename> [nodedef1] .. ........... 33
        3.16  File Request Keyword Definitions ........................ 33
          3.16.1  +RequestCfg <filename> .............................. 33
          3.16.2  +RequestFooter <filename> ........................... 33
          3.16.3  +FailedReqFooter <filename> ......................... 33
          3.16.4  +NoRequestBanner <filename> ......................... 34
          3.16.5  MaxSearchTime <#> ................................... 34
          3.16.6  UnknownReqTime <#> .................................. 34
          3.16.7  UnknownReqSize <#> .................................. 34
          3.16.8  KnownReqTime <#> .................................... 34
          3.16.9  KnownReqSize <#> .................................... 34
          3.16.10  ProtectReqTime <#> ................................. 34
          3.16.11  ProtectReqSize <#> ................................. 34
          3.16.12  FirstMatch ......................................... 34
          3.16.13  NoRequestOnUs ...................................... 34

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                 iii
      McMail v1.0                                        TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

          3.16.14  +ReqProcessor <exe> <cmdline> ...................... 35
        3.17  Log Keyword Definitions ................................. 35
          3.17.1  LogLevel <chars> .................................... 36
          3.17.2  ScrLogLevel <chars> ................................. 36
          3.17.3  SpcLogLevel <chars> ................................. 36
          3.17.4  +LogFile <filename> ................................. 36
          3.17.5  +SpcLogFile <filename> .............................. 36
          3.17.6  +CostLogFile <filename> ............................. 36
          3.17.7  +ErrLogFile <filename> .............................. 36
          3.17.8  +TerminalCap <filename> ............................. 36
          3.17.9  ShortLog ............................................ 36
          3.17.10  MaxHistory <#> ..................................... 36
        3.18  Environment Keyword Definitions ......................... 37
          3.18.1  Environment <string> ................................ 37
          3.18.2  SliceDuringTransfer [dynamic] ....................... 37
          3.18.3  DvTaskSwitch ........................................ 37
        3.19  External File Keyword Definitions ....................... 37
          3.19.1  +PktViewer <file> ................................... 37
          3.19.2  +BBSViewer <file> ................................... 37
          3.19.3  +DoorSys <file> ..................................... 38
          3.19.4  +BBSKick <file> ..................................... 38
        3.20  Protocol Keyword Definitions ............................ 38
          3.20.1  NoHydra ............................................. 38
          3.20.2  NoRH1 ............................................... 38
          3.20.3  NoDZA ............................................... 38
          3.20.4  NoZAP ............................................... 38
          3.20.5  HydraBlockLen <#> ................................... 38
          3.20.6  HydraTxWin <#> ...................................... 38
          3.20.7  HydraRxWin <#> ...................................... 38
          3.20.8  HydraNoBell ......................................... 38
          3.20.9  HydraTELENET ........................................ 39
          3.20.10  HydraCTLCHRS ....................................... 39
          3.20.11  HydraXONXOFF ....................................... 39
          3.20.12  HydraHIGHCTL ....................................... 39
          3.20.13  HydraHIGHBIT ....................................... 39
          3.20.14  HydraCANBRK ........................................ 39
          3.20.15  HydraCANASC ........................................ 39
          3.20.16  HydraCANUUE ........................................ 39
          3.20.17  HydraCRC32 ......................................... 39
          3.20.18  HydraDEVICE ........................................ 39
          3.20.19  +ExtDnProtocol <file> .............................. 39
          3.20.20  +ExtUpProtocol <file> .............................. 40
        3.21  Node Data Keyword Definitions ........................... 40
          3.21.1  NodeData <nodeaddress> <pw> <phone> <flags> ......... 40
          3.21.2  NodedataFile <file> ................................. 40
        3.22  Function Key Keyword Definitions ........................ 40
          3.22.1  KeyF? <menu title>,*<errorlevel> .................... 41
          3.22.2  KeyF? <menu title>,[#]<path\filename> [<parameters>]  41
          3.22.3  KeySF? *<errorlevel> ................................ 41
          3.22.4  KeySF? [#]>path\filename> [<parameters>] ............ 41
        3.23  Miscellaneous Keyword Definitions ....................... 41

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  iv
      McMail v1.0                                        TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

          3.23.1  NoMailFlash ......................................... 41
          3.23.2  NoPersMailScan ...................................... 41
          3.23.3  NoBusyScan .......................................... 41
          3.23.4  NoRoute ............................................. 41
          3.23.5  MinDrvSpace <drive> <minbyte> ....................... 42
          3.23.6  NoRemoteScreen ...................................... 42
          3.23.7  NoTransferSize ...................................... 42
          3.23.8  KbdLock <password> .................................. 42
          3.23.9  NoSound ............................................. 42
          3.23.10  AlertSound <#> ..................................... 42
          3.23.11  ScreenBlank <#> [BLANK] ............................ 42
          3.23.12  VideoMode <#> ...................................... 42
          3.23.13  AliveTime <#> ...................................... 42
          3.23.14  StartUpScanDelay <#> ............................... 43
          3.23.15  +Include <file> .................................... 43
          3.23.16  TaskKey <string> ................................... 43
          3.23.17  Color <string> ..................................... 43

      Section 4: MCMAIL<task>.EVT ..................................... 45
        4.1  Event Lines .............................................. 45
          4.1.1  Tag .................................................. 45
          4.1.2  Days ................................................. 45
          4.1.3  Start ................................................ 46
          4.1.4  End .................................................. 46
          4.1.5  ME - Mail Errorlevel ................................. 46
          4.1.6  SE - EventStart Errorlevel ........................... 46
          4.1.7  RD - Random Outbound Call ............................ 46
          4.1.8  RT - Busy Retries .................................... 46
          4.1.9  CST - Cost Matching .................................. 46
          4.1.10  FL - Event Flags .................................... 47
        4.2  Extra Commands ........................................... 48
          4.2.1  ToDo ................................................. 48
          4.2.2  Deny/Except .......................................... 49

      Section 5: Enhanced NodeData Configuration ...................... 51
        5.1  NodeData ................................................. 51
          5.1.1  Sysop <string> ....................................... 51
          5.1.2  System <string> ...................................... 51
          5.1.3  Password <string> .................................... 51
          5.1.4  Phone <string> ....................................... 51
          5.1.5  Flags <flags> ........................................ 51
          5.1.6  Prefix <string> ...................................... 52
          5.1.7  Suffix <string> ...................................... 52
          5.1.8  MaxAKAs <#> .......................................... 52
          5.1.9  ZoneMatch <string> ................................... 52
          5.1.10  TaskKey <string> .................................... 52
          5.1.11  Capability <string> ................................. 53
          5.1.12  OutDir <path> ....................................... 53
          5.1.13  InDir <path> ........................................ 54
          5.1.14  CostLog <filename> .................................. 54
          5.1.15  InfoID <string> ..................................... 54

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                   v
      McMail v1.0                                        TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

          5.1.16  InfoSize <#> ........................................ 54
          5.1.17  CCBSize <#> ......................................... 54
          5.1.18  FaxFwdID <string> ................................... 54
          5.1.19  FaxFwdAttr <string> ................................. 55

      Section 6: File Request Configuration ........................... 56
        6.1  Trash-Data ............................................... 56
        6.2  Magicnames ............................................... 56
        6.3  Path Definitions ......................................... 57
        6.4  The Index File ........................................... 58
        6.5  Including Other Configurations ........................... 59
        6.6  External Request Processors .............................. 59

      Section 7: Route Configuration .................................. 60

      Section 8: Modem Response Translation File ...................... 62

      Section 9: Costing Table ........................................ 63

      Section 10: McMail Nodelist-Indexer ............................. 67

      Section 11: Terminal Phonebook .................................. 69
        11.1  BBS-System <string> ..................................... 69
          11.1.1  Sysop <string> ...................................... 69
          11.1.2  Password <string> ................................... 69
          11.1.3  Phone <string> ...................................... 69
          11.1.4  Prefix <string> ..................................... 69
          11.1.5  Suffix <string> ..................................... 69
          11.1.6  Capability <string> ................................. 69

      Section 12: Running McMail ...................................... 71
        12.1  The Batchfile ........................................... 71
        12.2  McMail Main Screen ...................................... 71
          12.2.1  Settings/Flow ....................................... 71
          12.2.2  Whats On Hold ....................................... 72
          12.2.3  Last Sessions ....................................... 73
          12.2.4  Out- Sessions ....................................... 73
          12.2.5  In - Sessions ....................................... 74
          12.2.6  MultilineInfo ....................................... 74
          12.2.7  Online Keys ......................................... 75
          12.2.8  Status Line ......................................... 76
        12.3  The Outbound Manager .................................... 77
        12.4  Dumb Terminal ........................................... 77
        12.5  BBSNext ................................................. 78
        12.6  Miscellaneous Information ............................... 78

      Section 13: McMail LineViewer ................................... 80
        13.1  Online Keys ............................................. 80

      Section 14: McMail Intertask-Patcher ............................ 82


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  vi
      McMail v1.0                                        TABLE OF CONTENTS
      ────────────────────────────────────────────────────────────────────

      Section 15: Errors and Errorlevels .............................. 83

      Section 16: Conclusion .......................................... 84
        16.1  Registration Sites/Help Systems/Support ................. 84
        16.2  Getting Help ............................................ 86
        16.3  Special Thanks .......................................... 87
        16.4  Acknowledgements ........................................ 88













































      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                 vii
      Section 1                                               INTRODUCTION
      ────────────────────────────────────────────────────────────────────

                           Section 1: INTRODUCTION


      McMail is a complete frontend mailer system and it can perform a lot
      of important functions, some of which are:

       ■ FTN-compatible mailer for DOS
       ■ Full FTS-1 support with Modem7/TeLink/SeaLink CRC and CKS Send
         and Receive
       ■ Binkleystyle outbound
       ■ Internal netmail and file routing
       ■ Full-featured outbound manager
       ■ Support for up to 256 AKAs (in and out)
       ■ HYDRA file transfer protocol with chat
       ■ VERY flexible cost calculation
       ■ Node-specific cost logging
       ■ Support for up to 99 lines
       ■ Full visual line control from one station in Multiline
         environments
       ■ Log file scrolling
       ■ Definable log levels for both screen and file
       ■ Fast FileREQuest access via its own index files
       ■ ASCII configuration files or a setup program copyright by Klaus
         Winkler
       ■ Supports the V7 nodelist index
       ■ External nodelist compiler for short index files and multiple
         nodelist searches
       ■ Nodelist lookup
       ■ Runs without a nodelist if you do not need one
       ■ Direct CLASS 2 and CLASS 2.0 fax receive or via external programs
       ■ Fax forwarding
       ■ Runs with its own Asyncroutines or uses a Fossil driver
       ■ Special outbound and inbound functions
       ■ External Request-Processor interface
       ■ Direct support for cFos/Pro CCB-Mode
       ■ Full featured terminal with IEMSI, phone book, Zmodem, Hydra, and
         external protocols


                            1.1: Legal Disclaimer


      The authors make no warranties of any kind, express or implied,
      including, without limitation, any warranties of merchantability
      and/or fitness for a particular purpose.  Furthermore, the authors
      shall not be liable for any damage to data or property which may be
      directly or indirectly caused by the use of McMail v1.0 or any of
      its tools.  In no case will the authors be liable for any damages,
      including lost profits, or for any claim by any other party.  We
      only guarantee McMail will occupy disk space.


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                   2
      Section 1                                               INTRODUCTION
      ────────────────────────────────────────────────────────────────────


                              1.2: Distribution


      This version of McMail may be freely distributed in its original
      form with all files.  No user may modify McMail or this document in
      any way.  No fee, charge, or other compensation may be accepted or
      requested without prior written permission of the authors.

      McMail may not be included as part of any software library which is
      distributed on a commercial basis without prior written permission
      from Gordian Schuermann and Albert Freriks.


                                 1.3: License


      Version 1.0 is a release version of McMail, copyright by Gordian
      Schuermann and Albert Freriks.

      You may use this version of McMail under the following conditions:

       1) You are not allowed to alter or recompile McMail.
       2) You understand that McMail is neither freeware nor public
          domain software.  It is shareware, meaning that you must
          register McMail after a test period as described under 3.
       3) This version of McMail may be used unregistered for a test
          period of 60 days.  After this time you must register McMail
          if you wish to continue using it.
       4) Your registration of any prior gamma version of McMail covers
          the use of McMail 1.x as well.
       5) Gordian Schuermann and Albert Freriks are in no way obligated to
          provide future versions of, or support for, McMail.
       6) We regret that we cannot guarantee a faultless running of
          McMail.  Also, we cannot guarantee that McMail does no harm to
          your system, although we test it thoroughly.
       7) McMail may not be used in any unlawful or illegal manner.

      If you do not agree with one or more conditions as stated above, you
      are not permitted to use McMail.


                    1.4: Files in the Distribution Archive


          MCMAIL  .EXE - The main program executable
          MCMAIL  .OVR - The overlay data
          MCMAIL1 .CFG - Configuration file for task 1
          MCMAIL1 .EVT - Event configuration file for task 1
          MCMNODE .EXE - The nodelist compiler
          MCMNODE .CFG - Configuration file for McM-Node

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                   3
      Section 1                                               INTRODUCTION
      ────────────────────────────────────────────────────────────────────

          REQUEST .CFG - File request configuration file
          ROUTE   .MCM - Routing configuration file
          MCMPINT .EXE - Inter-task patch program
          MCMVIEW .EXE - Multi-line browser
          VIEWRA  .EXE - BBS viewer for RemoteAccess
          MCMREQIX.EXE - Filebase indexer
          MCMTYPES.PAS - Developer's information
          REGISTER.GER - Registration form for Germany
          REGISTER.INT - International registration form
          BUG     .REP - Bug report sheet.  Please use this if you have
                         problems.  Please send it as the body of a
                         netmail message, not a file attach!
          MCMFAX  .INF - Information about McMail and FAX-receiving
          MCMCFOS .INF - Information about McMail and cFos
          MCMAIL  .DOC - Hmmmm....
          FILE_ID .DIZ - ...




































      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                   4
      Section 2                                            GETTING STARTED
      ────────────────────────────────────────────────────────────────────

                          Section 2: GETTING STARTED


      Welcome to the world of mail and file exchanges.  This is a world of
      bits and bytes, but most importantly, communication.  You are
      reading this documentation now for one reason or another, but no
      matter what that reason is, you have picked up one of the single
      best frontend mailer systems to be had.  Be prepared for the
      experience of a lifetime.

      You already know what McMail can do.  But perhaps you don't know why
      it does what it does.  You've picked it up for a reason, so let's
      explore that a little more.

      Perhaps you're a sysop who has just setup a board and have heard the
      words "mailer" and "frontend" floating around and this was the first
      you found, but you really don't know what to do with it, or why you
      even have it.  Perhaps you've been doing the networking thing for a
      while now, but need something a little more powerful than what
      you're using.  Perhaps you're just curious and have nothing better
      to do...  It doesn't matter.  You now have power at your fingertips.

      McMail sends and receives mail.  There are two kinds of mail in the
      networking world.  Netmail and echomail.  Netmail is much like
      "email" on a BBS system and is, more or less, private mail between
      one sender and one receiver.  Echomail is like public mail, and
      although you may send it to one specific person, it is "echoed"
      around the world in international conferences and everyone can read
      it and anyone can reply to it.  McMail exchanges these two types of
      mail with other frontend mailer systems like itself.  This is the
      basis for echomail networks.  However, there can be more to it as
      well.  McMail, and other mailers, are capable of sending files to
      and from each other.  They are sent or received at your command, or
      another sysop's command.  But this isn't all!  McMail can receive
      FAX messages as well.  No need to go out and buy an expensive fax
      machine if you don't have to, as long as you have a fax capable
      modem.  McMail can receive your faxes for you, and much more.

      Sounds interesting, doesn't it?  Well, you've made a good choice in
      the mailer you have chosen.  Not only is McMail cost effective, but
      it is also reliable and stable.  Simple to setup and maintain, you
      couldn't ask for a better mailer.  Read on, and we'll setup McMail
      together.


                       2.1: Minimum System Requirements


          Hardware:

          8086 processor,

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                   5
      Section 2                                            GETTING STARTED
      ────────────────────────────────────────────────────────────────────

          360Kb of available base memory,
          1.5 Mb of free space for the install,
          35 Kb of free space (per task) for temporary files,
          Hayes-Compatible modem.

          Software:

          MS-DOS v3.0 or PC-DOS v3.0 or later,
          OS/2 v2.1 or later,
          Fossil software like X00 or BNU if you run McMail as a
            frontend for a BBS,
          Fossil software like cFos for internet connectivity


                         2.2: How McMail Handles Mail


      McMail uses the BinkleyStyle Outbound mail method.  If you are
      familiar with BinkleyTerm or similar mailers and know how they
      work, you can skip this section.  If not, continue on.  Mail is
      handled quite differently from FrontDoor and other mailers.


      2.2.1: The Outbound Directory


      McMail requires a main outbound mail directory in order to function.
      Let's say your network address in FidoNet was 1:342/52 and you
      defined C:\MCMAIL\MAIL\OUT as your main outbound address.  This
      directory will contain three kinds of files, each of which tell
      McMail something different.  The three kinds of files are ?LO files,
      ?UT files, and REQ files.  These files share the same naming
      convention so as to tell McMail where they are to be sent, and how.
      The filename for 1:342/52 would be:

          01560034.*

      It is named like this because the naming scheme calls for the first
      four characters in the name to display the NET number (in hex) and
      the last four characters are the NODE number (in hex).  Therefore,
      1:342/52 has the hex equivalent of 156 for Net 342, and 34 for Node
      52.

      ?LO and ?UT files are subject, however, to mail "flavours".  These
      are what tell McMail how to send the mail, and there are five
      different flavours:

          I   Immediate, send this file right away no matter what
          C   Crash, send this file right away if the receiver is CM
              (Continuous Mail)
          N   Normal, send in an event that is not CM only

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                   6
      Section 2                                            GETTING STARTED
      ────────────────────────────────────────────────────────────────────

          F/O Direct, send in an event that is not CM only with no routing
          H   Hold, only send if the receiver calls to pick it up


      2.2.1.1: ?LO Files


      This file contains a list of files to send to a particular node,
      with one file per line, including the full path and filename.
      Before the path and name of the file, there might be a certain
      character, and this tells McMail how to treat the file.

          ^   This tells McMail that the file is to be deleted after it
              has been sent.

          #   This tells McMail that the file is to be truncated to zero
              bytes after it has been sent.

          ~   This tells McMail that the file was sent, but the connection
              was terminated before all of the listed files were sent.
              This file will not be resent, however.


      2.2.1.2: ?UT Files


      These files are uncompressed mail bundles (or .PKT files).  This is
      typically netmail to be sent out.  They use the same naming
      convention as ?LO files.


      2.2.1.3: REQ Files


      This is a list of files to request from the node, one filename per
      line.  If a password is needed to request a file, it will be placed
      after the filename with a ! before it:

          THISFILE.RAR !PASSWORD

      This would request THISFILE.RAR with the password of PASSWORD.


      2.2.2: Multiple Zones


      We know that the outbound directory holds your mail.  However, it
      doesn't hold all of your mail.  Since the files are sorted by nets
      and nodes, it only stands to reason that the outbound directory
      tells McMail what zone the net and node belongs to.  Your main
      address, or AKA, is the zone for your main outbound directory.  If

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                   7
      Section 2                                            GETTING STARTED
      ────────────────────────────────────────────────────────────────────

      your main address is 1:342/52, your main outbound directory,
      C:\MCMAIL\MAIL\OUT holds all mail for zone 1.  So what if you were in
      another network that was zone 141?  What McMail does, is make
      another outbound directory for the other zone, and it does it in hex
      as well.  For zone 141, the outbound directory would be
      C:\MCMAIL\MAIL\OUT.08D.

      Because of this, it is VERY important that your mail tosser and
      McMail are in sync, in terms of addresses.  If you have 1:342/52
      defined in McMail as your main address, you cannot have 141:500/0
      defined as your main address in your mail tosser (ie. FastEcho).  If
      you define 1:342/52 as your main address in McMail, it MUST be
      defined as your main in your mail tosser.  This way things won't get
      confused, otherwise you may loose mail.


      2.2.3: 4D Points


      McMail has a unique way of dealing with your points.  We already
      know that each zone has its own directory, and within those
      directories are files that specify what net and node certain mail
      must go to.  Nowhere in that setup, however, are points mentioned.

      A point off of 1:342/52 would be addressed as 1:342/52.1 for the
      first point.  What McMail does is create another directory off of
      the zone directory, in this case, C:\MCMAIL\MAIL\OUT.  The directory
      takes the same format as the files, as in NNNNnnnn.PNT where NNNN is
      the net and nnnn is the node (all in hex).  So the directory for a
      point off of 1:342/52 would be C:\MCMAIL\MAIL\OUT\01560034.PNT and
      an uncompressed netmail bundle for 1:342/52.1 would be 00000001.OUT.


                         2.3: Commandline Parameters


      McMail is called in the following manner:

          MCMAIL.EXE <task> [<param>] [<param>] [<param>] ...

      where

          <task> is the specific task to start McMail in.  For example
          "MCMAIL 2" would start McMail for task 2.  The default task is
          1.

      the optional parameters are as follows:

          NOMODEM       - McMail does not access the modem (used for
                          testing purposes)
          NOEMS         - Disables EMS memory usage for the overlay and

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                   8
      Section 2                                            GETTING STARTED
      ────────────────────────────────────────────────────────────────────

                          swapping
          NOXMS         - Disables XMS memory usage for the overlay and
                          swapping
          NOUMB         - Disables UMB memory usage for overlay buffering
          NOBUFCHK      - Disables the Transfer/Receive-Buffer checking at
                          startup
          JMPEVT        - Forces McMail to jump directly to the actual
                          current event, and ignores forced events that
                          have yet to be executed
          WAIT          - Wait for two seconds at startup
          /C:<filename> - Forces McMail to use a specific configuration
                          file instead of the default
          NOVELL        - Use this if you have trouble with
                          "NCB-Directory-Searchlimits" under Novell
                          Netware


                          2.4: Environment Variables


      McMail can use the following environment variables.  These can be
      set by a batchfile or AUTOEXEC.BAT upon startup of your computer.

          MCM     - The path to McMail's home directory.  If it isn't set,
                    McMail uses the startup directory.
                    Ie. SET MCM=C:\MCMAIL
          MCMOVR  - The path to McMail's overlay data file MCMAIL.OVR.
                    Set this to a RAM disk for faster or access, or use
                    EMS memory.  If the OVR isn't found here, McMail/
                    McMView will look in the executable path.
                    Ie. SET MCMOVR=E:\
          MCMTMP  - The path to where McMail can create temporary files.
                    Ie. SET MCMTMP=C:\TEMP
          MCMSCR  - The path to where McMail can create its screen image
                    for multi-line viewing.
                    Ie. SET MCMSCR=C:\MCMAIL\MULTI


                             2.5: Semaphore Files


      Semaphore files are zero-byte files that tell McMail important
      information.  These files are especially useful in multi-line
      environments, however many are useful in single-line environments as
      well.  With McMail, <task> is a number without prior zeros (ie.
      for task 1, TASK.<task> would be TASK.1).  Errorlevels, however, do
      have prior zeros, so an errorlevel of 80 when calling
      MCMEXT<task>.<errorlevel> would produce MCMEXT1.080.

          TASK.<task>               - Created by McMail, it shows that a
                                      session in task <task> is running

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                   9
      Section 2                                            GETTING STARTED
      ────────────────────────────────────────────────────────────────────

          MCMRUN.<task>             - Created by McMail, it shows that
                                      McMail task <task> is up and
                                      running.  This file will be touched
                                      every three minutes
          MCMBBS.<task>             - Created by McMail, it shows that a
                                      human caller has been passed on to
                                      the BBS.  For RA sysops, a file
                                      called MCM<task>.BBS is also created
          MCMFAX.<task>             - Created by McMail, it shows that a
                                      FAX session is running
          MCMVOC.<task>             - Created by McMail, it shows that an
                                      external voice program is running
          MCMDEX.<task>             - Created by McMail, it shows that the
                                      DialExit function is executed
          MCMTRM.<task>             - Created by McMail, it shows that the
                                      external terminal function is
                                      running
          MCMSLEEP.<task>           - Created by McMail, it shows that the
                                      task has been stopped by a
                                      MCMHOLD.<task> semaphore
          MCMEXT<task>.<errorlevel> - Forces McMail task <task> to exit
                                      with errorlevel <errorlevel>
          MCMSCAN.<task>            - Forces McMail to perform an outbound
                                      scan for task <task>
          MCMSCAN.ALL               - Forces McMail to perform an outbound
                                      scan for all tasks
          MCMHOLD.<task>            - McMail task <task> kills this file
                                      and creates MCMSLEEP.<task>.  McMail
                                      task <task> then closes all open
                                      files and does nothing until
                                      MCMSLEEP.<task> is erased
          MCMROUTE.<task>           - Forces McMail to perform netmail
                                      routing for task <task>
          MCMROUTE.ALL              - Forces McMail to perform netmail
                                      routing for all tasks
          MCMNET.<task>             - Forces McMail to perform a personal
                                      mailscan for task <task>
          MCMNET.ALL                - Forces McMail to perform a personal
                                      mailscan for all tasks
          MCMWOH.<task>             - Forces McMail to update the "What's
                                      on Hold" data for task <task>
          MCMWOH.ALL                - Forces McMail to update the "What's
                                      on Hold" data for all tasks
          CLRIN.<task>              - Clears the inbound-flow data
          CLROUT.<task>             - Clears the outbound-flow data
          CLRCOST.<task>            - Clears the cost-value data
          CLRBBS.<task>             - Clears the BBS-calls data
          CLRFEV.<task>             - Clears the FEV-calls data (FAX-
                                      External-Voice)
          CLRALL.<task>             - Clears all flowdata for task <task>
          MCMNOREQ.<task>           - Forces McMail to not process any

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  10
      Section 2                                            GETTING STARTED
      ────────────────────────────────────────────────────────────────────

                                      file requests for task <task>
          MCMNOBBS.<task>           - Forces McMail to disallow all human
                                      callers for task <task>


                     2.6: Files Used or Created by McMail


      There are a number of files that McMail will create to contain
      specific information or that McMail needs FOR specific information.

          MCMAIL<task>.CFG    - Configuration file for task <task>
          MCMAIL<task>.EVT    - Event configuration file for task <task>
          MCMAIL<task>.FLW    - McMail's flowdata for task <task>.  This
                                file can be erased to set all flowdata to
                                zero
          MCMAIL<task>.NOD    - The compiled node data.  This file is
                                created every time McMail starts
          MCMAIL<task>.BBS    - The compiled phonebook data.  This file is
                                created every time McMail starts
          MCMAIL<task>.SCD    - The compiled data on the current event
          MCMAIL<task>.SET    - The last status of the History-Window
          MCMAIL<task>.INH    - The Inhistory information for task <task>
          MCMAIL<task>.OUH    - The Outhistory information for task <task>
          MCMAIL.INT          - The Intercom file (line information)
          MCMAIL.BXF          - The Bad Transfer information file
          MCMAIL.WOH          - The "What's on Hold" information file
          MCMAIL<task>.RUT    - The file request response PKT file
                                (created temporarily by McMail)
          MCMAIL<task>.INF    - The special outdirectory file information
                                PKT (created temporarily by McMail)
          MCMAIL<task>.SCR    - The screen image of task <task>
          MCMROUTE.NOW        - Created by McMail if any task is routing
                                netmail
          MESSAGE.MCM         - A plain ASCII textfile.  If this file is
                                placed in a special out directory, it will
                                be appended to the information file
                                MCMAIL<task>.INF (see section 5.1.12)
          REMINF<task>.DAT    - FrontDoor-compatible remote information
                                file
          SRIF.$<task>        - This is the Standard-Requestprocessor-
                                Information-File
          ????????.-??        - A call semaphore, placed in the outbound
                                directory
          ????????.$??        - A busy mark semaphore, placed in the
                                outbound directory
          ????????.&??        - An undialable mark semaphore, placed in
                                the outbound directory
          ????????.#??        - A handshake failure mark semaphore, placed
                                in the outbound directory


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  11
      Section 2                                            GETTING STARTED
      ────────────────────────────────────────────────────────────────────


                               2.7: Batchfiles


      McMail creates a few batchfiles depending on what the current
      inbound call to your mailer is.  There are names as follows:

          BBSBAT<task>.BAT    - Normal BBS caller
          FAXBAT<task>.BAT    - External FAX receiver
          VOCBAT<task>.BAT    - External voice receiver
          DEXBAT<task>.BAT    - Exit on DialExit
          TRMBAT<task>.BAT    - Exit on BBSnext

      The contents of these batchfiles are always the same, regardless of
      which one is created:

          SPAWN???.BAT <task> <com> <DTEspeed> <lspeed> <noBBS> <cnt> <el>

      where

          SPAWN???.BAT is either ??? = BBS, FAX, VOC, DEX, NXT
          corresponding to the created batchfile

          <task> is the task number

          <com> is the comport number

          <DTEspeed> is the DTE speed connect

          <lspeed> is the actual line speed connect

          <noBBS> is the number of minutes to the next NoBBS event

          <cnt> is the extra connect add-ons (ie. V32/LAPM/MNP)

          <el> is the errorlevel of the exit


                     2.8: Converting from ARCmail Systems


      McMail has a very easy and convenient way for you to convert from
      your ARCmail system (FrontDoor, InterMail, etc.) to a binkley-style
      outbound in a matter of seconds.

      After your basic setup is completed, follow these few steps.
      Assuming that you have a different netmail area from your previous
      mailer:

          a)  Go into your main McMail configuration file and change the
              netmail directory to your old netmail directory (using the

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  12
      Section 2                                            GETTING STARTED
      ────────────────────────────────────────────────────────────────────

              Netmail keyword).

          b)  Now load McMail using your main batchfile.  Press "B" to
              bundle/route netmail.  This will bundle up your *.MSG
              netmail files and, because they have the file attach bit
              set, McMail will update your .FLO files to include the file
              attaches.  You now have bundled ARCmail messages and McMail
              knows about the file attaches (ARCmail) and will send them.

          c)  Go back into your main McMail configuration file and change
              the netmail directory back to your new netmail directory.

      That's all it takes.  Extremely simple, easy, and efficient.







































      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  13
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

                         Section 3: MCMAIL<TASK>.CFG


      This is the main configuration file for McMail.  This is what drives
      your frontend mailer and tells it what to do, when, and why.  Each
      task must have its own configuration file, so for task 3, you would
      use MCMAIL3.CFG.


                                 3.1: Macros


      The main configuration file can use a few different macros.  The
      macros are as follows:

          $T    - The task number
          $P    - The com port number used
          $S    - The current port's linespeed
          $L    - The current port's lockspeed
          $U    - The ASCII taglist for uploads in terminal mode
          $D    - The path defined under "DownLoadPath"
          $G    - The path and filename defined under "LogFile"
          $M    - The task number of the highlighted task in the
                  multi-line information screen

          *DD   - The current day (two digits)
          *MM   - The current month (two digits)
          *YY   - The current year (two digits)
          *WW   - The week of the year (two digits

                  You must shutdown McMail at midnight if you use this
                  stuff!

          =FAX  - The full path and name of a received FAX
          =UNX  - The current time in UNIX format (in hex, 8 characters)

          =PA   - Remote primary address (zone:net/node[.p]; [.p] only if
                  it is not zero)
          =BR   - The current baudrate on the line (not DTE)
          =IO   - Inbound call or outbound call ("INBOUND" or "OUTBOUND")
          =RL   - Remote location
          =RN   - Remote system name
          =RS   - Remote sysop name
          =RP   - Remote phone number
          =RF   - Remote flags
          =PW   - Remote session-level password
          =SU   - Protected or unprotected session ("SECURE" or
                  "UNSECURE")
          =ST   - The session type ("EMSI", "WAZOO", or "OTHER")
          =LS   - The node type ("LISTED" or "UNLISTED")


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  14
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

          =FL   - Filename of the incoming file request list file
          =PFL  - Full path and filename of the incoming file request list
                  file
          =XL   - Filename of the Filexmit-Listfile (the request processor
                  creates this)
          =PXL  - Full path and filename of the Filexmit-Listfile (the
                  request processor creates this)
          =IF   - Filename of a binary remote information file (FD
                  compatible)
          =PIF  - Full path and filename of a binary remote information
                  file (FD compatible).  These files will be created in
                  McMail's home directory, see also the Developer's Kit
                  RemInfoRecord
          =MB   - The minutes left to the next NoBBS event
          =MR   - The minutes left to the next NoRequest event
          =SRIF - Full path and filename to the "Standard Request Info
                  File".  If the request processor supports this, you only
                  need this parameter to call it

      All of these macros can be used in the configuration file entries
      marked with a plus sign (+) before their entry.  The macros that
      begin with a "=" are only valid during mail or FAX sessions.


                          3.2: Environment Variables


      McMail also supports DOS environment variables in all of the control
      files.  For example if you had "SET BAUD=38400" in your AUTOEXEC.BAT
      you can define in the MCMAIL<task>.CFG file "BAUDRATE %baud%".

      You can also define the following:

          %task=1% Baudrate 57600

      which would mean if the task was 1 then the baudrate is 57600, or:

          %task#2% Baudrate 115200

      which would mean if the task was NOT task 2 then the baudrate is
      115200.

      This will work in MCMAIL.CFG, MCMAIL.EVT, REQUEST.OK, TRANSLAT.COD,
      COST.TBL and all banner and response files that McMail generates as
      well.  If you want to insert a % symbol somewhere in the text fields
      or command strings, use %% instead.


                           3.3: Keyword Definitions



      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  15
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      McMail uses a variety of key definitions in its configuration files
      in order for it to know how you want it to operate.  There are quite
      a few keywords, and this gives you a lot of control over how McMail
      operates and behaves in different situations.

      Anything behind a ";" in any configuration file is treated as a
      comment and is ignored.  Any tabs that are placed in any of the
      config files will be translated to 8 spaces.


                        3.4: Modem Keyword Definitions


      The modem keywords deal directly with how McMail talks to your
      modem.  There are a few characters that can be used with some of
      the modem keywords, particularly those with initialization or modem
      response strings:

          `   Wait 1/20 seconds before sending the next character
          ~   Wait 1 second
          |   Send a carriage return and wait for a response
          !   Send a carriage return without waiting for a response
          -   This character is removed
          v   Lower DTR
          ^   Raise DTR
          \   This character is removed, but send next character without
              translation.  Use \- to send - and \\ to send \ to the modem

          Use %% to send a % to the modem

      On a side note, if you wish to use an external fossil driver, we
      recommend X00 v1.53a with the Receive/Transmit buffers equal to, or
      greater than, 4096.

      3.4.1: ComPort

      This is the comport this task must use.

      3.4.2: Baudrate

      This is the baudrate to call the modem.  If you use an external
      fossil driver such as X00, the baudrate here should be the baudrate
      you lock your fossil driver at.

      3.4.3: PortLocked

      If the port is locked by a fossil driver, PortLocked should be
      present in your configuration file.

      3.4.4: NoFossil


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  16
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      This keyword forces McMail to use its own asyncroutines, even if a
      fossil driver is currently loaded.

      3.4.5: FosHot

      This keyword forces McMail to leave the fossil hot on exit.

      3.4.6: UseFifo <#>

      This tells McMail how many bytes should be sent/received per
      interrupt.  This is only active when McMail's own asyncroutines are
      loaded.  Valid byte sizes are 1, 4, 8, and 14.

      3.4.7: ComReadSize <#>

      This tells McMail how many bytes should be read at once from the
      fossil/async in-buffer.  The default is 128, and this should only be
      changed if you know what you are doing as strange things may happen
      if you select incorrect sizes.  An example would be:

      ComReadSize 2048.

      3.4.8: ComWriteSize <#>

      This tells McMail how many bytes should written at once to the
      fossil/async out-buffer.  The default is 128, and this should only
      be changed, again, if you know what you are doing.

      3.4.9: FosDebugline [last]

      If you need a debug line for fossil debugging information, you can
      choose either line 8 (the default) or the last line of the screen
      (FosDebugline last).  The ISDN-Fossil driver cFos has this feature.

      3.4.10: FosDbglineChar <char>

      This is where you can define the character to use as the line
      character for the line between the fossil debug information and the
      logscreen.  This is only valid if FosDebugline is not "last".

      3.4.11: SlowModem

      If you have a slower modem, use this keyword as it tells McMail to
      wait two seconds for a response from the modem after sending a
      command.

      3.4.12: CommandDelay <#>

      This tells McMail to delay in <#>/100 seconds between each character
      of a modem command string.  The default is 10/100 seconds.  Set this
      to 0 if you have disabled the modem echo (E0).

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  17
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────


      3.4.13: SlowDisk

      This keyword stops async I/O during disk access.  This option is
      needed on some systems, and also with certain disk caches.  This
      command will only work with an extended fossil driver (ie. X00 v1.50
      and higher) or the internal async routines.

      3.4.14: NoModem

      This will run McMail without a modem.  This can be used for testing
      purposes.  Also, the commandline parameter NOMODEM can be used
      instead.

      3.4.15: ModemReset <string>

      This command will be sent to the modem at startup only.

          Ie. ModemReset ATZ|

      3.4.16: ModemInit <string>

      This command will be sent to the modem whenever an initialization is
      called for.  You can define more than one ModemInit keyword, and
      each will be sent to the modem in the order they are placed in the
      configuration file.

          Ie. ModemInit ATM3X4Q0V1&A3&B1&C1&D2&H1|
              ModemInit AT&K3&M4&R2&T5S2=255|

      3.4.17: Terminalinit <string>

      This command will be sent to the modem if you start up the internal
      terminal program.

          Ie. Terminalinit ATZ|

      3.4.18: ModemDeInit <string>

      This command will be sent to the modem before the system shuts down.

          Ie. ModemDeInit ATH0|

      3.4.19: ModemAnswer <string>

      This command will be used to force the modem to answer the phone.

          Ie. ModemAnswer ATA|

      3.4.20: ModemHangup <string>


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  18
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      This command will be used to hang up the phone.

          Ie. ModemHangup ATH0|

      3.4.21: ModemReject <string>

      This is the command used to reject an incoming call, but is
      available for ISDN only.  See also InfoID, InfoSize, and capability
      "I" in the enhanced NODEDATA.CFG (section 5)

          Ie. ModemReject ATH1H0|

      3.4.22: RejectResponse <string>

      This is the response from the modem if an outgoing call is rejected
      by the other end.  See also InfoID, InfoSize, and capability "I" in
      the enhanced NODEDATA.CFG.

          Ie. RejectResponse Call Rejected

      3.4.23: ModemBusy <string>

      This is the command to set the modem offhook.  This will be sent if
      you swap to DOS or run an external program via function keys.

          Ie. ModemBusy ATH1|

      3.4.24: ModemDial <string>

      The prefix for dialing out.

          Ie. ModemDial ATDT

      3.4.25: ModemSuffix <string>

      The suffix for dialing out.

          Ie. ModemSuffix |

      3.4.26: ModemOk <string>

      This is the command to force an OK response from the modem.  It will
      be sent by McMail every three minutes.

          Ie. ModemOk ATZ|

      3.4.27: ModemInfo <string>

      This is the command to send after hang up for logging modem
      connection information.  An example for USRobotic modems would be
      ATI6|, whereas an example for a user of cFos would be ATI2|.

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  19
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────


          Ie. ModemInfo ATI6|

      3.4.28: ModemIgnore <string>

      This is the response from the modem that McMail will ignore.  You
      can define more than one.

          Ie. ModemIgnore DATA

      3.4.29: MaxRinging <#>

      This tells McMail to hang up the line after <#> RINGs have been
      received without a connection.

      3.4.30: RingCounter <default> [v1] [s1] [v2] [s2]..

      This tells McMail how many rings to receive before answering the
      phone.  The <default> number of rings is used if no other string in
      the RING message is received.

          Ie. RingCounter 3

      A special case scenario would be:

          RingCounter 1 6 /0102 3 0441

      If the modem gives a response of "RING UNKNOWN/EAZ0/0102" McMail
      will wait until the sixth ring before answering, or if the response
      is "RING 0441.." McMail will answer on the third ring, or will
      answer on the first ring for any calls without "/0102" or "0441" in
      the RING responses.

      This is particularly useful if you use cFos or cFostalk.  The
      "/0102" indicates a voice caller, so you will have enough time to
      pick up the phone manually.

      3.4.31: RingTimer <#>

      This keyword defines the time in seconds between two RINGs.  The
      default is six seconds.  If no second RING is received after the
      defined RingTimer seconds, the ring counter is reset.  If you set
      this number too low, McMail will never answer the phone.

      3.4.32: WaitCarrier <#>

      This keyword tells McMail the maximum time in seconds to wait for a
      carrier connect.

      3.4.33: CallCollision


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  20
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      This keyword will force McMail to answer the phone if a NO CARRIER
      or NO DIALTONE is received when McMail tries to make an outbound
      call.


                      3.5: Modem/FAX Keyword Definitions


      McMail supports direct FAX receiving.  There is no need to drop to a
      third-party utility to receive your FAXes (although you certainly
      can).  All incoming FAXes are stored in Zyxel's Zfax format.

      If you use an external FAX receiving program, a file called
      FAXBAT<task>.BAT is created in McMail's main directory with the
      following contents:

          SPAWNFAX.BAT <task>
                        <com port>
                         <DTE speed>
                          <line speed>
                           <time to next NoBBS event>
                                         <connect add-ons>
                                                 <errorlevel>

      3.5.1: FaxResponse <string>

      This is the response from the modem to exit with FaxLevel to start
      the FAX receiving program.  If you have a modem that supports Class
      2 or Class 2.0 FAX/modem standards, you can disable FaxLevel and
      McMail can receive the incoming FAX calls directly.

          Ie. FaxResponse +FCON

      3.5.2: FaxLevel <#>

      This is the errorlevel that McMail must exit with upon receiving a
      FAX.  Disable this keyword if you want McMail to receive the FAX.

      3.5.3: AfterFax <string>

      This is where you define the program that will process the FAX after
      McMail receives it.  This keyword is only valid if you use McMail to
      receive the FAX and not an external FAX receiving program.  Include
      the full path and filename and all optional parameters.  You may
      define more than one AfterFax keyword and they will be processed in
      the order they appear in the configuration file.

          Ie. AfterFax f:\tools\zfax\zfax 2 =FAX
              AfterFax f:\tools\zfax\fax2tif =FAX f:\mailer\infax\=UNX.TIF



      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  21
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

                     3.6: Modem/Voice Keyword Definitions


      McMail also has the ability to perform special functions if the
      incoming call is a voice call.  This could be to call up "answering
      machine" software.  A file called VOCBAT<task>.BAT will be created
      in McMail's main directory with the following contents:

          SPAWNVOC.BAT <task>
                        <com port>
                         <DTE speed>
                          <line speed>
                           <time to next NoBBS event>
                                         <connect add-ons>
                                                 <errorlevel>

      3.6.1: VoiceResponse <string>

      This is where you define the response from your modem that states
      the incoming call is a voice call.

          Ie. VoiceResponse CONNECT VOICE

      3.6.2: VoiceLevel <#>

      This is the errorlevel that McMail must exit with upon receiving a
      voice connect.


                 3.7: Modem/External-Mail Keyword Definitions


      McMail has the ability to call up external mail receiving programs
      depending on the connection string received in a mail session.  This
      would be primarily useful if, for certain modems, you wanted to call
      a specific program for them alone, and wanted McMail to handle the
      mail in all other sessions.

      A file called EXMBAT<task>.BAT is created in McMail's main directory
      with the following contents:

          SPAWNEXM.BAT <task>
                        <com port>
                         <DTE speed>
                          <line speed>
                           <time to next NoBBS event>
                                         <connect add-ons>
                                                 <errorlevel>

      3.7.1: ExternalMail <string> <errorlevel>


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  22
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      This is the keyword that tells what string to respond to, and what
      errorlevel to exit McMail with.  The string is case sensitive, and
      can have a maximum of 30 characters and a minimum of four
      characters.

          Ie. ExternalMail ZyXEL 8


                              3.8: BBS Keywords


      When a human caller is detected and presses ESC twice, McMail will
      create a file called BBSBAT<task>.BAT in the McMail main directory
      with the following contents:

          SPAWNBBS.BAT <task>
                        <com port>
                         <DTE speed>
                          <line speed>
                           <time to next NoBBS event>
                                         <connect add-ons>
                                                 <errorlevel>

      3.8.1: BBSLevel <#>

      This is the errorlevel McMail will exit with when a human (BBS)
      caller is detected.

      3.8.2: BBSBanner <filename>

      The path and filename to a BBS banner file.  This file will be
      displayed to human callers before starting the BBS.

      3.8.3: InEventBanner <filename>

      The path and filename to an In-Event banner file.  This file will be
      displayed to human callers who have called when we are in Mail-Only
      mode.

      3.8.4: WaitBBSCaller <#>

      This is the definable number of seconds to wait for the human caller
      to press ESC twice before automatically starting the BBS.  The
      minimum value, and the default, is 11 seconds.

      3.8.5: NoBBSNext

      This keyword will disable the BBSNext function for all incoming
      calls.  See section 12.5.



      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  23
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

                    3.9: Terminal Mode Keyword Definitions


      McMail is equipped with its own terminal for you to use to call out
      to other BBS systems.  It is not overly sophistic, but definitely
      does the job.

      3.9.1: DefaultIEMSI <string>

      The default IEMSI options for the internal terminal.  See
      section 11.1.5 for more information.

          Ie. DefaultIEMSI NEWS,MAIL,FILE,HOT,CLR,MORE,FSED

      3.9.2: +ExtTerminal <#> or <file>

      The path and filename of an external terminal program.  A file
      called TRMBAT<task>.BAT is created in McMail's home directory with
      the following contents:

          SPAWNTRM.BAT <task>
                        <com port>
                         <DTE speed>
                          <line speed>
                           <time to next NoBBS event>
                                         <connect add-ons>
                                                 <errorlevel>

      However, you don't have to use this method.  TRMBAT<task>.BAT will
      only be created if you use the errorlevel method.

          Ie. ExtTerminal *50

      This would exit McMail with an errorlevel of 50 and it is up to you
      and your batchfiles to trap it.  However, you can also use the
      spawning method.  This will swap McMail into memory to load the
      terminal program.  If you place a "#" character before the program
      name, McMail will clear the screen before calling the program.

          Ie. ExtTerminal #c:\term\terminat.exe /PORT:$P /BAUD:$L $G

      3.9.3: PhoneBook <file>

      The path and filename to the BBS Phonebook control file.  This is
      used in the terminal mode when you press ALT-B.  The file is
      typically called BBSDATA.CFG.  See section 11 for more information.


                   3.10: Path/Filename Keyword Definitions



      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  24
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      McMail needs to know the location to a number of different
      directories and files on your hard drive.  This is where you let
      McMail know where to find everything.

      3.10.1: +EventFile <filename>

      The full path and name to the Event control file.  If you disable
      this keyword MCMAIL<task>.EVT is used instead.

      3.10.2: +Outbound <dir>

      Your default outbound directory.

          Ie. Outbound C:\MCMAIL\MAIL\OUT

      3.10.3: FaxOutbound <dir>

      This is the directory where McMail will store all of the FAX
      forwards.

      3.10.4: +Inbound <dir>

      Your inbound directory for normal mail sessions.

      3.10.5: +SecureInbound <dir>

      Your inbound directory for secure mail sessions.

      3.10.6: +UnKnownInbound <dir>

      Your inbound directory for unknown sessions.

      3.10.7: +FaxInbound <dir>

      Your inbound directory for FAX sessions.

      3.10.8: +DownloadPath <dir>

      When in terminal mode, all incoming files will be placed in this
      directory.

      3.10.9: +NetMail <dir>

      This is your netmail directory.  This is used for InfoMail and the
      internal routing.

      3.10.10: +PersMail <dir>

      This is your personal netmail directory.  If you use a personal
      netmail mover like IMOVE or ITRACK, enter the directory here where
      mail directed to you is moved to.  The default is the NetMail path.

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  25
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────


      3.10.11: +RouteInfo <filename>

      The filename of your routing information configuration, if any.

      3.10.12: +Semaphore <dir>

      The directory where McMail should place and look for its semaphore
      files.

      3.10.13: +DefTransDir <dir>

      This is the path where the file tagger will start when you press
      ALT-S to transmit files to another node.

      3.10.14: TranslatFile <filename>

      This is the full path and filename to the modem-response translation
      file.  See section 8 for more details.


                      3.11: Nodelist Keyword Definitions

      3.11.1: +Nodelist <dir>

      This is the path where the nodelist index files can be found.

      3.11.2: Version7

      This tells McMail to use a V7 nodelist index.  You must have a V7
      nodelist compiler like FastV7 in order to use this.

      3.11.3: OldStyle

      This tells McMail to use the old style bit-type V7 flag format.

      3.11.4: V7Flags <flag> <flag> ...

      This is where you define the modem Version7 flags.  You have to
      define these bits (each flag is an array of 8 bits) and give them a
      meaning.  For example:

          V7Flags V34 V32T ZYX V32B V32 V22B V22 V21
          ;bit     1   2    3   4    5   6    7   8
          ;value   1   2    4   8   16  32   64  128

      The first bit is V34, the second is V32T, and so on.  If a bit has
      no meaning, it must be ignored by using the minus sign.  So, if bit
      2 doesn't mean anything, the keyword would look like:

          V7Flags V34 - ZYX V32B V32 V22B V22 V21

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  26
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────


      With new-style Version7 compiled nodelists, things are a little
      different.  You can define up to 255 different meanings for the
      flags.  When a flag for the node is found with a value higher
      than the previous flag, the old flag is replaced by the new one.
      For example, you define 1=V32, 2=V32B, 3=V34, and 4=H16.  A node
      with flags V34,V32B,V32 will get the number 3 (according to V34).  A
      node with flags V32T,V32B,V42B will get the number 2 (according to
      V32B).

      This is only needed if you use the Version7 nodelist index.  If you
      do, the V7 compiler you use will have more information on the
      V7Flags and probably a default set to use.

      3.11.5: V7NodeFlags

      This is where you define the node flags.  A node flag is an array of
      16 bits.  Each bit, like V7Flag, has a meaning.  There are a few
      hard-coded meanings:

          1=HUB, 2=HOST, 3=REGION, 4=ZONE, 5=CM, 13=POINT

      For example, if the sysop has defined bit 6 as XA and bit 9 as MO,
      the keyword would look like:

          V7NodeFlags -  -  -  -  -  XA  -  -  MO  -  -  -  -  -  -  -
          ;bit        1  2  3  4  5  6   7  8  9   10 11 12 13 14 15 16

      Since the first 5 bits are hard-coded, there is no need to define
      them anymore.  Again, it is important that this interfaces with your
      Version7 nodelist compiler, so please look into your V7
      configuration there carefully.  You will probably get more
      information on how to set the bits with your compiler with it's
      docs.

      3.11.6: Domain <name> <index> <zone>

      This will enable domain information.  The proper syntax of this
      keyword is:

          Domain <name> <indexes without ext.> <zones to match>

      If you don't use a V7 index, you can define more than one index.
      For example:

          Domain fidonet fidonet®ion 1 2 3 4 5 6

      In this case, McMail will search first in FIDONET.MNI and if the
      node is not found there, then will search in REGION.MNI.  You will
      have to compile the two indexes with separate "NodeList" entries in
      MCMNODE.CFG, like:

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  27
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────


          NodeList fidonet 2 nodelist.#
          NodeList region  2 region24.#

      If you are in only one domain, or network, you don't have to worry
      about this.  For default, the nodelist index is NODEX.  At the
      moment, McMail is not fully Domain-aware.  It is used only for
      searching in different nodelist files for node data.

      3.11.7: MaxCallBaud <#>

      The maximum baud a node can have in the nodelist to call him.

      3.11.8: MinCallBaud <#>

      The minimum baud a node can have in the nodelist to call him.

      3.11.9: NoCallFlags <string>

      The flags a node CANNOT have in the nodelist in order to call him.
      This keyword has the highest priority.

          Ie. NoCallFlags HST H14 H16

      3.11.10: OnlyCallFlags

      The flags a node MUST have in the nodelist in order to call him.
      This keyword has a lower priority than NoCallFlags.

          Ie. OnlyCallFlags ISDN

      3.11.11: FlagTrans <nodeflag> <dialprefix> <dialsuffix>

      This allows you to dial different systems with different dialing
      strings, to enable certain features in your modem.  This is a very
      handy method to use if you use cFos and ISDN.  In the configuration
      file, the LAST FlagTrans keyword entry has the highest priority, and
      the FIRST FlagTrans keyword has the lowest priority.

          Ie. FlagTrans HST  ATB1D  |
              FlagTrans ISDN AT&B2D |

      3.11.12: NoNodelist

      If this keyword is enabled, McMail will operate without a nodelist.
      The only information that will be used is that in the node data
      configuration.  This is particularly useful for point systems, as
      they can just insert their boss node with his phone number in the
      NodeData section of the configuration, and thus don't need an entire
      nodelist.


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  28
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────


                  3.12: Site Information Keyword Definitions

      3.12.1: AKA <address>

      This is where you define your AKA (Also Known As) addresses.  These
      are all your network addresses.  The first definition is your main
      address. You can define up to a maximum of 256 AKAs.

          Ie. AKA 1:342/52

      3.12.2: AkaMatching

      If this keyword is enabled, McMail will only send matching AKAs to
      incoming calls.  This is called ZoneMatching.  So if system one had
      the three addresses 1:342/52, 38:1403/0, and 141:500/0, and system
      two had the address 1:217/11 and 144:23/854, McMail would only
      present 1:342/52 to the incoming caller, because the only zone match
      between the two systems is zone 1.

      3.12.3: Sysop <name>

      Your name.  This is used in the EMSI site information.

      3.12.4: Site <string>

      Your site name, typically your BBS name.  This is used in the EMSI
      site information.

      3.12.5: Location <string>

      Your site location (city, province/state, country).  This is used in
      the EMSI site information.

      3.12.6: MaxSpeed <#>

      The maximum speed of your modem on this line.  This is used in the
      EMSI site information.

      3.12.7: Flags <string>

      Your system's capability flags.  These are your modem protocol flags
      (ie. V32, VFC, V42B, etc.) as well as your fido capabilities.  You
      will be using XX for your mailer type (McMail is a WAZOO file
      request/update compliant mailer), and CM if your system is
      continuous mail, MO if it is mail only, etc.  These are the same
      flags listed in your entry in your nodelists.  This is used in your
      EMSI site information.

      3.12.8: Phone <string>


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  29
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      Your system's phone number, preferably in international format.
      This is used in your EMSI site information.

      3.12.9: Ticker <string>

      This is where you can define an information line.  This will be sent
      to the remote chat window at the start of Hydra sessions.

          Ie. Ticker FREQ MCMAIL for McMail v1.0...

      3.12.10: TimeZone <#>

      This is where you define your Timeoffset in minutes to UTC (GMT,
      Greenwich Mean Time).  This is used for VIA-lines, EMSI handshaking,
      and T-Nodelist flags.  If you were in the MST (Mountain Standard
      Time) TimeZone, you would use:

          TimeZone -420

      because MST is -0700 UTC, or -7 hours from UTC, which, in turn, is
      -420 minutes from UTC.

      3.12.11: Dial <string> <new string>

      This is where you can define some dial translation commands.  With
      this keyword, <string> is what is found in the nodelist, and <new
      string> is what <string> is replaced with.  For example, if you were
      in the 403 area code and everything was local, you would use the
      following to strip international and national information from local
      calls:

          Dial 1-403- /

      If you wished to add a 00 to all international calls, you would use:

          Dial / 00

      You may define up to 50 dial translations.

                        3.13: Cost Keyword Definitions


      McMail uses a very flexible cost calculation system that may take a
      little time to fully understand, but is very powerful and can be
      used for anyone in any situation.

      3.13.1: +CostDatFile <filename>

      The full path and name of your cost control file, if any.

      3.13.2: CostTimeOffset <#>

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  30
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────


      This is the time in 1/10 seconds that your modem requires for
      handshaking.  This will be added to the overall session time, to
      calculate the correct cost for sessions.

      3.13.3: FosChargeUnit <#>

      If you use cFos, McMail tries to get the real charge from the ISDN
      Appendage of cFos.  This is where you can define the cost per charge
      unit so you don't need a cost control file.

      3.13.4: NoFosCharge

      This disables McMail's retrieval of the cost information from cFos.
      So, if you do NOT want McMail to get the cost information from cFos,
      enable this keyword.

      3.13.5: Currency <dec-del> <tho-del> <div> <dec-dig>

      This keyword can change the currency information for the cost data.
      This is only for screen output.

          Ie. Currency . , 100 2

      This tells McMail that the decimal-delimiter for your currency is a
      decimal (.), that the thousand-delimiter for your currency is a
      comma (,), that its divisor is 100, and that it has two digits
      behind the decimal.  The above currency setting is used in Canada
      and the USA (Ie. $99,999.00).

      3.13.6: Scottishmode <#>

      This allows you to define the maximum value that is permitted in the
      Flow Data Cost Field.  If the Flow Data cost is lower than this
      number, outbound calls will be made.  If a call cannot be made
      without going ABOVE this value, the call will not be made.  This is
      a good way to make sure you don't go above a certain budget.


                        3.14: Mail Keyword Definitions

      3.14.1: +MailFlag <filename>

      This is the full path and filename of the semaphore file which is
      created on received mail.  This is only used if the errorlevel to
      exit with on received mail in the event configuration is set to
      zero.

          Ie. MailFlag c:\mcmail\mailin.$T

      3.14.2: MailExitExt <def>

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  31
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────


      This is where you can define what extension a received file must
      have to exit on received mail, or to create the mail processing
      flag.  If you use the wildcard "*", McMail will exit after every
      session.  If you use something like TU or WE, it will match TU1 or
      WE3, and so forth.

          Ie. MailExitExt PKT TIC ZIC AIC LIC SU MO WE TU TH FR SA FAX

      3.14.3: ScaredMode

      If this keyword is enabled, McMail will force all incoming files to
      be received into the unknown inbound directory during ALL
      unprotected sessions.

      3.14.4: PWOverride

      If this keyword is enabled, McMail will ignore password errors on
      outbound calls, but only mail for the called up AKA will be sent.
      Otherwise it will hang up.  If you have mail waiting for two
      different AKAs of a system with a password error, only one mail
      packet will be sent, and it will be sent to the AKA you specifically
      told McMail to dial.  This option can also be toggled with CTRL-P.

      3.14.5: HandshakeFailureTries <#>

      The maximum outbound calls that will be tried if a handshake failure
      occurs.  The maximum value is 99, the default is 2, and a value of
      0 will ignore the number of handshake failures and will continue to
      try until a successful connect is made.

      3.14.6: SessionFailureTries <#>

      The maximum outbound calls that will be tried if a zmodem, xmodem,
      or hydra session failure occurs.  The maximum value is 99, the
      default is 2, and a value of 0 will ignore.

      3.14.7: NoCarrierTries <#>

      The maximum outbound calls that will be made if the modem reports a
      NO CARRIER after dialing.  The default is 0 (ignore).


                      3.15: InfoText Keyword Definitions


      InfoText is a special feature of McMail.  What it does is, based on
      certain definable criteria, uses a defined text file to send as
      netmail to in-calling systems.  You may define some node information
      after the path and filename of the text to use, and the text will
      only be sent as netmail if the incoming node matches the node

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  32
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      information.  For example:

          KnownInfoText c:\mcmail\info.knw 1:* 2:2426/*

      would send the file INFO.KNW as netmail to anyone calling in who's
      node address is in zone 1 OR in zone 2 and net 2426.

      You can use wildcarding in your node definitions.  For example, 1:*
      would include every system in zone 1, 1:342/* would include every
      system in zone 1 and net 342, 1:342/52.* would include every system
      in zone 1, net 342, and all points under node 52.  You may also
      exclude certain systems by placing a ! in front of the node address.
      For example, a setting of !1:342/* would exclude zone 1, net 342
      from the nodespec.

      3.15.1: +KnownInfoText <filename> [nodedef1] ..

      Sent only to known systems.  Known systems are those listed in your
      nodelists.

      3.15.2: +ProtectInfoText <filename> [nodedef1] ..

      Sent only to protected systems.  Protected systems are those you
      share a session level password with and are defined in your node
      configuration.

      3.15.3: +UnknownInfoText <filename> [nodedef1] ..

      Sent only to unknown systems.  Unknown systems are those not listed
      in your nodelists.


                    3.16: File Request Keyword Definitions

      3.16.1: +RequestCfg <filename>

      The full path and filename of the request control file.  See section
      6 for more info.

      3.16.2: +RequestFooter <filename>

      The full path and filename to the textfile that will be appended to
      the response netmail for all successful file requests.

      3.16.3: +FailedReqFooter <filename>

      The full path and filename to the textfile that will be appended to
      the response netmail for all failed file requests.  This will be
      used instead of the defined RequestFooter if one or more of the
      requested files could not be found.


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  33
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      3.16.4: +NoRequestBanner <filename>

      The full path and filename to the textfile that will be appended to
      the response netmail for all file requests received during NoFREQ
      events.

      3.16.5: MaxSearchTime <#>

      The maximum number of seconds McMail should spend searching for a
      requested file.

      3.16.6: UnknownReqTime <#>

      The maximum time in minutes an unknown system has for their file
      requests.

      3.16.7: UnknownReqSize <#>

      The maximum number of bytes an unknown system has for their file
      requests.  (For example, a value of 1000000 would be the equivalent
      of one megabyte.)

      3.16.8: KnownReqTime <#>

      The maximum time in minutes a known system has for their file
      requests.

      3.16.9: KnownReqSize <#>

      The maximum number of bytes a known system has for their file
      requests.

      3.16.10: ProtectReqTime <#>

      The maximum time in minutes a protected system has for their file
      requests.

      3.16.11: ProtectReqSize <#>

      The maximum number of bytes a protected system has for their file
      requests.

      3.16.12: FirstMatch

      If this keyword is present, McMail will stop searching for a
      requested file on its first match.  This is not valid for wildcard
      searching (ie. MCM10*.RAR).

      3.16.13: NoRequestOnUs

      If this keyword is present, McMail will NOT process incoming file

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  34
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      requests on outbound calls.  If it is not present, McMail WILL
      process incoming file requests on outbound calls.

      3.16.14: +ReqProcessor <exe> <cmdline>

      This is where you define the full path and name to an external
      Request Processor (such as XOR).  If this keyword is enabled, McMail
      will call the Request Processor instead of responding to the file
      request itself.

          Ie. ReqProcessor c:\mcmail\xor.exe /M=SRIF


                        3.17: Log Keyword Definitions


      McMail's logging procedures can be extremely detailed or very
      simple, and no matter how you like it, you can define it, as they
      are completely configurable.  There are a few key characters that
      can be used to tell McMail what to log.  If any of these characters
      are present in the LogLevel or ScrLogLevel keywords, McMail will add
      what the characters represent to the logs.

          +   normal messages
          -   nothing vital, but nice
          ?   errors
          !   important messages
          ~   serial (modem) commands
          #   special information
          &   nodial information
          $   routing information
          =   mail-to-you information
          F   file debug
          R   routing debug
          M   memory debug
          D   special debug
              (this shows special information like the types of inbound
              calls in the logs:
                  B-Call - BBS Caller
                  E-Call - EMSI Caller (FTS)
                  N Call - No-Call
                  Y-Call - YooHoo Caller (FTS-0006) )
          E   emsi debug
          V   event debug
          Y   yoohoo debug
          H   hydra debug
          Z   zmodem debug
          X   xmodem debug
          A   fax debug

      So, if you defined the following:

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  35
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────


          LogLevel +-?!#&$=

      The file log would contain normal messages, nice messages, error
      messages, important messages, special information, nodial
      information, routing information, and mail-to-you information.

      3.17.1: LogLevel <chars>

      This defines what is to be included in the default file log.

      3.17.2: ScrLogLevel <chars>

      This defines what is to be included in the screen log.

      3.17.3: SpcLogLevel <chars>

      This defines what is to be included in the special file log (if
      defined).

      3.17.4: +LogFile <filename>

      The full path and filename of the default log file.

      3.17.5: +SpcLogFile <filename>

      The full path and filename of the special log file.

      3.17.6: +CostLogFile <filename>

      The full path and filename of the log file containing the costing
      information.

      3.17.7: +ErrLogFile <filename>

      The full path and filename of the error log file.

      3.17.8: +TerminalCap <filename>

      The full path and filename of the terminal capture file.

      3.17.9: ShortLog

      Enable this keyword if you do not want any day or program
      information added to your log files.

      3.17.10: MaxHistory <#>

      This defines the maximum entries in the history files.  A value of 0
      is unlimited, and the minimum value is 4.  The default is 20.  The
      history files are updated daily at midnight.

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  36
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────



                    3.18: Environment Keyword Definitions


      McMail is optimized to run effectively in any environment.  Although
      a native DOS mailer, it runs well under DESQview, OS/2, etc. but in
      some cases needs to be told how to deal with the different
      environments.

      3.18.1: Environment <string>

      This is the keyword to force McMail to use Time Slicing techniques
      for the specific multitasking environment.  If this keyword is
      disabled, McMail will attempt to detect it.  Valid environment
      strings are:

          OS/2
          Windows
          DesqView
          TopView
          DoubleDOS
          PC-DOS
          None

      3.18.2: SliceDuringTransfer [dynamic]

      If this keyword is present, McMail will give up time slices during
      file transfers in multitasking environments.  If the word "dynamic"
      is present after the keyword, dynamic time slicing is enabled for
      optimal transfer speeds.

      3.18.3: DvTaskSwitch

      If this keyword is present and McMail receives a "CONNECT" from the
      modem, this task will be switched to the foreground immediately in
      DESQview environments.


                   3.19: External File Keyword Definitions

      3.19.1: +PktViewer <file>

      The path and filename to the external PKT viewer.  This is used in
      the Outbound Manager when you press CTRL-ENTER.

      3.19.2: +BBSViewer <file>

      The path and filename to an external BBS Viewer like the
      included VIEWRA.EXE.  It will be called if you press ENTER in the
      Multiline Window.  The first parameter is the Task number you have

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  37
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      chosen in the History Window.

          Ie. BBSViewer c:\mcmail\viewra.exe $M

      3.19.3: +DoorSys <file>

      The path and filename of a DOOR.SYS compatible BBS file.  This is
      used by McmView if you are not running RemoteAccess.

      3.19.4: +BBSKick <file>

      The path and filename of a semaphore file that will disconnect the
      user online.  This is used by McmView if you press ALT-K on a
      BBS-Caller Window.


                      3.20: Protocol Keyword Definitions

      3.20.1: NoHydra

      Do not use the Hydra protocol at all.

      3.20.2: NoRH1

      Do not use the RH1 (Request First option in Hydra sessions) protocol
      at all.

      3.20.3: NoDZA

      Do not use the DirectZedZap protocol at all.

      3.20.4: NoZAP

      Do not use the ZedZap protocol at all.

      3.20.5: HydraBlockLen <#>

      The maximum Hydra block length.  The default is 2048.

      3.20.6: HydraTxWin <#>

      Set window management and stream size for transmit.

      3.20.7: HydraRxWin <#>

      Set window management and stream size for receive.  The default is
      0.  (After transfering that block size, wait or send an ACK.  This
      is good for bad connections.)

      3.20.8: HydraNoBell


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  38
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      This keyword, if present, forces McMail to disable the beep in Hydra
      chat mode.

      3.20.9: HydraTELENET

      Enables Telenet Escape sequences (<CR>@<CR>).

      3.20.10: HydraCTLCHRS

      Enables Escape of all control characters (ASCII characters 0-31 and
      127).

      3.20.11: HydraXONXOFF

      Enables Escape XON/XOFF.

      3.20.12: HydraHIGHCTL

      Enables Escape of all control characters (Telenet, Control,
      XON/XOFF) with high bit set too.

      3.20.13: HydraHIGHBIT

      Enables 7 bit mode, using 7-bit encoding.

      3.20.14: HydraCANBRK

      Enables transmitting of a break signal.

      3.20.15: HydraCANASC

      Enables ASC packet format where 8-bit data is transformed into 7-bit
      data by a simple shift operation.

      3.20.16: HydraCANUUE

      Enables UUE packet format where 8-bit data is transformed into
      printable ASCII using the UUEncode algorithm.

      3.20.17: HydraCRC32

      Enables use of 32-bit CRC error detection in receive packets.

      3.20.18: HydraDEVICE

      Enables receiving of device packets.

      3.20.19: +ExtDnProtocol <file>

      The path and filename of an external download protocol driver for
      your Terminal Mode.  Use the parameter *H to leave the fossil hot.

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  39
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      Only one protocol is supported.

          Ie. ExtDnProtocol c:\ut\hslink.exe -p$P -E$S -u$D -r -k -o @$U

      3.20.20: +ExtUpProtocol <file>

      The path and filename of an external upload protocol driver for your
      Terminal Mode.  Use the parameter *H to leave the fossil hot.  Only
      one protocol is supported.

          Ie. ExtUpProtocol c:\ut\hslink.exe -p$P -E$S -u$D -r -k -o @$U


                     3.21: Node Data Keyword Definitions


      This is where you can define your nodes.  By nodes, we mean the
      systems that you call or that call you (not yourself!).  There are a
      number of different options that can be used when defining your
      nodes.

      3.21.1: NodeData <nodeaddress> <pw> <phone> <flags>

      This defines your node.  You must specify the node address, your
      session-level password you share with the node, the node's phone
      number, and their nodelist flags.  The phone numbers MUST be in
      international format.  If you do not use one entry (ie. the
      session-level passwords) you must place a "-" character in that
      field.

          Ie. NodeData 2:2426/2090 password 49-441-123  CM,V34
              NodeData 2:2426/2033     -    49-441-9836    -

      3.21.2: NodedataFile <file>

      The path and filename to the enhanced NodeData configuration file.
      It is possible to use both the NodeData keyword and the enhanced
      configuration file, however you should NOT define a node twice, once
      in the NodeData keyword field and once in the enhanced
      configuration.  See section 5 for more information.


                    3.22: Function Key Keyword Definitions


      McMail has the ability for you to define up to 24 function keys to
      be used once McMail is loaded.  These can be used for various things
      like manually packing or unpacking mail, manual maintenance, loading
      setup programs, etc.



      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  40
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      3.22.1: KeyF? <menu title>,*<errorlevel>

      This will exit McMail with an errorlevel when the specified function
      key is pressed.  For example:

          KeyF11 Unpack Mail,*50

      would exit with an errorlevel of 50 when F11 is pressed.

      3.22.2: KeyF? <menu title>,[#]<path\filename> [<parameters>]

      For the swapping method, if you put a "#" in front of the program,
      McMail will clear the screen before loading the program.  For
      example:

          KeyF6 AllFix Setup,#c:\mcmail\allfix\asetup.exe

      This will load AllFix's setup program and clear the screen before
      calling it.

      3.22.3: KeySF? *<errorlevel>

      This function is exactly the same as the KeyF? function, without the
      menu title option.

      3.22.4: KeySF? [#]>path\filename> [<parameters>]

      This function is exactly the same as the KeySF? function, without
      the menu title option.


                   3.23: Miscellaneous Keyword Definitions

      3.23.1: NoMailFlash

      This keyword disables the "Mail" flashing that is displayed when
      personal mail (PersMail) is found.

      3.23.2: NoPersMailScan

      This keyword disables the PersMail scan at startup.

      3.23.3: NoBusyScan

      This keyword disables the checking of old busy files on startup.

      3.23.4: NoRoute

      This keyword disables McMail's routing of files and netmail.

      3.23.5: MinDrvSpace <drive> <minbyte>

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  41
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────


      This is the minimum drive space that must be present to run.  This
      is also checked during mail sessions.  You may define more than one
      MinDrvSpace keyword.  The minimum is defined in BYTES.

          Ie. MinDrvSpace C: 2000000

      3.23.6: NoRemoteScreen

      This keyword tells McMail not to create data for the line-watch
      facility.  This should only be enabled if you performance problems.

      3.23.7: NoTransferSize

      This keyword disables McMail's calculation of bytes to send.  This
      can be used for faster outbound scans during mail sessions.

      3.23.8: KbdLock <password>

      This keyword will lock the keyboard whenever McMail starts.  The
      <password> is the case sensitive password that will unlock the
      keyboard (maximum of 8 characters). To activate the keyboard lock,
      press CTRL-L or enable the ScreenBlank keyword.  To unlock the
      keyboard, type in <password> and press ENTER.

      3.23.9: NoSound

      This keyword will disable all sounds.

      3.23.10: AlertSound <#>

      This is the frequency, in Hz, McMail will beep at if you have
      inserted a "$A" somewhere in the Translation File.  See the sample
      TRANSLAT.COD for more information.  The default is 2000.

      3.23.11: ScreenBlank <#> [BLANK]

      This keyword will blank the screen in <#> seconds of no activity.  A
      value of 0 will disable this.  Adding BLANK to the end of the
      keyword will disable the jumping task screen saver and simply black
      out the screen.

      3.23.12: VideoMode <#>

      This keyword will reset the video mode of your mailer to either 25
      lines or 43/50 lines at startup.

      3.23.13: AliveTime <#>

      This keyword tells McMail how many seconds to wait before touching
      the MCMRUN.<task> semaphore file.  0 disables this feature.  The

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  42
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

      default is every 180 seconds.

      3.23.14: StartUpScanDelay <#>

      The delay in seconds before the first outbound scan after startup is
      called.  The default is 12 seconds.

      3.23.15: +Include <file>

      This tells McMail to include <file> when writing the configuration.
      This is good to use if you want one main configuration file with
      certain aspects (ie. BBS keywords) to be different for different
      nodes.

          Ie. Include c:\mcmail\mcm$T.cfg

      3.23.16: TaskKey <string>

      The TaskKey is the special key for this task, or node.  If a node in
      the enhanced node data configuration file does not have a matching
      flag in the file's TaskKey field, then that node will NOT be called
      by this node.

      If one of the Keys are empty, then no checking will be done.  A
      value of "----------" is the same as disabling this keyword.

      For example, the TaskKey for this node is "--X-----" and the TaskKey
      field for a node in the enhanced node data configuration file is
      "-XX-----".  This node would be called by this line.  If the TaskKey
      for this node was "X-------" then that node would NOT be called,
      under ANY circumstances (even immediate mail).

      All entries in this field will be interpreted as an "X", except for
      the "-".  So you could also define:

          TaskKey -2-4--6---

      and it would be interpreted as:

          TaskKey -X-X--X---

      3.23.17: Color <string>

      With this keyword, you can define how McMail will look when you
      start it up.  The following numbers represent certain colors:

          Black     = 00      LightBlack   = 08
          Blue      = 01      LightBlue    = 09
          Green     = 02      LightGreen   = 10
          Cyan      = 03      LightCyan    = 11
          Red       = 04      LightRed     = 12

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  43
      Section 3                                           MCMAIL<TASK>.CFG
      ────────────────────────────────────────────────────────────────────

          Magenta   = 05      LightMagenta = 13
          Brown     = 06      Yellow       = 14
          LightGrey = 07      White        = 15

          To make a color blink, add 128 to it's value.  For example, to
          use the color blinking red, you would use the value 132 (4+128).

      The keyword is called like this:

          Color <1fore> <1back> <2fore> <2back> ..

      Therefore, each "field" or configurable color area, has two numbers
      it must deal with, the first being the foreground color, and the
      second being the background color.  For example:

          01 00 08 00

      This would define the FIRST field to be dark blue on black, and the
      second field to be light black on black.  The fields are called in
      this order:

          1)  Header line
          2)  Status line
          3)  Log file frame
          4)  Log file text
          5)  Log file title
          6)  Window frame
          7)  Window text
          8)  Window title
          9)  Zoom window frame
          10) Zoom window text
          11) Zoom window title
          12) Transfer window frame
          13) Transfer window text
          14) Transfer window title
          15) Edit window frame
          16) Edit window text
          17) Edit window title
          18) Selected item

      So, for the following keyword definition:

          Color 08 00 15 00 03 00 08 00 15 00 04 00 03 00 11 00 08 00

      the header line would be light black on black, the status line would
      be bright white on black, the log file frame would be cyan on black,
      the log file text would be light black on black, the log file title
      would be bright white on black, the window frame would be red on
      black, the window text would be cyan on black, the window title
      would be light cyan on black, the zoom window frame would be light
      black on black, and so forth, for all 18 fields.

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  44
      Section 4                                           MCMAIL<TASK>.EVT
      ────────────────────────────────────────────────────────────────────

                         Section 4: MCMAIL<TASK>.EVT


      The event scheduler for McMail is also a text configuration, usually
      called MCMAIL<task>.EVT.  As you will soon see, it is a VERY
      flexible event manager.  There is almost nothing you can't, one way
      or another, do.


                               4.1: Event Lines


      Below is an example MCMAIL1.EVT file for task (node) 1:

      ;Tag Days                        Start End   ME SE RD RT  CST   FL
      ;------------------------------------------------------------------
       @   ALL                         00:00 24:00 50 00 30 20 >1200  IBP

      ; Midnight maintenance event "A"
       A   ALL                         00:02 00:03 00 29 00 00   00   RF


      The event lines should be created in the below format.

          <tag> <days> <start> <end> <me> <se> <rd> <rt> <cst> <fl>

      This is the major information line that the event file MUST contain
      for each event.  After this line you may specify some extra
      commands.  Ie:

          <tag> <days> <start> <end> <me> <se> <rd> <rt> <cst> <fl>
          <extra commands>

      The extra commands will be processed for the current event
      definition alone.  Once a new event line is created with a new tag,
      it tells McMail that a new event definition has begun.

      4.1.1: Tag

      This is just to remind you, and McMail, which event is running.  @
      is the tag for the global event, and you may use A-Z for other tags.

      4.1.2: Days

      Which day the event is active.  You can do this in a variety of
      ways.  "ALL" means every day of the week, whereas "Mon+Wed+Fri"
      would mean only on Mondays, Wednesdays, and Fridays.  "MM" means a
      day of the month (1-31) so if you put the day as 14, the event would
      only be executed on the 14th of each month.  "DDMM" means a day of
      the year where DD is the day (1-31) and MM is the month (1-12), so a
      value of 3112 would mean December 31st only.

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  45
      Section 4                                           MCMAIL<TASK>.EVT
      ────────────────────────────────────────────────────────────────────


      4.1.3: Start

      The start of the event.  Must be in 24 hour format, and MUST contain
      five characters (ie. 00:00 for midnight).

      4.1.4: End

      The end of the event.  Must be in 24 hour format, and MUST contain
      five characters (ie. 00:00 for midnight).  The @ event must have a
      starting time of 00:00 and an ending time of 24:00.

      4.1.5: ME - Mail Errorlevel

      The errorlevel with which to exit with when mail is received during
      this event.

      4.1.6: SE - EventStart Errorlevel

      The errorlevel with which to exit with at the start of the event.
      This is good for defining events to do some sort of maintenance on
      the BBS or zipping up your logs.

      4.1.7: RD - Random Outbound Call

      The seconds to wait before making the next outbound call.  McMail
      calculates this randomly with the following formula:

          RD + Random(0.5*RD to 1.5*RD)

      This means that a value of 30 would cause McMail to wait between 45
      seconds (30+(.5*30)) and 75 seconds (30+(1.5*30) between outbound
      calls.

      4.1.8: RT - Busy Retries

      How many retries McMail is permitted to make on outbound calls that
      receive a BUSY signal from the modem.  A value of 0 will ignore this
      setting.  A value of 20 would mean that McMail will make 20 tries,
      and if all 20 tries are BUSY, McMail will not try any more.

      4.1.9: CST - Cost Matching

      The costmatch for this event.  Here you can enter a TimeUnit in
      one/tenths of a second like in the COST.TBL file (see section 9).
      The first character controls the comparison:

          >   The TimeUnit of a node must be higher to call out
          <   The TimeUnit of a node must be lower to call out
          =   The TimeUnit of a node must be equal to call out
          #   The TimeUnit of a node must be unequal to call out

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  46
      Section 4                                           MCMAIL<TASK>.EVT
      ────────────────────────────────────────────────────────────────────


      If the value of this field is 0, the costmatch will be ignored.
      This setting is NOT valid for immediate mail.  Immediate mail will
      be sent regardless, if the event permits.  In order to use the
      costmatch in the events, you must also have a valid COST.TBL
      defined, otherwise things may not work properly.

      For example:

          >1200   Only call a node if the time for one charge is greater
                  than 120 seconds, or 2 minutes.

          =215    Only call a node if the time for one charge is equal to
                  21.5 seconds.

          #300    Only call a node if the time for one charge is NOT equal
                  to 30 seconds.

      This is all VERY dependant on your COST.TBL settings.  The TimeUnits
      are read from that file.  With these settings, you can restrict
      McMail from sending mail to systems where the connection will be too
      long, therefore costing too much.  The possibilities for this are
      endless, but it all boils down to the ability to save yourself money
      on expensive polls.  You can use this to save the longer polls for
      the middle of the night where it would be cheaper, and the
      inexpensive polls for during the day, where the cost is generally
      much higher.

      Please refer to section 9 for more information on the cost table.

      4.1.10: FL - Event Flags

      These are the flags for the event.  The flags basically tell McMail
      what is permitted during this event, and what isn't.

          A   All mail will be sent on outgoing calls, even HOLD mail.
          B   Allow BBS callers.
          C   Crash mail only.
          D   Dynamic event.  End event if there is no more mail to send.
          F   Forced event.  Event will be started, regardless if the
              start time has passed.
          H   Don't send ARC-mail or file attaches.  Only .PKT files will
              be sent.
          I   Immediate mail only.
          M   Mute.  No sound in this event.
          N   No file requests allowed.
          O   Read the "What's On Hold" data after every disconnect.
          P   Pickup mail on outgoing calls.  If this flag is not
              included in the event configuration, McMail will hang up the
              line immediately after sending mail.
          Q   Hold (don't send) file requests.

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  47
      Section 4                                           MCMAIL<TASK>.EVT
      ────────────────────────────────────────────────────────────────────

          R   Receive only, don't call out at all.
          S   Send only.  Ignore RING.
          #   Allow calling non-CM (continuous mail) systems.

      For most systems, your @ (global) event should contain "BIP" as this
      allows BBS callers, sends immediate mail only, and picks up mail on
      outgoing calls.  You should use "F" in your maintenance events in
      case McMail gets started after the event was scheduled to run, as
      this way it will always get run, no matter what.  "P" is a very
      important flag to remember.  If you do not include it in your
      events, you will not pick up any mail on outbound calls (which can
      tend to be frustrating after a while).


                             4.2: Extra Commands


      There are a few extra commands that you can use in your event
      configuration that give you more control over exactly what McMail
      does during a specific event.  All of the above commands are very
      general in their handling.  These commands will allow you to specify
      who to poll, and when, who to prevent from picking up mail, etc.

      4.2.1: ToDo

      This is where you can define whom to poll during the specific event.
      McMail will create a .FLO file for who you specify.  The flavour of
      the .FLO file is defined by a starting letter:

          P   .PLO - Special McMail poll flag.  This will be erased at the
              end of the event, and will be treated as a crash flag while
              it exists.  The Event CostMatch value has no effect on this
              flavour type.
          T   .P<task> - A task-specific poll flag.  .P01, for example,
              will only be seen by task 1.  This file is treated exactly
              the same as a normal .PLO file.
          C   .CLO - Crash flag.
          I   .ILO - Immediate flag (this will ignore the CM flag (or
              absence of it) in the nodelists so you may want to be
              careful for which systems you use this flag with to ensure
              you don't poll at a time when the system is not up).
          N   .FLO - Normal flag.
          H   .HLO - Hold flag (you will most likely never need to use
              this).
          !   Exclude the following nodespec

      If you write only part of a node number, the missing portion is
      taken from your main address.  For example, your main AKA is
      38:1403/0.  If you simply entered P1017, it would be translated to
      38:1403/1017.  A field of P6210/0 would be translated to 38:6210/0.
      and so forth.

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  48
      Section 4                                           MCMAIL<TASK>.EVT
      ────────────────────────────────────────────────────────────────────


      To send something crash to a system, you would use the following:

          ToDo C1:342/1017

      You can also tell McMail to poll only if a certain amount of bytes
      is waiting for a particular node.

          ToDo C1:342/1017,50000

      This tells McMail to call 1:342/1017 crash only if there is 50,000
      bytes, or 50Kb waiting for him.  Or else you could do something like
      this:

          ToDo P2:2426/2091,50000,2:2426/2090

      This tells McMail to create a poll flag for 2:2426/2091 only if
      there is more than 50Kb waiting for 2:2426/2090.

      McMail also has the ability to create semaphore files at the start
      of any event.  If you specify something like *MCMSCAN.ALL, McMail
      will create the semaphore file MCMSCAN.ALL in the semaphore path at
      the beginning of this event.  For example:

          ToDo *MCMSCAN.ALL

      4.2.2: Deny/Except

      This tells McMail not to send mail to the specified nodes during
      this event.  Be warned that even if the system you specify here
      polls YOU, McMail will not send them mail.  It will receive it
      (depending on your flag settings) but will not send anything, so
      this should only be used in special situations.

          Deny 1:342/1017

      This would deny mail to 1:342/1017, whether you poll him or he polls
      you.

      You can also use the keyword Except here.  This is for if you want
      to deny global networks, but wish to exclude certain nodes from the
      restriction.  For example:

          Deny 1:342/*
          Except 1:342/1017

      This would deny all mail to anyone in net 342, except for node 1017.
      1:342/1017 would be the only node permitted to pick up mail.

      If you have a modem capable of CallerID and have the service on
      your line, you can also Deny and Except calls on the basis of what

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  49
      Section 4                                           MCMAIL<TASK>.EVT
      ────────────────────────────────────────────────────────────────────

      the modem reports.  If you use "Deny idXXXX", McMail will reject any
      matches where "XXXX" is part of the reported CallerID string.  The
      "id" is treated as a keyword, and NOT part of the identification
      string.  For example:

          Deny id0441
          Except id04419400

      This will deny mail to all callers with a CallerID of "0441*" except
      for "04419400*".  You can use "Deny idRING" to deny all incoming
      calls.

      The keywords ToDo, Deny, and Except are only active for the event
      defined directly above them.  If you disable an event, you must
      disable the keywords directly below them or they will be used for
      the first previous ACTIVE event.

      The @ (global) event is a 24 hour event.  All other events can
      overlap in it.  When there is no event for a specific time, the @
      event will be used as a "filler" event, so define what you want,
      however you want.  Any way you want it, McMail can handle it.

      In MCMAIL<task>.EVT, all lines beginning with an ";" are treated as
      a comment.




























      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  50
      Section 5                            ENHANCED NODEDATA CONFIGURATION
      ────────────────────────────────────────────────────────────────────

                  Section 5: ENHANCED NODEDATA CONFIGURATION


      The Enhanced NodeData Configuration file is where you can define all
      sorts of specifics for your uplinks and downlinks, which may include
      anything from session level passwords to capability flags to
      alternate phone numbers.  It is very comprehensive, and you will
      find that it can easily fit your needs, whatever they might be.


                                5.1: NodeData


      This is the keyword to begin a node record.  Everything after this
      keyword is included into one single node record until the next
      NodeData keyword is encountered or until the end of the file is
      reached.

      5.1.1: Sysop <string>

      This is where you define the name of the sysop for this system.

      5.1.2: System <string>

      This is where you define the name of the system.

      5.1.3: Password <string>

      This is where you define the session-level password you will have
      with this system.  Make sure that this system has the same password
      defined on you in THEIR setup otherwise you will have constant
      connection password (session password) failures.  Speak to your
      uplink about this if you are not sure what your session-level
      password is.  Session-level passwords are a very good idea to have
      as it prevents (in most cases) other people from stealing your mail.

      5.1.4: Phone <string>

      The phone number of the system.  If this isn't defined, the number
      will be read out of the nodelist.  You may define more than one
      Phone statement, and McMail will dial between them randomly.

      5.1.5: Flags <flags>

      These are normal nodelist/modem flags.  McMail will add these to the
      nodelist flags, if any exist.  These will be used to compare to the
      NoCallFlags (Section 3.11.9) or OnlyCallFlags (Section 3.11.10) on
      outbound calls.  To strip an existing flag, place a "!" in front of
      the flag (ie. "!ZYX" to strip the ZYX flag from this node's entry
      in the nodelist).


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  51
      Section 5                            ENHANCED NODEDATA CONFIGURATION
      ────────────────────────────────────────────────────────────────────

      If you enter a "DX=100" in the flags portion of the NodeData
      configuration, McMail will exit with an errorlevel of 100 once it
      receives the CONNECT XXXX message from the modem.  This is called
      the DialExit function.  A file called DEXBAT<task>.BAT is created in
      McMail's main directory with the following contents:

          SPAWNDEX.BAT <task>
                        <com port>
                         <DTE speed>
                          <line speed>
                           <time to next NoBBS event>
                                         <connect add-ons>
                                                 <errorlevel>

      The DialExit feature is useful to start something like a UUCP mailer
      so you can use McMail to initially dial, but let the UUCP mailer
      take over when a connection has been established.

      If you use a "FX=???" command you can force McMail to exit with
      errorlevel ??? after every session with this node (inbound and
      outbound).

      5.1.6: Prefix <string>

      Here you can define a dial prefix, if you need a special one for
      this node.

      5.1.7: Suffix <string>

      Here you can define a dial suffix for this node.

      5.1.8: MaxAKAs <#>

      This is where you can define the maximum number of AKAs to be
      presented to this node.

      5.1.9: ZoneMatch <string>

      Only AKAs that match those in this entry will be sent to this node.
      You can also define zones and nets.  For example:

          ZoneMatch 1:342 38

      Will present only your akas of 1:342/?? and the AKAs in zone 38 to
      this node.

      5.1.10: TaskKey <string>

      Please see Section 3.23.16 for a description of this keyword.

      5.1.11: Capability <string>

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  52
      Section 5                            ENHANCED NODEDATA CONFIGURATION
      ────────────────────────────────────────────────────────────────────


      This is where you define the node capabilities for this node.  Valid
      node capability flags are:

          A   Use AKA matching for this node during outbound calls
          D   Don't use DirectZedZap
          E   Don't use EMSI
          F   Don't use FTS-1
          H   Don't use Hydra
          I   Honor rejected outcalls (see also InfoID and InfoSize below)
          S   SyncHydraSessions.  If this flag is set, McMail will only
              SEND data while RECEIVEing data.  This is only active in
              outbound calls and any HOLD mail will be handled as normal
              mail in this situation.
          Y   Don't use YooHoo
          Z   Don't use ZedZap
          1   Don't use the RequestFirst (RH1) option in Hydra sessions

      5.1.12: OutDir <path>

      This is where you can define a special outbound directory for this
      node.  A N= means normal, while H= means hold.  It is used in this
      fashion:

          OutDir N=D:\OUT\ALBERT     (normal)
          OutDir H=D:\OUT\ALBERT     (hold)

      If the character before the path is an "!" no infomail message will
      be sent to the remote unless the directory contains a file called
      MESSAGE.MCM.  If this file exists, it will be transformed into an
      info-netmail.  This file must be a plain ASCII file.  For example:

          OutDir N=D:\OUT\ALBERT

      would mean everything in the directory of D:\OUT\ALBERT would have a
      normal status (will be sent during inbound or outbound calls) and
      will create a Responsemail message.  However:

          OutDir H=!D:\OUT\ALBERT

      would mean that everything in the directory D:\OUT\ALBERT would have
      a hold status (only send during inbound calls and NOT outbound
      calls) and no Responsemail message would be created.

      If you copy files into that directory while connected to the
      matching node, those files will be sent as well.  After sending, the
      files will be erased.  You can define more than one path as well.
      For example:

          OutDir N=D:\OUT\ALBERT H=D:\OUT\ALBERT1


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  53
      Section 5                            ENHANCED NODEDATA CONFIGURATION
      ────────────────────────────────────────────────────────────────────

      5.1.13: InDir <path>

      This keyword tells McMail that a special inbound directory is in use
      for this node.  All incoming files from this node will be placed
      into this special directory.  If, for example, you have trouble with
      a node producing duplicate messages, you can have all inbound files
      saved to this directory for you to look at manually before
      processing them.

      5.1.14: CostLog <filename>

      This is where you can specify the full path and filename of a
      special CostLog file for this node alone.

      5.1.15: InfoID <string>

      This is the identification of the inbound caller as reported by
      Caller ID.  This option only works with ISDN, and the "I" capability
      flag must be set.

      5.1.16: InfoSize <#>

      This is the minimum number of bytes this caller must have on hold in
      order for the call to be answered.  For example:

          InfoSize 1000

      If there is less than 1k (1000 bytes) on gold for this node, then
      the call will be rejected and McMail will not answer the phone (see
      section 3.4.20 for more information on rejecting calls).  If this
      happens, then the remote mailer will delete the .PLO file so that it
      won't poll again.  However, if the remote mailer calls again within
      five minutes, McMail will accept the call so that important crash
      mail is received without any problems.  This feature was implemented
      to prevent your up-/down-links from wasting money if there is
      nothing or too little on hold.  Currently, this feature is only
      between McMail mailers, and it must be used with ISDN and the "I"
      capability flag must be set.

      5.1.17: CCBSize <#>

      CCBSize uses the feature of cFos v1.05 (registered) to use 2 or more
      B-Channels.  If the inbound and outbound mail (together) is bigger
      than the defined CCBSize, McMail will try to add another B-Channel.

      5.1.18: FaxFwdID <string>

      If McMail receives a FAX with this ID, a copy of the FAX will be
      sent to this node.  You can enter more than one ID or use "*" to
      forward all inbound FAXes to this node.  The ID cannot contain any
      spaces.  For example:

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  54
      Section 5                            ENHANCED NODEDATA CONFIGURATION
      ────────────────────────────────────────────────────────────────────


          FaxFwdID [phone] 9400833 44146875

      5.1.19: FaxFwdAttr <string>

      This is where you can define the status of the FAXes (as file
      attaches to this node).  Valid values are:

          IMM     Immediate
          CRS     Crash
          HLD     Hold


      Please look at the NODEDATA.CFG included with the distribution
      archive for some examples on what you can do with the NodeData
      configuration.




































      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  55
      Section 6                                 FILE REQUEST CONFIGURATION
      ────────────────────────────────────────────────────────────────────

                    Section 6: FILE REQUEST CONFIGURATION


      McMail has a comprehensive File Request system.  With its own index
      files, it makes finding FREQed files fast and convenient.  You must
      define a configuration file called REQUEST.CFG and use MCMREQIX.EXE
      to index it.  Every time you change REQUEST.CFG, you should run
      MCMREQIX.EXE again to update the index files.  There are a few rules
      for the definitions in this file:

      Session type definitions must begin with a ":".

      Magicname definitions must begin with a "@".

      Passwords MUST be the last entry on the line, and must begin with a
      "!".  Passwords are also case-insensitive and are only permitted a
      maximum of 8 characters.

      Trash-Filename definitions must begin with a "#" and MUST be stated
      before any other definitions.  They should not have wildcards to
      allow for faster access.

      If no part of a filename is given at the end of a path entry, *.* is
      assumed and used.


                               6.1: Trash-Data


      Trash-Data filenames are files that will never be sent in any
      session.  These MUST be defined first in your configuration.  Ie:

          #FILES.BBS FILES.BAK
          #FILES.IDX
          #FILES.MIX


                               6.2: Magicnames


      Protected Sessions are those where you and the remote share a
      session-level password.  Everything after the :Protected marker will
      only be available to protected systems.  Ie:

          :Protected
          @NODEDIFF   C:\MCMAIL\NODELIST\NODEDIFF.A56     !PASSWORD
          @NODELIST   C:\MCMAIL\NODELIST\NODELIST.ZIP     !PASS2

      This would only allow password-protected system to FREQ the magic
      names NODEDIFF and NODELIST, each with their own passwords.


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  56
      Section 6                                 FILE REQUEST CONFIGURATION
      ────────────────────────────────────────────────────────────────────

      Known Sessions are those where the remote is listed in one of your
      nodelists.  Everything after the :Known marker will be available to
      listed and password-protected systems.  Ie:

          :Known
          @OBLIVION   C:\FILES\BBS\OBV2-230.RAR

      This would allow both listed and password-protected systems to FREQ
      the magic name OBLIVION, without needing a password for the file.

      Unknown sessions are those where the remote is not listed in any of
      your nodelists.  Everything after the :Unknown marker will be
      available to any system, regardless of whether they are listed or
      not.  Ie:

          :Unknown
          @MCMAIL     C:\FILES\MAILER\MCM10.RAR

      This would allow all systems to FREQ the magic name MCMAIL, without
      needing a password for the file.


                            6.3: Path Definitions


      This is where you can define open paths for systems to FREQ from.
      Every file in any path definition can be FREQed, unless file
      specifications are given.  Ie:

          :Protected
          F:\FILES\SECRET\        !PASSWORD

          :Known
          F:\FILES\MCMSTUFF\

          :Unknown
          F:\FILES\MCMSTUFF\*.ZIP

      In the above example, only password-protected systems would have
      access to the files in the directory F:\FILES\SECRET, but only if
      they new the password PASSWORD.  All listed and protected systems
      could FREQ files from F:\FILES\MCMSTUFF without needing a password,
      and ALL systems could FREQ from F:\FILES\MCMSTUFF, but if they were
      unknown, they could only FREQ files with the extension of .ZIP.

      The examples shown above, and in the section previous, are not
      included in the index files.  They are read directly from the
      configuration file.


                             6.4: The Index File

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  57
      Section 6                                 FILE REQUEST CONFIGURATION
      ────────────────────────────────────────────────────────────────────



      The index file is where files available to everyone, listed,
      unlisted, or protected, are found.  This is very handy for BBS files
      you have for FREQ or CDROM files you have for FREQ.  This is where
      the McMail FileBase-Indexer (MCMREQIX.EXE) comes into play.

      To begin adding to the index file, you must use the keyword
      ":BeginIDX".  Everything after that, until the keyword ":EndIDX" is
      reached, is compiled into the index file by MCMREQIX.EXE.  You can
      also include a special index file to your master index file.  This
      is very good for CDROMs as you will only have to make an index file
      for the CDROM once and then merely merge it with the regular index
      file.  For example:

          :BeginIDX
          E:\FILES\FRONTEND\*.*
          E:\FILES\DIS\*.*
          E:\FILES\MINE\*.*       !PASSWORD
          :MergeRIX C:\MCMAIL\REQCDROM.RIX
          :EndIDX

      This does a few things.  It tells MCMREQIX that we are to include
      the files in E:\FILES\FRONTEND and E:\FILES\DIS to the index file,
      as well as the files in E:\FILES\MINE (although these files are
      password protected with the password PASSWORD).  It then tells
      MCMREQIX that we are to merge with the index file REQCDROM.RIX (.RIX
      is the extension MCMREQIX gives to compiled index files), and then
      it tells MCMREQIX to stop adding to the index file.

      This means that if new files are added to the directories
      E:\FILES\FRONTEND or E:\FILES\DIS or E:\FILES\MINE, when MCMREQIX is
      called again, only the files in those three directories are
      compiled, and the master index file is merged with the CDROM index
      file.  This way, you never have to recompile the CDROM more than
      once, saving yourself a lot of time.  To merge with another index
      file use the keyword ":MergeRIX".

      One thing you must remember is that the index configuration follows
      the ":Protected", ":Known", and ":Unknown" philosophy.  If you use
      the keywords ":BeginIDX" and ":EndIDX", the files in between that
      statement (see above example) will only be included in the Protected
      setup, ie:

          :Protected
          F:\FILES\SECRET\    !PASSWORD
          :BeginIDX
          E:\FILES\FRONTEND\*.*
          :EndIDX

      The files in E:\FILES\FRONTEND will still only be available to

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  58
      Section 6                                 FILE REQUEST CONFIGURATION
      ────────────────────────────────────────────────────────────────────

      Protected systems.  I have found it best to use the index commands
      (":BeginIDX", ":EndIDX," and ":MergeRIX") under the ":Unknown"
      heading for FREQs allowable to everyone and simply define the few
      restricted magic names or paths for protected and listed systems.


                     6.5: Including Other Configurations


      If you wish to include another configuration with the main
      configuration, simply use the keyword ":Include" and then follow it
      with the path and filename of the configuration you wish to include.
      For example:

          :Include C:\MCMAIL\REQUEST.INC

      would include REQUEST.INC with REQUEST.CFG.  This way you can
      organize your request system a little nicer or in separate files if
      you so wish.


                       6.6: External Request Processors


      McMail can also be used in conjunction with external request
      processors like XOR and AllFix.  However, you should be aware of one
      thing.  If you use an external request processor and a node who is
      listed in your Deny-List requests a file, the external request
      processor will be started regardless, so it is up to your request
      processor to check to see if the node is allowed to request or not.

      The ReqProcessor keyword in the McMail configuration files is what
      is used to call the external RP.



















      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  59
      Section 7                                        ROUTE CONFIGURATION
      ────────────────────────────────────────────────────────────────────

                        Section 7: ROUTE CONFIGURATION


      McMail has a very powerful mail and file routing system.  It is
      almost unlimited in what it can do.  McMail's internal netmail
      router relies on this configuration for where to send what, whether
      it be netmail or file attaches, and whether they originate from you
      or are pass-thru.

      It is very simple to define.  The basic syntax for the routing
      configuration is:

          <flavour>   <node> [nodes...]

      This will route mail addressed to [nodes] through <node> with a mail
      type of <flavour>.  You must specify at least two entries, a mail
      destination [nodes] and a final .PKT destination <node>.

      The flavour of the mail can be of the following:

          HLD     Hold
          NRM     Normal
          DIR     Direct (normal)
          CRS     Crash
          IMM     Immediate

      This calls for a few examples:

          HLD 1:342/52.* 1:342/52.*

      This will HOLD all mail for my points, direct to them.

          CRS 2:2426/2090 2:2426/2090.*

      This will route all mail for 2:2426/2090 and his points CRASH
      through 2:2426/2090.

          NRM 1:1/2 2:*
          NRM 1:1/3 3:*

      This will route all mail destined for zone 2 to 1:1/2 (the european
      fido zonegate) and all mail destined for zone 3 to 1:1/3 (the
      australian fido zonegate).  All of the mail will be flagged as
      NORMAL, which means it will only be sent out when specifically told
      to.

      The routing will be processed from the top of the file down, until a
      match is made.  This means that any specifics should be made before
      any globals are made.

      If McMail doesn't find a matching entry in the routing

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  60
      Section 7                                        ROUTE CONFIGURATION
      ────────────────────────────────────────────────────────────────────

      configuration, the mail will be flagged HOLD and routed direct to
      the destination address.

      If mail has the file request status set and it is not local, the
      request status will be stripped.  This prevents systems from sending
      a file request message to you, to be routed somewhere else, and thus
      you FREQing a file you didn't want.

      File routing is handled in the same manner.  You only have to add
      the keyword FILES before the routing information.  For example:

          FILES NRM 1:342/0 1:342/*

      This will route all files for any nodes in net 342 to 1:342/0.

      In-transit file attaches with no matching file-routing statements
      will be flagged as HOLD and routed direct.

      If you place a ! in front of a nodespec, that nodespec will be
      excluded from the command string.  For example:

          NRM 1:342/0 1:342/* !1:342/1017

      This will route all mail for any nodes in net 342 to 1:342/0, except
      for node 1:342/1017.

      Please take a look at the included ROUTE.MCM for more examples.

























      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  61
      Section 8                            MODEM RESPONSE TRANSLATION FILE
      ────────────────────────────────────────────────────────────────────

                  Section 8: MODEM RESPONSE TRANSLATION FILE


      McMail has a very comprehensive way of dealing with the response
      codes given by your modem.  The translation file gives you a lot of
      flexibility where response messages are concerned.

      The basic syntax for each line in the translation file is:

          <keyword>: <alternate response>

      If a keyword is found in the original modem response, the alternate
      response is given back and used.

      There are three macros you can use for the alternate response:

          $A  AlertBeep (McMail will give a short beep here, see also
              ALERTSOUND in MCMAIL<task>.CFG (Section 3.23.10)
          $E= Exits McMail with an errorlevel (ie. $E=100 would exit with
              an errorlevel of 100)
          $O  Insert the original response message (if the first word is
              RING, it will be stripped)

      A few examples:

          RING UNKNOWN: Unidentified Caller, Skipping...

      This will prevent McMail from answering the phone on calls with
      CallerID blocking enabled.

          CONNECT 19200: CONNECT 9600

      This might be necessary in the oddest of situations, but what it
      does is whenever the modem sends a CONNECT 19200, McMail will
      translate it to CONNECT 9600 and will connect at 9600 instead of
      19200.

          RING 04419400834: RING McMail/HQ is calling!

      This will display "RING McMail/HQ is calling!" instead of "RING
      04419400834".  If you choose to do something like this you MUST
      remember to include a "RING" in the alternate response otherwise
      McMail won't answer the phone.

      For more examples, look at the TRANSLAT.COD file included in the
      release archive.






      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  62
      Section 9                                              COSTING TABLE
      ────────────────────────────────────────────────────────────────────

                           Section 9: COSTING TABLE


      The Costing table for McMail is very powerful and very flexible, and
      it will meet all of your needs easily.  However, it is a little
      daunting to look at, at first, but since it isn't 100% crucial to
      the operation of McMail, don't kill yourself trying to set it up at
      first.  It will take a little time.

      First thing you must remember, is in MCMAIL<task>.CFG the "Currency"
      keyword.  This must be accurate for proper display.  In Canada and
      the USA use:

          Currency . , 100 2

      The default is "Currency , . 100 2".  This tells McMail how to write
      the currency (the first character is the decimal delimiter, then the
      thousand delimiter, then the divisor amount (ie. 100 cents to one
      dollar) and then the decimal digits).

      The first thing you have to define in the costing table are the
      cost-zone keywords.  This is where you specify part of an
      international phone number to a cost-zone keyword equivalent.  The
      syntax is:

          <number> <keyword>

      For example, in Canada/USA you would use:

          1-403-  Local
          1-604-  Canada
          1-312-  UStates

      This tells McMail that the international prefix of 1-403- belongs to
      your Local calling area, that 1-604- belongs to the Canada group,
      and that 1-312- belongs to the United States.  You should do this
      with all international phone prefix's (whether local, regional, or
      international).  You may use any cost-zone keywords you like, as
      long as you realize that the maximum length of the keyword is 20
      characters.

      The second part of the costing table is the most difficult one to
      understand, but once understood is fairly easy to deal with.  It is
      also structured for a lot of flexibility.  This is where you define
      the different cost units and time units to the cost-zone keyword
      that you defined in the first part of the costing table.  It follows
      this basic syntax:

          <keyword> <weekday> <timebar> <t1>,<cu1>,<tu1> <t2>,<cu2>,...

      where

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  63
      Section 9                                              COSTING TABLE
      ────────────────────────────────────────────────────────────────────


          <keyword> is the cost-zone keyword defined in the first part of
          the cost table

          <weekday> is the day of the week that this definition is active
          for

          <timebar> is the actual timebar (see below)

          <t1> is the matching tag in the timebar for definition 1

          <cu1> is the cost unit per time unit for tag <t1>

          <tu1> is the time unit in 1/10 seconds for tag <t1>

          <t2> is the matching tag in the timebar for definition 2

          <cu2> is the cost unit per time unit for tag <t2>

          <tu2> is the time unit in 1/10 seconds for tag <t2>

      etc.

      For the <weekday> you can use a few different values.  You can use
      "Mon" or "Tue" for a specific day of the week (Monday or Tuesday,
      etc.), you can use "All" for every day of the week, and you can use
      "DDMM" where MM is the number for a month and DD is the number for a
      day.  A value of "2512", for example, would mean Christmas day.  It
      is also possible that in the <weekday> field, you can write multiple
      days like in the event configuration file.  You can write something
      like "Sun+Sat+2512+2612" for example to mean ALL Saturdays, Sundays,
      Christmas days, and day-after-Christmas days.

      The configuration list will be processed "top down", meaning what is
      listed first in the file will be processed first.  This means that
      any "default" definitions have to be listed FIRST.  If there are two
      similar definitions for the same cost-zone keyword, the SECOND
      definition will be used over the first.

      The tags you use in the timebar can be any character between A-Z
      that you like.  However, if you use a tag, you MUST remember to
      define the tag for cost unit and time unit.  You could use, for
      example a tag of "D" for day, "N" for night, "H" for holidays, etc.

      The timebar.  What is it?  It is the structure that McMail reads to
      find out what time/cost unit period it is in.  It is split up into
      30 minute intervals.  The best way to make things easy for you to
      plan in your cost table file is to use the following "header" in
      your files to make it easy to read:

          ;       0                   1                   2

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  64
      Section 9                                              COSTING TABLE
      ────────────────────────────────────────────────────────────────────

          ;       0.1.2.3.4.5.6.7.8.9.0.1.2.3.4.5.6.7.8.9.0.1.2.3.

      This gives you a time "bar" from 00:00 to 24:00.  Each "."
      represents the half-hour mark.  Let's take a look at a few
      examples:

          ;         0                   1                   2
          ;         0.1.2.3.4.5.6.7.8.9.0.1.2.3.4.5.6.7.8.9.0.1.2.3.
          Local All NNNNNNNNNNNNNNNNDDDDDDDDDDDDDDDDDDDDNNNNNNNNNNNN
          Local Sat NNNNNNNNNNNNNNNNDDDDDDDDDDDDDDDDDDDDNNNNNNNNNNNN
          Local Sun NNNNNNNNNNNNNNNNDDDDDDDDDDDDDDDDDDDDNNNNNNNNNNNN

      This example shows how the timebar works.  Here we define the
      cost-zone keyword "Local" (which we had previously defined in the
      file as "1-403- Local").  In the above example, the definition for
      "All" is used every day EXCEPT for Saturday and Sunday.

      In the above example, we have also defined the tag N for night and D
      for day.  The above example, however, is missing the most crucial
      part.  The cost calculation.  For Canada/USA, we are generally
      billed in 1 minute increments, so we should define our cost table
      to reflect that.  This means that we are billed in pennies per tenth
      of a second, and there are 600 tenths of a second in a minute, so
      the extension to the above timebar would look like:

          Local All ... D,00,600 N,00,600
          Local Sat ... D,00,600 N,00,600
          Local Sun ... D,00,600 N,00,600

      Because we are defining a calling area local to us (meaning that we
      don't have to pay in order to call them), we define tag "D" (day) as
      00 cents per 600 tenths of a second, or 0 cents per minute.  Same
      with tag "N" (night).

      Now let's look at a larger scale example of calling long distance
      within Canada.

          1-403- Can
          1-416- Can
          1-418- Can
          1-604- Can
          [...]
          ;       0          1             2
          ;       0.1.2.3.4[.].1.2.3.4.[.].0.1.2.3.
          Can All NNNNNNNNN[.]DDDDDDDDD[.]NNNNNNNNN D,50,600 N,25,600
          Can Sat NNNNNNNNN[.]DDDDDDDDD[.]NNNNNNNNN D,45,600 N,20,600
          Can Sun NNNNNNNNN[.]DDDDDDDDD[.]NNNNNNNNN D,40,600 N,10,600

      The timebar is shortened in order to fit on the page, but I'm sure
      you get the basic picture (just imagine an entire timebar there).
      Ok, here goes the explanation:

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  65
      Section 9                                              COSTING TABLE
      ────────────────────────────────────────────────────────────────────


      Canada, every day of the week, during the day costs 50 cents per
      minute (600 tenths of a second), and during the evening costs 25
      cents per minute.  This holds true for every day of the week, except
      for Saturday and Sunday.

      Saturday, during the day, you are paying 45 cents per minute, and
      during the evening you are paying 20 cents per minute.  On Sundays,
      you pay 40 cents per minute during the day, and 10 cents per minute
      during the evening.

      As you can see, its not very difficult to setup your cost
      calculation tables.  The above were very easy examples of what you
      can do, however, you can make your tables far more complex to suit
      your every need, based on holiday, day of the week, etc.  You can be
      extremely specific, or very general.  McMail's cost calculation
      tables give you the ability to choose how you want your own cost
      calculation performed.

      The cost calculations defined here are used in the main mailer WFC
      screen (see section 12.2) as well as the cost log and the general
      log.  All estimates for cost in the event definition file are also
      based on the data in this file, so you may want to keep all of this
      in mind when you are working on the event file and the cost table
      file.



























      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  66
      Section 10                                   MCMAIL NODELIST-INDEXER
      ────────────────────────────────────────────────────────────────────

                     Section 10: MCMAIL NODELIST-INDEXER


      McMail comes with its own nodelist indexer (MCMNODE.EXE).  This can
      be used instead of the Version7 nodelist indexes, if you wish.
      Some people may prefer it as McMNode's index files are extremely
      small.  The configuration file, MCMNODE.CFG, is really simple.  It
      follows this basic syntax:

      NodelistPath <path> <zones to add to the fido userlist>
      ;
      Nodelist <domain> <default zone>:[<net>] <nlist.1> [<nlist.2>] ...
      ;
      Pointlist <default zone> <plist.1> [<plist.2>] ...

      All of the entries in []'s are optional.  You may define only one
      NodelistPath statement, and as many Nodelist and Pointlist
      statements as you like.  For example:

          NodelistPath c:\mcmail\nodelist 1 38 111
          Nodelist fido 1   nodelist.#
          Nodelist dni  38  daemon.#
          Nodelist stn  111 stnlist.#
          Pointlist 111 mystnpt.#

      This will find the nodelist files in the path C:\MCMAIL\NODELIST and
      add zones 1, 38, and 111 to the FIDOUSER.LST file.  The first
      nodelist's domain is "fido", with a zone of 1, and the file is
      NODELIST.# (where # (or *) is replaced with the highest day number
      McMNode can find).  The same is done for nodelists DAEMON and
      STNLIST.  And finally, pointlist MYSTNPT is added to the
      FIDOUSER.LST as well.  Please note that the pointlists are added
      ONLY to the FIDOUSER.LST file.

      Also, in regards to pointlists, McMNode can handle the 3D and 4D
      Boss formats.

      Now you must make sure that you define the same thing in
      MCMAIL<task>.CFG with the "Domain" keywords.  For the above
      configuration, you might have the following in your main McMail
      configuration file:

          Domain fido    fido 1
          Domain dni     dni  38
          Domain stn     stn  111

      Where the basic syntax is:

      Domain <domain name> <nodelist index> <default zone>

      There is one main thing you must remember here.  McMNode compiles

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  67
      Section 10                                   MCMAIL NODELIST-INDEXER
      ────────────────────────────────────────────────────────────────────

      the nodelist indexes according to the DOMAIN NAME.  So, in the above
      examples, the FidoNet index would be FIDO.MMI, not NODELIST.MMI.  So
      the domain name you define in MCMNODE.CFG is the nodelist index you
      define in MCMAIL<task>.CFG.

      If you do not use domains, then you MUST set the domain to "nodex"
      in MCMNODE.CFG.  So if we did not use domains, our MCMNODE.CFG would
      look like this:

          NodelistPath c:\mcmail\nodelist 1 38 111
          Nodelist nodex 1   nodelist.#
          Nodelist nodex 38  daemon.#
          Nodelist nodex 111 stnlist.#
          Pointlist 111 mystnpt.#

      The commandline parameters for MCMNODE.EXE are:

          /F       Force compile nodelists, even old nodelist
          /U       Create a fido userlist (FIDOUSER.LST) that is used for
                   nodelist browsing
          /UC      Create a fido userlist that is compatible with some
                   message editors
          /D       Delete old nodelists (will only delete nodelists of an
                   older day-of-the-year extension than the newest)




























      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  68
      Section 11                                        TERMINAL PHONEBOOK
      ────────────────────────────────────────────────────────────────────

                        Section 11: TERMINAL PHONEBOOK


      McMail comes with its own terminal package.  This terminal package
      relies on an external file defined in MCMAIL<task>.CFG under the
      keyword PHONEBOOK (Section 3.9.3) for its dialing directory.


                          11.1: BBS-System <string>


      This is the keyword to begin the definition for a single BBS system,
      and also includes the name of the system as <string>.

      11.1.1: Sysop <string>

      The name of the sysop of this system.

      11.1.2: Password <string>

      Your password on the system.

      11.1.3: Phone <string>

      The phone number of the system.  This number MUST be in
      international format!  McMail will dial according to the dialing
      definitions in MCMAIL<task>.CFG under the keyword DIAL (Section
      3.12.11).

      11.1.4: Prefix <string>

      The dialing prefix for this BBS.

      11.1.5: Suffix <string>

      The dialing suffix for this BBS.

      11.1.6: Capability <string>

      The IEMSI capability of this system that you will use.  Valid
      choices are:

          NEWS    Show bulletins, announcements, etc.
          MAIL    Check for new mail.
          FILE    Check for new files.
          HOT     Enable hot-keys.
          CLR     Enable screen clearing.
          HUSH    Do not disturb.
          MORE    Enable page pausing (otherwise known as "more" prompts).
          FSED    Enable the system's full screen editor.


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  69
      Section 11                                        TERMINAL PHONEBOOK
      ────────────────────────────────────────────────────────────────────

      So, for example, you might use the following:

          Capability NEWS,HOT,CLR,MORE,FSED

















































      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  70
      Section 12                                            RUNNING MCMAIL
      ────────────────────────────────────────────────────────────────────

                          Section 12: RUNNING MCMAIL


      Now that you have setup your configuration files and have everything
      defined and setup the way you want to, its time to fire up McMail.


                             12.1: The Batchfile


      The first thing you'll need to do before you can have McMail running
      fluidly to answer calls, make calls, drop to your mail tosser and
      file tosser, etc., is a good batchfile.

      Take a look at section 15 for the predefined errorlevels McMail
      will give.  Anything other than those errorlevels you may define for
      external utilities and actions McMail will take during different
      circumstances.  These errorlevels are ones that you will define in
      your configuration.  A very simplistic batch file would be the
      following:

          @echo off
          :start
          cd %mcm%
          mcmail

          if errorlevel 255 goto fatal
          if errorlevel 254 goto nomodem
          if errorlevel 253 goto nospace
          if errorlevel  50 goto unpack
          if errorlevel   0 goto done

          goto start

      This simple batchfile takes care of the four pre-defined McMail
      errorlevels, as well as contains an errorlevel for received mail
      (50).  You must know a little DOS batch programming in order to
      write a proper batchfile for your mailer, but it doesn't need to be
      elaborate or complex, although it certainly can become so.


                           12.2: McMail Main Screen


      The McMail main screen has many different aspects to it.  It is
      divided up into little windows to make things easier for you to keep
      an eye on, and the special online keys can help you navigate through
      and toggle the various windows.

      12.2.1: Settings/Flow


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  71
      Section 12                                            RUNNING MCMAIL
      ────────────────────────────────────────────────────────────────────

           McMail 1.0 ■ 38:1403/0 ■ Task: 1
          ┌Settings─────────┬Flow─────────────┬
          │Port : xFos COM 1│BBS: 628 FEV:   0│
          │Speed:     115200│Out: 302 In:  339│
          │Event: @ n@,24:00│   11.9M    55.7M│
          │Flags: 9       IP│Cost:        7.70│
          └─────────────────┴─────────────────┴
          + 15:37:07 Hang up the line
          # 15:37:22 Scanning Outbound...

      The above is a screen capture of the top left-hand side of the
      McMail main screen.  On the first line it identifies the version
      number, the main address of the system, and the task (line/node)
      number.

      Below that, you see a box called "Settings".  This box shows you
      what is defined for this node at this time.  The "Port" setting
      shows you what mode you are in and what COM port you are using.  In
      the above screen the system is using COM 1 with xFos (External
      fossil driver).  Instead of xFos you may see cFos for the ISDN
      fossil driver, or ASYNC for the internal "fossil" driver.  The
      "Speed" setting shows what the current port is locked at (in this
      case 115200bps).  Below that you see "Event".  This tells you what
      event is active.  The "@" event (or 24hr global event) is currently
      active, and the next event is also the "@" event at midnight (shown
      by the "n@,24:00" token).  Below that, the "Flags" setting shows
      what event flags are active in this event (in this case Immediate
      mail only and Pickup mail on outbound calls).  You also see the
      number 9 there.  That means there is 9 seconds until the next
      outbound scan (it is a countdown token).

      The box directly beside the "Settings" window is the "Flow" window
      and this window shows all the flow data for this task.  The "BBS"
      portion shows how many BBS callers have called the system.  The
      "FEV" portion shows the number of FAX, External Mail, and Voice
      calls that were received.  The "Out" and "In" tokens show how many
      mail calls have been made outbound, and how many mail calls have
      been answered inbound.  The numbers below them show the amount of
      data (in bytes, Kbytes, Mbytes, etc.) have been exchanged outbound
      and inbound.  And finally "Cost" shows the cost of the outbound
      calls, according to your settings in the cost table.  In the above
      example, $7.70 has been accounted for in outbound calls.

      Finally, the text below the top window is the screen log.  This is
      what shows you exactly what McMail is doing, and can show as much,
      or as little, detail as you configured in the configuration.

      12.2.2: Whats On Hold




      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  72
      Section 12                                            RUNNING MCMAIL
      ────────────────────────────────────────────────────────────────────

                                  Sun 05 May 21:33:03
          ┬Whats on Hold─────────────────────────────┐
          │1:342/1.0             N    917b   1F      │
          │1:342/52.1            N     51b   1F    1D│
          │1:342/5013.0          N    3.8K   1F      │
          │1:3417/20.0           N    6.7K   1F      │
          ┴──────────────────────────────────────────┘

      The above shows the top left-hand side of the McMail screen.  This
      is a variable window.  Above, it is the WOH window, but it can be
      many windows which you can toggle as well.  The first line shows the
      date of the system and the time (this is the same line as the one
      that identifies the task, main address, and McMail version).  The
      window itself is directly next to the "Flow" window.

      The WOH window merely shows what your system has in its outbound
      "queue".  You can use the arrow keys to scroll up and down the list.
      The first thing it shows on any line is the address of the node
      mail/files are waiting for.  Next, it shows the status of the
      mail/files.  "I" means immediate, "N" means normal, "H" means hold,
      "P" means poll, "C" means crash.  Next to that the size of what is
      on hold is displayed, in bytes, Kbytes, or Mbytes.  Beside that it
      shows how many files are waiting to be sent.  1F means one file, 2F
      means two files, etc.  And finally after that, you will see how many
      days the mail has been waiting to go out.  1D meaning one day, 2D
      meaning two days, etc.  You will not always see something in that
      column.  If you don't, it means the mail has been updated or is new
      as of that day.  If you see the word SENT, it means that the mail
      has been sent, but the window has not yet been updated.  If you
      press ALT-W, the WOH window will be updated, and the line containing
      the word SENT will disappear.

      12.2.3: Last Sessions

          ┬Last Sessions─────────────────────────────┐
          │Out: IVsoft Server               411:411/0│
          │     13:37    1 min   1201 cps       Known│
          │In : Razor's Domain ][          111:6210/0│
          │     05:59    0 min     73 cps   Protected│
          ┴──────────────────────────────────────────┘

      This is a window that takes place of the WOH window when you press L
      or H at the main screen.  This window shows the last inbound and
      outbound sessions.  It shows the time of the connection, the time
      spent connected, the average CPS rate, the address and name of the
      system, and whether it was a Protected/Known/Unknown system.  Only
      the latest inbound and outbound connections are shown.

      12.2.4: Out- Sessions



      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  73
      Section 12                                            RUNNING MCMAIL
      ────────────────────────────────────────────────────────────────────

          ┬Out- Sessions─────────────────────────────┐
          │05 01:57 Quantum Alliance          20:20/0│
          │05 05:00 PCWindows Support BBS  1:342/5013│
          │05 10:48 PCWindows Support BBS  1:342/5013│
          │05 13:37 IVsoft Server           411:411/0│
          ┴──────────────────────────────────────────┘

      This is another window that replaces the WOH window by pressing O or
      toggling through by pressing H at the main screen.  This screen
      shows the day of the month, the time, the name of the system you
      called, and the node address of the system.  You can scroll through
      this window with the arrow keys.  If you press enter on a
      highlighted entry you will see some information on that session.  It
      will show you the total bytes that came in, that went out, and the
      total amount of bytes in and out.  It will also show the baud rate,
      the average CPS rate, the cost of the session, the starting time of
      the session, the date, and the amount of minutes the session lasted.

      12.2.5: In - Sessions

          ┬In - Sessions─────────────────────────────┐
          │05 19:31 Lasher's Point Syste  38:1403/0.3│
          │05 19:33 The Generica BBS      411:230/103│
          │05 20:38 Quantam Alliance        1:342/824│
          │05 21:19 C+Net BBS              1:342/1017│
          ┴──────────────────────────────────────────┘

      This is another window that replaces the WOH window by pressing I or
      toggling through by pressing H at the main screen.  This screen
      shows the day of the month, the time, the name of the system who
      called you, and the node address of the system.  You can scroll
      through this window with the arrow keys.  If you press enter on a
      highlighted entry you will see some information on that session.  It
      will show you the total bytes that came in, that went out, and the
      total amount of bytes in and out.  It will also show the baud rate,
      the average CPS rate, the cost of the session, the starting time of
      the session, the date, and the amount of minutes the session lasted.

      12.2.6: MultilineInfo

          ┬MultilineInfo─────────────────────────────┐
          │1:                                    DOWN│
          │2:                                    Idle│
          │                                          │
          │                                          │
          ┴──────────────────────────────────────────┘

      This is another window that replaces the WOH window by pressing M or
      toggling through by pressing H at the main screen.  This screen
      shows the status of your other McMail tasks.  In the above screen
      capture, we see that task 1 is DOWN (due to a BBS caller) and that

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  74
      Section 12                                            RUNNING MCMAIL
      ────────────────────────────────────────────────────────────────────

      task 2 is sitting idle, waiting for a call.

      12.2.7: Online Keys


      There are a few keys you can use while McMail is sitting in its
      main Waiting For Call screen.  These online keys will help you get
      the most out of your McMail system.

          H        Toggle History/InterTask/WOH-Window
          L        Switch directly to LastIn/LastOut
          O        Switch directly to Out-Sessions
          I        Switch directly to In-Sessions
          M        Switch directly to Multi-line view
          W        Switch directly to WOH view

          S        Scan outbound immediately
          B        Bundle (route) netmail
          N        Start the personal mail scanner
          T        Change event flags temporarily (effective until next
                   shutdown)
          F        Clears the flow data
          ?        Information on McMail

          ALT-A    Manually answer the phone
          ALT-C    Call node/name once (you can enter in the phone number
                   of unlisted nodes by pressing E when prompted
                   "OK ? Y/n/e")
          ALT-D    Invokes Terminal mode
          ALT-H    Help screen
          ALT-I    Manually initialize the modem
          ALT-J    Invokes a DOS shell
          ALT-L    Log file scrolling with keys:
                     F   Search text
                     N   Search again (next)
                     ESC Quit
          ALT-M    Invokes pop-up menu
          ALT-O    Invokes Outbound Manager
          ALT-P    Poll node/name
          ALT-R    Request files from another system (FREQ)
          ALT-S    Send files to another system
          ALT-U    Clears the history and BadTransfer files (this is
                   normally done automatically at midnight)
          ALT-V    Restarts the current event
          ALT-W    Update WOH (What's On Hold) Information
          ALT-X    Exit (errorlevel 0)
          ALT-Z    Zoom the Info-Window (this cuts the log screen to half
                   the screen and puts the WOH window as the other half of
                   the screen, with the use of normal Info-Window toggling
                   keys)
          CTRL-B   Toggles BBSNext information

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  75
      Section 12                                            RUNNING MCMAIL
      ────────────────────────────────────────────────────────────────────

          CTRL-D   Toggles Crash dialing (no try counter, no waiting)
          CTRL-L   Lock keyboard (must have the keyboard password defined
                   (see section 3.23.8)
          CTRL-P   Toggles the Password-Override feature
          CTRL-ENT In Multiline mode, McMail shows the header and the last
                   three log entries of the corresponding line.  In WOH
                   mode, McMail calls the highlighted node
          ENTER    Dependant on the history menu, ENTER will do:

                   Whats on Hold: Shows information on highlighted node
                   Out- Sessions: Shows history information on the
                                  highlighted session (includes bytes
                                  in/out/total, the baud rate, average CPS
                                  rate, the cost, starting time, the date,
                                  and the amount of minutes the session
                                  lasted).
                   In- Sessions : Shows history information on the
                                  highlighted session (with the same
                                  information as the Out- Sessions).

          Up/Dn    Scrolls text in the history window
          PgUp     Scrolls text in the history window
          PgDn     Scrolls text in the history window
          Pos1     Scrolls text in the history window
          End      Scrolls text in the history window

          PgUp     Adds a B-Channel during mail transfer
          PgDn     Removes a B-Channel during mail transfer (both PgUp and
                   PgDn will only work with cFos/pro v1.03 or higher in
                   CCB-Mode)

          CTRL
           PgUp    Start upload in Terminal mode
           PgDn    Start download in Terminal mode

      To use the name calling feature for ALT-C and ALT-P, you must enter
      in the name as it would appear in the FIDOUSER.LST.  For example,
      you would have to enter "Danen, Vincent" as opposed to "Vincent
      Danen".  Again, this will depend on your nodelist compiler, as some
      nodelist compilers create the FIDOUSER.LST file differently.

      12.2.8: Status Line


      McMail has a small status line at the very bottom of the screen
      where on the left side it displays "AltM-Menu AltH-Help ?-Info".  On
      the right side of this status line you may see small characters
      every once in a while.  These characters have special meanings.

          !   No-Connect mark found (McMail had called without connecting
              or receiveing a busy signal)

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  76
      Section 12                                            RUNNING MCMAIL
      ────────────────────────────────────────────────────────────────────

          $   Dial-Overtry mark found (McMail had dialed a node to the
              maximum defined tries and will not dial anymore)
          #   Handshake-Failure mark found (McMail connected to a system
              but had a handshake failure and will not call that system
              anymore)
          BN  BBSNext is active on the next outbound call.


                          12.3: The Outbound Manager


      The Outbound Manager is an integrated, menued way for you to manage
      your outbound mail.  Pressing ALT-O from the Waiting For Caller
      screen will bring up the outbound manager with a list of all the
      zones you are in for your networks.  Each zone is represented as a
      "<DIR>" directory.  Your default zone is the first on the list, and
      after that the zones are listed numerically.

      There are a few keys you can use while in the Outbound Manager.

          ALT-B    Go one directory back
          ALT-C    Change mail status of highlighted packet/attach
          ALT-D    Sort by DOS
          ALT-E    Sort by Extension
          ALT-G    Go to Zone
          ALT-H    Help
          ALT-N    Sort by Name
          ALT-O    Sort Descending/Ascending
          ALT-R    Readdress highlighted packet/attach
          ALT-S    Sort by Size
          ALT-T    Sort by Date/Time
          ALT-Z    Zoom Window
          DEL      Toggle delete mark on highlighted bundle/attach
          CTRL-D   Delete marked bundles/attaches
          CTRL-S   Show ?LO file size
          CTRL-ENT View highlighted bundle
          ENTER    Accesses zone directory or shows who the highlighted
                   bundle/attach is going to
          TAB      Toggles Raw mode on/off (Raw mode shows the filenames
                   instead of the node addresses)


                             12.4: Dumb Terminal


      McMail has it's own Dumb Terminal that you can use instead of using
      an external one.  It is called by using ALT-D from the main McMail
      screen.  It has a variety of commands you can use:

          ALT-A    Toggle ANSI graphics on/off
          ALT-B    Enter phonebook

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  77
      Section 12                                            RUNNING MCMAIL
      ────────────────────────────────────────────────────────────────────

          ALT-C    Call node/name (you can enter in the phone number
                   of unlisted nodes by pressing E when prompted
                   "OK ? Y/n/e")
          ALT-D    Deletes the batch upload tag list
          ALT-E    Toggle IEMSI on/off
          ALT-H    Shows help
          ALT-I    Initialize modem
          ALT-L    Show capture file
          ALT-M    Invokes the menu
          ALT-P    Toggle capture on/off
          ALT-Q    Clear the dial queue
          ALT-T    Create a batch upload tag list
          ALT-X    Hangup / Exit terminal
          ALT-=    Toggle Raw Mode (Alt`)

          CtrlPgUp Start Upload
          CtrlPgDn Start Download

          PgUp     Adds a B-Channel during ISDN connections
          PgDn     Removes a B-Channel during ISDN connections (both PgUp
                   and PgDn will only work with cFos/pro v1.03 or higher
                   in CCB-Mode)

      The dial queue in the terminal will be scanned every nine seconds
      when cycling between different BBS systems to call.


                                12.5: BBSNext


      BBSNext is a special feature currently only available in McMail
      mailers.  This feature, when turned on, will call the specified node
      to send and receive mail.  Once the mail session is done, McMail
      will send a BBSNext "request" to the remote mailer.  If the remote
      has BBSNext disabled, it will not send back the BBS-FLAG.  If McMail
      receives the BBS-FLAG after having sent the BBSNext request, McMail
      will launch the dumb terminal, shell to DOS and load the terminal
      program or exit with an errorlevel (as specified with the keyword
      ExtTerminal (see section 3.9.2)) to create TRM<task>.BAT which will
      load SPAWNNXT.BAT and load your external terminal.

      This feature is particularly useful between long distance systems as
      it saves you from having to pay the connection fee again (which you
      would pay by polling, dropping carrier, and then dialing from your
      terminal).


                       12.6: Miscellaneous Information


      Almost everything has been covered so far in the manual in regards to

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  78
      Section 12                                            RUNNING MCMAIL
      ────────────────────────────────────────────────────────────────────

      running McMail.  There are, however, some little miscellaneous bits
      of information I had no idea where to put, so I decided to make a
      section for it.  Some of this may mean nothing to you, but some may
      find it helpful information.

      Whenever McMail is about to send any information that has a
      drive-specific "tag" to it, McMail will check to see if that drive
      exists, and if it doesn't it will hang up the line.  For example, if
      a file request comes through for a file configured to be on drive D:
      but drive D: doesn't exist, McMail will hang up.

      When a node is marked undialable (due to a bad connection, or having
      reached maximum tries for busy, etc.) McMail will not only create the
      ????????.&?? semaphore in the outbound directory, it will also write
      a netmail message to the sysop informing the sysop of the change and
      why.




































      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  79
      Section 13                                         MCMAIL LINEVIEWER
      ────────────────────────────────────────────────────────────────────

                        Section 13: MCMAIL LINEVIEWER


      The McMail LineViewer is like the "central control centre" for
      McMail.  It allows you to monitor all of your tasks from one
      location.  You will see portions of each task and can send specific
      commands to any given task you choose.

      McMView can use its own configuration file as well, and this
      defaults to MCMAIL0.CFG, unless the TASK= environment variable is
      set.  It can be run just like any other task of McMail, except
      without a modem.  You can get McMView to deal with mail as it comes
      in, or package mail, without disturbing any of the other tasks.

      Another alternative to McMView is to use it as a simple line monitor
      that does nothing more than let you know what each task of McMail is
      doing at any given time.  You can, instead, use a NoModem task of
      McMail (for example, MCMAIL1.CFG (task 1) is a local, no modem task
      to simply toss and scan mail and files, while MCMAIL2.CFG (task 2)
      is the task that answers the phone, passes human callers to the BBS,
      etc.) which is perhaps more versatile in doing maintenance and
      responding to semaphores than McMView is.  The choice is up to you,
      and both will work, and provide you with many options as well.

      The commandline syntax for MCMVIEW.EXE is:

      MCMVIEW.EXE <task 1> [<task 2>] ... [<task N>] [</c:x:\cfgfile>]

      For example:

      MCMVIEW.EXE 1 2 3 /c:c:\mcmail\mcmail.cfg


                              13.1: Online Keys


      There are quite a few keys you can use while you are in McMView.

          B        Bundle (route) netmail
          N        Scan for personal netmail
          ?        Product information

          ALT-J    Shell to DOS
          ALT-L    Scroll log file
          ALT-O    Outbound manager
          ALT-P    Poll a node/name
          ALT-R    Request files from a node
          ALT-S    Send files to a node
          ALT-U    Restart event
          ALT-X    Exit with errorlevel 0
          CTRL-L   Lock keyboard

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  80
      Section 13                                         MCMAIL LINEVIEWER
      ────────────────────────────────────────────────────────────────────


          Up/Dn    Navigate through task windows

      The following are called Line-Control Keys and are used while "in"
      specific tasks:

          L        Switch directly to LastIn/LastOut
          O        Switch directly to Out-Sessions
          I        Switch directly to In-Sessions
          M        Switch directly to Multi-line view
          W        Switch directly to WOH view

          CTRL-B   Bundle (route) netmail for this task
          CTRL-H   Toggle SleepMode for this task
          CTRL-K   Kill connection for this task (when in session)
          CTRL-N   Scan for personal netmail
          CTRL-S   Scan outbound
          CTRL-W   Update the Whats On Hold data
          CTRL-X   Exit with errorlevel 0

































      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  81
      Section 14                                  MCMAIL INTERTASK-PATCHER
      ────────────────────────────────────────────────────────────────────

                     Section 14: MCMAIL INTERTASK-PATCHER


      The McMail Intertask-Patcher (MCMPINT.EXE) is a very simple little
      program with one simple function.  It is used to update the
      Multiline Info window in McMail.  It is called like this:

          MCMPINT.EXE <task> <text>

      where

          MCMPINT.EXE 2 Human Caller On BBS

      would show the following in the Multiline Info window:

          ┬MultilineInfo─────────────────────────────┐
          │1:                                    Idle│
          │2:                     Human Caller On BBS│
          │                                          │
          │                                          │
          ┴──────────────────────────────────────────┘

      This is MCMPINT's sole function, and is useful especially in
      multiline environments.




























      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  82
      Section 15                                    ERRORS AND ERRORLEVELS
      ────────────────────────────────────────────────────────────────────

                      Section 15: ERRORS AND ERRORLEVELS


      McMail exits with a few different errorlevels if it cannot run:

          255     Fatal error
          254     Modem initialization error
          253     Not enough disk space to operate
            0     ALT-X from within McMail (operator exit)

      If you encounter a fatal error (errorlevel 255) please notify one of
      the authors immediately as this is a serious problem that must be
      looked into.







































      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  83
      Section 16                                                CONCLUSION
      ────────────────────────────────────────────────────────────────────

                            Section 16: CONCLUSION

                16.1: Registration Sites/Help Systems/Support


      Germany Help and Registration (authors):

               Gordian Schuermann
               Franz-Reyersbach-StraBe 6b
               26133 Oldenburg, Germany

               Tel: [phone]             (BBS/FAX)   24hr
                    [phone]           (BBS/FAX)   24hr
                    [phone]           (BBS/ISDN)  24hr
                    [phone]           (BBS/ISDN)  24hr

               Netmail: 2:2426/2001@fidonet
                        2:2426/2002@fidonet
                        2:2426/2003@fidonet
                        2:2426/2004@fidonet

               InterNet:   [e-mail]
               WWW:        http://home.t-online.de/home/mcmailhq

               Albert Freriks
               Schilfgraben 3
               26389 Wilhelmshaven, Germany

               Tel: [phone]           (BBS/FAX)   24hr
                    [phone]           (BBS/ISDN)  24hr

               Netmail: 2:2426/2090@fidonet
                        2:2426/2091@fidonet


               InterNet:   [e-mail]
               WWW:        http://www.fh-wilhelmshaven.de/~afreriks















      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  84
      Section 16                                                CONCLUSION
      ────────────────────────────────────────────────────────────────────

      Canada Help and Registration:

               Vincent Danen
               #108 13806-24 Street
               Edmonton, AB, Canada   T5Y 1J7

               Tel: [phone]            (BBS)       24hr

               Netmail: 1:342/52@fidonet
                        411:230/102@ivnet
                        753:1000/102@tgpbnet
                        152:5403/0@impactnet
                        141:500/0@osnet
                        111:1403/0@stn

               InterNet:   [e-mail]
                           [e-mail]
      United States of America Help and Registration:

               Michael McCabe
               139 Swan Drive
               Forsyth, MO.  USA
               65653

               Tel: [phone]            (BBS/FAX)   24hr

               Netmail: 1:297/11@fidonet
                        1:1/148@fidonet
                        808:109/0@musicnet

               Internet:   [e-mail]
      Australia Help and Registration:

               Bob Milutinovic

               Tel: [phone]            (BBS)       24hr

               Netmail: 3:713/111@fidonet

               Internet:   [e-mail]
                           [e-mail]

               Voice: [phone] (9am - 10pm, 7 days)
      United Kingdom Help

               Peter Hargroves

               Tel: [phone]          (BBS)       24hr

               Netmail: 2:2502/9@fidonet


      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  85
      Section 16                                                CONCLUSION
      ────────────────────────────────────────────────────────────────────

      Austria Help and Registration

              Christian Wagner

              Tel: [phone]             (BBS)       24hr

              Netmail: 2:314/40@fidonet
      Portugal Help

              Pedro Cardoso

              Tel: [phone]             (BBS)       24hr
                   [phone]             (BBS/ISDN)  24hr

              Netmail: 2:362/5@fidonet
                       2:362/500@fidonet
      Italy Help and Registration

              Andrea Brancatelli

              Tel: [phone]             (BBS)       24hr

              Netmail: 2:335/354@fidonet
      Netherlands Help and Registration

              Nico van Vliet

              Tel: [phone]             (BBS)       24hr
                   [phone]             (BBS)       24hr
                   [phone]             (BBS/ISDN)  24hr

              Netmail: 2:286/710@fidonet
                       2:286/711@fidonet
                       2:286/712@fidonet
      Belgium Help and Registration

              Frederic Van De Velde
              Rue Au Bois, 146
              1150 Bruxelles
              Belgique

              Tel: [phone]              (BBS/FAX)   24hr
                   [phone],#11,#11,#11  (BBS/FAX)   24hr

              Netmail: 2:291/740@fidonet
                       111:7322/0@stnet


                              16.2: Getting Help



      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  86
      Section 16                                                CONCLUSION
      ────────────────────────────────────────────────────────────────────

      There is currently an echo on the international fido network called
      MCMAIL.  If you post your concerns here, you will get whatever help
      you might need.  In Zone 2 of fidonet, there is also a German echo
      called MCMAIL.GER for McMail support in the German language.  There
      is also the international FTN network, the Sysop's TechNet, that is
      a support network for McMail (zone 111).  You may also send netmail
      to one of the authors, registration sites, or help sites.

      For a registration form FREQ the magicname MCMREG from the
      registration site nearest you.


                             16.3: Special Thanks


      Special thanks, from myself, go out to my wife for not beating me
      while I was spending time writing this documentation and beta
      testing McMail.  I know it was frustrating for her at times
      (especially considering we got married right in the middle of my
      writing the docs), but she kept quiet and let me do my thing.  And
      extra special thanks to God for giving me the ability to do this (He
      knows how much work it is).  Also, thanks to Gordian and Albert for
      finally creating a mailer I could definitely say I have fallen in
      love with.  =)  And finally, a great thanks to the people in the
      fido MCMAIL echo.  When I needed help with this sucker, they gave it
      to me freely and at their own expense.  I totally appreciate it.
      Thanks guys.

      Special thanks, from the authors, go out to ...

      the Beta Team for testing McMail in the real, hard "MailerLife" ;-)

                          >> In alphabetical order <<

                                Andreas Hensel
                                Andreas Klein
                                Andreas Otto
                                Andreas Rehberg
                                  Boris Huertgen
                                  Chris Lueders
                              Christian Hase
                                  Edgar Becker
                                  Frank Baier
                                  Frank Koehler
                                Gerhard Klobuzinski
                                   Hans Steine
                                 Jochen Grashorn
                                Juergen Tibi
                                  Klaus Meyer
                                  Klaus Winkler
                                   Marc Braun

      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  87
      Section 16                                                CONCLUSION
      ────────────────────────────────────────────────────────────────────

                                 Markus Mohr
                                 Martin Moers
                                Michael Bauer
                                  Mirko Mucko
                                 Oliver Stephan
                                 Ronald Brusch
                              Siegfried Osterloh
                                 Stefan Kaspar
                                   Sven Dueker
                                   Sven Meinhardt
                                 Thomas Leubner
                                    Tim Karnau
                                    Uwe Boettjer
                                Vincent Danen
                               Wilfried Hausmann
                                    Wim Abels
                               Winfried Scharff


                            16.4: Acknowledgements


      All brand and product names are copyrighted material, trademarks or
      registered trademarks of their respective holders:

      McMSetup             Klaus Winkler
      X00                  Raymond L. Gwinn
      BNU                  Unique Computing Pty Ltd
      cFos                 Martin Winkler & Christopher Lueders
      cFosTalk             Michael Grube
      FastV7               Marius Ellen
      Binkley              Bit Bucket Software
      FrontDoor            Joaquim Homrighausen, Absolute Solutions
      InterMail            Further Development, Inc.
      RemoteAccess         Wantree Development & Andrew Milner
      FastEcho             Software Technik Burchardt
      AllFix               Harald Harms
      ITrack               Frank Prade
      IMove                Oliver Stephan
      XOR                  Mirko K. Mucko
      OS/2, PC-DOS,
        TopView            International Business Machines Corp.
      Windows, MS-DOS      Microsoft
      DESQView             QuarterDeck Office Systems
      USRobotics           U.S. Robotics, Inc.
      ZyXel                ZyXel






      ────────────────────────────────────────────────────────────────────
      McMail v1.0 FrontEnd Mailer System Documentation                  88