*I
Netmail⌠Messagebase╙Inbound┼Outbound╚Decompression Programs¥Logfile<StatisticslSwapping╧	Swapping (Path)%
Mailero Badmail-Board╙"Auto-Area-Create#$
Compression Programs_'Securityß)Node-ManagerC-Address╨/Your Akaα0Passwords┐1Packerÿ24D▄3Tosscanö6AreaFix Log²7ARCmail-Status9Export By NameE=Automatic PassiveΓ>UmlautAAddressesWBDomain¼CPoint-NetcDRetear±E Origin┤H!Carbon CopiesEJ"Area-ManagerjN#Board:S$Area Name=T%Export to∙T&Purge Defaults╘V'Purging°W(Kill empty netmails'Y)Routing$Z*Autorenumber Messages░^+ARCmail 0.60`,Dupe-Board╧a-Duperecords c.Messagebufferf/ARCmail-Password═g0AreaFix-Password'i1PassiveIj2Groups⌐k3Kill Dupesn4Temp. Outb.)o5Help-FileΓp6Security-Level	r7Groupàs8StorageÖt9Path z:Use Akaû{;Type╨|<Security (Echo){=Loggingé>Umlaut (Netmail)σâ?New Area Default GroupVà@Allow Area-Create╞åAFind Area╙çBAllow Rescan¿ëCKeep requestsTïDKeep receiptsjîEDetailed ListùìFGroup namesÅGForward AreaFix-Requests^ÉHArea Manager⌐öIArea ListûJList typevùKCPD▀ÜLTiny SEEN-BY╪£MShare QBBS-Base╬₧NForce Mailer rescanäáOSemaphoresIóPDisable RescanòúQMaximum .PKT size(ÑRPassive (Area)τªSArea List (Node)M¬TUser namesπ½UName7¡VExclude users°¡WExclude SysOpsC»XKeep SEEN-BY¬░YCheck .PKT destinationf▓ZComment╔│[Update BBS Config╡\New area defaults (BBS)o╢]BBS Software╩╖^Secure Inb.I╣_DB Queue╗`Use EMS for buffering¢╜aKill grunged date7┐bMandatoryW└cKeep users¼┴dSeen-by├eAllow Remote Maintenanceå─fList Prefix*╞gAllow %PWDh╔hAllow %PKTPWDÅ╩iUnconditional╗╦jGroup Area Defaults╣═kBoard (default)°╤lExport to (default)F╘mDefault for rescan⌐╓nDefault for %DAYS⌐╪oDefault for %MSGS÷┘pMaximum for %DAYSC█qMaximum for %MSGSL▄rKill readM▌sKeep netmails▌▐tSecure TOSS mode+αuDisable PassiveüΓvMaximum open .QQQs¼πwSend NotifyBτxSorting¿ΦyTag╥ΩzAdd '+',∞{After Unpack─φ|Before PackH≡}Send Help┴≥~AreaFix-Status)⌠Status┴⌡ÇAdd '---'¿÷üAllow %COMPRESS+°éBe 'quiet'I∙âTemp. Inb.ç·äUpdate mailer config;ⁿàToss BuffersW²åUse arrival dateµ■çScan before tossing3êMax. Receipt size╚ëArchive extensions|èMailer's semaphoresVïCheck complete files∩(#Pathsn
'NoHelpΣ'NoHelp    

  FastEcho Setup-Utility (c)1991-1993 by Tobias Burchhardt

*B 1,Netmail
  Netmail
  ────────────────────────────────────────────────────────

  This field has to contain the path in  which  your  net-
  mails (*.MSG) are stored.

  See also:  ^Messagebase^  ^Paths^
*E
*B 2,Messagebase
  Messagebase
  ────────────────────────────────────────────────────────

  This  field  has to point to the directory in which your
  RA/QBBS-Messagebase-files (MSG*.BBS) are stored.

  See also:  ^Netmail^  ^Paths^
*E
*B 3,Inbound
  Inbound
  ────────────────────────────────────────────────────────

  This field has to contain the  path  in  which  incoming
  mail bundles are stored by your mailer.

  See also:  ^Secure Inb.^  ^Temp Inb.^  ^Outbound^  ^Paths^
*E
*B 4,Outbound
  Outbound
  ────────────────────────────────────────────────────────

  This  is  the path in which FastEcho is to store the ge-
  nerated outgoing mail-bundles.

  In Binkley-environments this path will be used for  your
  primary  address/domain.  If  creating file-attaches for
  other zones/domains, it takes  the  information  out  of
*P

  your  Network addresses.  For example if you have an AKA
  like   9:492/6050@virnet  and   you  set  this  path  to
  C:\BT\OUTB, FastEcho will replace OUTB with VIRNET.009.

  When FastEcho is working together with Binkley  it  thus
  has full multi-zone capability.

  See also:  ^Inbound^  ^Temp. Outb.^  ^Mailer^  ^Paths^
*E
*B 5,Decompression Programs
  Decompression Programs
  ────────────────────────────────────────────────────────

  Here you have to specify the  programs  to  be  used  to
  unpack  the  incoming  ARCmail  according to the packing
  method used.

  You  can  type the full command-line. The full path to a
  program is only needed in case it cannot  be  found  via
*P

  your 'PATH' environment variable.

  For 'Unknown' you should use a kind of unpack-shell that
  copes   with  different  unpackers  and  can  be  easily
  extended.  For  example,  programs  like  'PolyXarc'  or
  'General-Unpack-Shell' (GUS) work well!

  See also:  ^Compression Programs^
*E
*B 6,Logfile
  Logfile
  ────────────────────────────────────────────────────────

  This  should contain the full path to your logfile.  The
  format of this logfile is determined by your ^Mailer^.

  If you don't specify a logfile, ^Logging^ will  be  turned
  off. [Not recommended !]
*E
*B 7,Statistics
  Statistics
  ────────────────────────────────────────────────────────

  This is the file to which the  echomail-statistics  will
  be appended each time you call FastEcho STAT.

  The echomail-statistics gives you a brief overview about
  the  number  of  echomails  that  have  run through your
  system (import & export).
*E
*B 8,Swapping
  Swapping
  ────────────────────────────────────────────────────────

  You  can choose different ways to swap when FastEcho and
  FESetup shell to  DOS  (for  example  when  calling  the
  unpacker).  With swapping enabled, only about 1400 bytes
  will remain in memory to allow the  called  programs  to
  run even if your computer is short on memory.
*P

  With swapping enabled, you  also  have  to  specify  the
  path  to swap to, because if no EMS/XMS-memory is avail-
  able or free, the programs will swap to disk.

  See also:  ^Swapping (Path)^
*E
*B 9,Swapping (Path)
  Swapping (Path)
  ────────────────────────────────────────────────────────

  This is the directory in which FastEcho and FESetup will
  place their overlay-files when swapping, if 'Swapping to
  Disk' is specified, or if your computer is short on EMS/
  XMS-memory.

  See also:  ^Swapping^  ^Paths^
*E
*B 10,Mailer
  Mailer
  ────────────────────────────────────────────────────────

  Here  you  select  the  mailer you are currently working
  with.   You  can  run   FastEcho   with   FrontDoor(tm),
  InterMail(tm), D'Bridge(tm) and Binkley(tm).

  This   selection  is  used  to  determine  the  kind  of
  configuration-files,  FastEcho  has  to  cope  with  and
*P

  especially for Binkley-users the different way to create
  file-attaches (.?LO-files).

  Further, the logfile-format will fit the typical logfile
  of your mailer.

  See also:  ^Auto-Area-Create^  ^Outbound^
*E
*B 11,Badmail-Board
  Badmail-Board
  ────────────────────────────────────────────────────────

  During  tossing  all mails that are not allright will be
  stored  here.  For  example,  mails  in  unknown   areas
  (without ^Auto-Area-Create^  being enabled)  or mails from
  nodes who fail the ^Security (Echo)^-check.
*E
*B 12,Auto-Area-Create
  Auto-Area-Create
  ────────────────────────────────────────────────────────

  If enabled, FastEcho will try to automatically  add  new
  (unknown)  areas while tossing to the internal FastEcho-
  Area-Setup.  A file named "NEWAREAS.FE" will be left  in
  the FastEcho directory as a semaphore-file.

  If you enable ^Update mailer config^ FastEcho will add the
*P

  new areas to your mailer editor's folder configuration.

  If  you are  using  one of  the  supported  ^BBS Software^
  packages, you can let FastEcho add the new areas to your
  setup by enabling ^Update BBS Config^.

  Areas  will be created depending on the settings for the
  ^New Area Default Group^.
*P

  Note: the system sending the new area must be qualified
        with ^Allow Area-Create^ !
*E
*B 13,Compression Programs
  Compression Programs
  ────────────────────────────────────────────────────────

  You   may   specify  up  to  8   different   compression
  utilities used for packing outgoing mail-bundles.

  Each  tag  has  to  be unique and should be set as usual
  (LZH for LHArc, ZIP for PKzip(tm) etc.) - it  will  only
  be used in the ^Node-Manager^.
*P

  You may type the full command-line including all kind of
  switches  etc.  The full path to the program has only to
  be  given if it cannot be found by means of your  'PATH'
  environment variable.

  See also:  ^List Prefix^  ^Decompression Programs^
*E
*B 14,Security
  Security
  ────────────────────────────────────────────────────────

  »None«

  All incoming packets will be tossed without  any  check.
  This  allows  even systems to send you mail that are not
  defined  in the  ^Node-Manager^.  The ^Security (Echo)^ set-
  tings are ignored as well.
*P

  »Normal«

  Only mail from systems  defined  in  the  ^Node-Manager^
  will be tossed. If FastEcho tracks a mail-packet from an
  'unlisted' system, this packet will not be processed and
  the file will be renamed to '.BAD'.

*P

  »Full«

  With  'full'  security  enabled,  mail  from  'unlisted'
  systems will not be processed. In addition to  that,  it
  will only be processed if the password-test succeeds. If
  no ^ARCmail-Password^ is specified  for the specific node,
  FastEcho will behave like »Normal«.

*E
*B 15,Node-Manager
  Node-Manager
  ────────────────────────────────────────────────────────

  The  Node-Manager  allows you to specify up to 200 diff-
  erent nodes you are im-/exporting mail to.

  See also:  ^Address^  ^Your Aka^  ^Passwords^  ^Packer^
             ^Tosscan^  ^Routing^   ^Passive^    ^4D^
             ^Groups^   ^Umlaut^    ^Name^       ^Status^
*P

  See also:  ^ARCmail 0.60^    ^Security-Level^
             ^Disable Rescan^  ^Allow Area-Create^
             ^Export By Name^  ^New Area Default Group^
             ^Send Notify^     ^Automatic Passive^
             ^Send Help^       ^Allow Remote Maintenance^
*E
*B 16,Address
  Address
  ────────────────────────────────────────────────────────

  This is the matrix-address of the system.

  It  has  to be defined in full 4-dimensional addressing-
  mode: Zone:Net/Node.Point

  See also:  ^Your Aka^  ^Node-Manager^
*E
*B 17,Your Aka
  Your Aka
  ────────────────────────────────────────────────────────

  This is your matrix-address used for this node.

  You can choose one of your akas.

  See also:  ^Node^  ^Node-Manager^
*E
*B 19,Passwords
  Passwords
  ────────────────────────────────────────────────────────

  There  are 2 different  passwords. The  ^ARCmail-Password^
  and the ^AreaFix-Password^.

  See also:  ^Node-Manager^
*E
*B 20,Packer
  Packer
  ────────────────────────────────────────────────────────

  Here  you  can  choose the compression utility used when
  generating mail-bundles for this node.
  If you select 'PKT', FastEcho will send the .PKT without
  compressing them.

  See also:  ^Compression Programs^  ^Node-Manager^
*E
*B 21,4D
  4D/Type 2+
  ────────────────────────────────────────────────────────

  This  flag  has  to  be set to 'Yes' if you or the other
  system is running a 4D-point.
  It  forces  FastEcho  to  generate mail-packets that are
  compatible with FSC-0039.  If set to 'No' pure FTS-0001-
  packets  will  be  generated  using  your  ^Point-Net^  if
  necessary.
*P

  It's  suggested that you enter your points with their 4D
  address instead of using  their  fakenet-address.  Mails
  from/to  them will be remapped automatically while being
  processed by FastEcho. To do so,  the ^Point-Net^ for your
  aka is mandatory !

  See also:  ^Tosscan^  ^Node-Manager^
*E
*B 22,Tosscan
  Tosscan
  ────────────────────────────────────────────────────────

  Set this flag, if this node uses Tosscan 1.0 and you are
  running ^4D^ - due to the  fact that TS 1.0  only knows of
  D'Bridge(tm)  to  be 4D-capable. This forces FastEcho to
  use the D'Bridge-Product-Code instead  of  its  own,  to
  avoid any problems.
*E
*B 23,AreaFix Log
  AreaFix Log
  ────────────────────────────────────────────────────────

  This should contain the full path to your  AreaFix  log-
  file to log all AreaFix operations performed by AFIX.

  You can't use the same file you specified for ^Logfile^ !
*E
*B 24,ARCmail-Status
  ARCmail-Status
  ────────────────────────────────────────────────────────

  You  can  set  the status of ARCmail-attaches created by
  FastEcho.
  There are 3 values »None«, »Crash« and »Hold« which  can
  be combined with the »Direct«  flag.  »No  attach«  will
  instruct  FastEcho  not to create a file-attach for this
  system.
*P

  »Direct«

  This  flag  forces  to  set  the  DIRECT-flag  in  file-
  attaches generated by FastEcho on FrontDoor and D'Bridge
  systems.

  On  BinkleyTerm  systems  it  will  create  a 'DLO'-file
  instead of a 'FLO'-file.
*P

  »Crash«

  This  flag forces to set the CRASH-flag in file-attaches
  generated by FastEcho on FrontDoor and D'Bridge systems.

  On BinkleyTerm  systems  it  will  create  a  'CLO'-file
  instead of a 'FLO'-file.
*P

  »Hold«

  This  flag forces to set the HOLD-flag in  file-attaches
  generated by FastEcho on FrontDoor and D'Bridge systems.

  On  BinkleyTerm  systems  it  will  create  a 'HLO'-file
  instead of a 'FLO'-file.
*E
*B 25,Export By Name
  Export By Name
  ────────────────────────────────────────────────────────

  With  this  switch  turned on, FastEcho TOSS & SCAN will
  export  mails containing  the ^Name^ of this Sysop in  the
  TO: field to this system, even  if  the  system  is  not
  active in the specific area or is ^Passive^ or even is not
  allowed to receive the mail due to the ^Security-Level^.
*E
*B 26,Automatic Passive
  Automatic Passive                         * Nodes only *
  ────────────────────────────────────────────────────────

  If a system isn't polling its mail for  longer  than  XX
  days,  it will be  automatically  set  ^Passive^  and  the
  normal mail flow will be stopped for this system.

  A  notification  mail  will be written with instructions
  for this system in order to become 'Active' again.
*P

  Note:  This function is only active, if your mailer uses
         *.MSG style ARCmail-Fileattaches !
*E
*B 27,Umlaut
  Umlaut
  ────────────────────────────────────────────────────────

  This  feature may only be interesting for people writing
  in German.  As in many echomail areas  German  'Umlauts'
  (ÄäÖöÜüß)  are  still 'forbidden', it's possible to con-
  vert them while exporting messages.

  See also:  ^Area-Manager^
*E
*B 28,Addresses
  Addresses
  ────────────────────────────────────────────────────────

  This   is  a  full  4-dimensional  [Zone:Net/Node.Point]
  address.

  Place  your different addresses here. If you are a point
  there is no need to  specify  your  Fakenet-address,  as
  this address will be built out of the ^Point-Net^.
*E
*B 29,Domain
  Domain
  ────────────────────────────────────────────────────────

  Here you may place the domain of this Aka.

  Example: 'fidonet.org' or 'virnet.ftn'
*E
*B 30,Point-Net
  Point-Net
  ────────────────────────────────────────────────────────

  This is the Point-Net  that  will  be  used  when  gene-
  rating FTS-0001-compliant mail-bundles to/from points.

  It will be used if ^4D^ is set to 'No' for a system in the
  ^Node-Manager^. Also, on node-systems, it will be used for
  internal remapping of your points (AreaFix for example).
*E
*B  31,Retear
  Retear, Tearline
  ────────────────────────────────────────────────────────

  You  may  specify  a  tearline  that  will  replace  the
  existing tearline when  exporting  echomail-messages  if
  'Retear' is set to 'Yes'.
  Remember that - if  specified  -  a  tearline  MUST  NOT
  contain   meaningless  information  or  just  'rubbish'.
  Further,  the  tearline  MUST  NOT  contain   the   same
*P

  information  the  ^^APID-kludge  of  your editor  already
  contains  or  the  ^^ATID-kludge  FastEcho  adds to  each
  message.

  The length of a tearline is  limited  to  35  characters
  including preceeding '--- ' which is automatically added
  by FastEcho.
*E
*B 32,Origin
  Origin
  ────────────────────────────────────────────────────────

  You may specify up to 8 different origin-lines.  One  of
  them  will  be  inserted  in  exported echomails if they
  don't contain one.
  Remember  that an origin-line containing all information
  [" * Origin: ", your line  and  "(Zone:Net/Node.Point)"]
  MUST NOT be longer than 79 characters.
*E
*B 33,Carbon Copies
  Carbon Copies
  ────────────────────────────────────────────────────────

  When you call FastEcho TOSS with the -C switch, FastEcho
  will  generate 'Carbon  Copies'  of  certain  echomails.
  The criterions for these messages can be specified here.

  Each echomail can be searched  in  the  fields  'From:',
  'To:'  and  'Subject:' for strings. If one contains  one
*P

  of  these  strings  it  will  not  only be stored to its
  normal board, but also to the board specified here.

  The  comparison  of  strings  will  be case insensitive.
  Please note that it's not checked if  the  field  starts
  with this string, but it's checked if the field contains
  this  string.  So  if you, for example, want to test the
  'To:' field  for  'martin',  all  mails  containing  any
*P

  'martin'  will  be  copied - mails to 'Martin Miller' as
  well as  mails  to  'John  Martinelli'.   So  don't  let
  FastEcho  test for short strings as it would cause it to
  copy many mails more, than you wanted to.

*E
*B 34,Area-Manager
  Area-Manager
  ────────────────────────────────────────────────────────

  The  Area-Manager  helps  you to cope with the masses of
  echomail-areas.
  There  are 2 modes: the 'view'-mode and the 'edit'-mode.
  The 'view'-mode is selected by default, the  'edit'-mode
  may  be  invoked  simply by pressing 'Enter' or 'Ins' to
  edit one echomail-area.
*P

  In 'view'-mode you may browse the area-list by using the
  cursor-keys, PGUP and PGDN as well as HOME and END.  You
  can change the ^Sorting^ of the area list with F2. Depend-
  ing on that, you can use  the  normal  keys  to  quickly
  switch  to  other  areas.  You  can Tag/Untag areas with
  SPACE and  the ^Tag^ function F3.  Further, you can search
  for specific areas with F4 and SHIFT-F4 (find-next)  and
  perform global changes with F5.
*P

  In 'edit'-mode you can edit the following fields:

       ^Area Name^     ^Origin^     ^Group^     ^Storage^
       ^Board^         ^Path^       ^Your Aka^  ^Umlaut^
       ^Type^          ^Purging^    ^Security (Echo)^
       ^Tiny Seen-By^  ^CPD^        ^Passive (Area)^
       ^Keep Seen-By^  ^Mandatory^  ^Keep users^
       ^Export to^     ^Seen-By^    ^Kill read^
*E
*B 35,Board
  Board
  ────────────────────────────────────────────────────────

  This is the QBBS-board the messages in this area will be
  stored  to.  Each  board  can  only be defined once. The
  range of the board number is from 1 to 200.
*E
*B 36,Area Name
  Area Name
  ────────────────────────────────────────────────────────

  This is the name of the area. It  is  specified  in  the
  global or regional echolist.
*E
*B 37,Export to
  Export to
  ────────────────────────────────────────────────────────

  Here you may specify to which nodes mail written  by you
  in this area will be exported to.

  Further, if you are a node,  here you  can  specify your
  downlinks,   for  whom  mails  will  be  exported  while
  tossing.
*P

  You may add/delete one node by tagging it with  'Space',
  select  all  nodes  with 'ALT-A' or clear all selections
  with 'ALT-C'.
*E
*B 38,Purge Defaults
  Purge Defaults
  ────────────────────────────────────────────────────────

  These  are  the defaults that will be used for the areas
  that  have set the number 0 for one of the criterions in
  ^Purging^.

  0 for one of the defaults means not to care about it.
*E
*B 39,Purging
  Purging
  ────────────────────────────────────────────────────────

  These  are  the  values  that will be used for this area
  when calling FEUtil PURGE.

   0 means to use the defaults set with ^Purge Defaults^.

  -1 means not to care about this criterion.
*E
*B 40,Kill empty netmails
  Kill empty netmails
  ────────────────────────────────────────────────────────

  Enabling this option, FastEcho will delete all  imported
  netmails  that  don't  contain any text. These mails are
  normally File-Attaches.

*E
*B 41,Routing
  Routing
  ────────────────────────────────────────────────────────

  This is a rather complex but powerful topic.

  You   can   define   up  to  15  different  'statements'
  specifying the systems whose netmails should  be  routed
  via the selected node.
*P

  Valid 'statements' have the format:  Zone:Net/Node.Point

  Each  statement  can  be  shortened by 'ALL' or '*'. For
  example '2:*' will cause FastEcho to route all  netmails
  to  zone-2-systems  and '2:245/31.*' will cause to route
  all netmails to the points  of  2:245/31  including  the
  node itself (because it's .0).
*P

  There are different levels:

  *                     Level 0
  Zone:*                Level 1
  Zone:Net/*            Level 2
  Zone:Net/Node.*       Level 3
  Zone:Net/Node.Point   Level 4      [Point = 0 for nodes]
*P

  The  routing  with the highest level will be used - that
  means: If you  have  specified  '2:*'  for  node  A  and
  '2:245/*'  for  node  B, a netmail to 2:245/31.5 will be
  routed via node B because it has level 2 and node A only
  level 1.

  See also:  ^Node-Manager^
*E
*B 42,Autorenumber Messages
  Autorenumber Messages
  ────────────────────────────────────────────────────────

  Here  you specify the level, at which renumbering should
  be  forced  when  calling  "FEUtil  PACK"  without   the
  '-Renumber' - switch.
  If  the  highest  messagenumber  in  the  messagebase is
  greater than this level, renumbering is forced.
*E
*B 43,ARCmail 0.60
  ARCmail 0.60
  ────────────────────────────────────────────────────────

  Some   'stone-age'  tossers  require  a  special  naming
  convention for mail-packets for  their  security  check.
  This  is  called  the  ARCmail  0.60  standard.  To make
  FastEcho create such packets, turn on this  switch.  But
  only  use it if you are really in need of this feature!
  Ask your uplink if you do so.
*E
*B 44,Dupe-Board
  Dupe-Board
  ────────────────────────────────────────────────────────

  This is the board, where the incoming echomails that are
  dupes (with dupe-checking turned on, see ^Duperecords^ and
  ^Kill Dupes^ for  details). If you  don't specify any area
  as Dupe-Board, incoming dupe-mails will be killed.
*E
*B 45,Duperecords
  Duperecords
  ────────────────────────────────────────────────────────

  This  is the number of records, that should be stored in
  your dupe-database.  Each record represents one  message
  that  was  processed  -  so  the records of the XXX last
  processed mails will be stored. A number of 0 would mean
  that no records should be stored - dupe-checking will be
  disabled (see also ^Kill Dupes^ and ^Dupe-Board^).
*P

  Note:  The larger the number of Duperecords is, the more
         memory is needed for storing them. Therefore  EMS
         memory is used for keeping the database in memory
         while  tossing  and scanning. Up to 512kB of free
         EMS is therefore needed to store 131000 records !
*E
*B 46,Messagebuffer
  Messagebuffer
  ────────────────────────────────────────────────────────

  This is the length of the buffer,  used  for  processing
  incoming  and  outgoing  mails. It specifies the maximum
  length of a message to be processed.
  It's recommended to use a buffer as  large  as  possible
  (doesn't  affect  the  performance), and only to make it
  smaller if your computer is short on memory.
*E
*B 47,ARCmail-Password
  ARCmail-Password
  ────────────────────────────────────────────────────────

  This password will be inserted in mail-packets generated
  by FastEcho.
  Further, if ^Security^ set to »Norm« or »Full«, it  will
  be used to check incoming packets against it.

  See also:  ^AreaFix-Password^  ^Node-Manager^
*E
*B 48,AreaFix-Password
  AreaFix-Password                          * Nodes only *
  ────────────────────────────────────────────────────────

  This password will be  used  for  AreaFix-requests  from
  the specified node to your system.

  See also:  ^ARCmail-Password^  ^Node-Manager^
*E
*B 49,Passive
  Passive                                   * Nodes only *
  ────────────────────────────────────────────────────────

  A  node  that  is  set  to  'Passive' [manually via this
  switch or via an AreaFix-request from that node  or  via
  ^Automatic Passive^]  will not receive  any mails in areas
  he is currently linked to.
*E
*B 50,Groups
  Groups
  ────────────────────────────────────────────────────────

  These are the groups (specified by characters  from  'A'
  to  'Z') this node is allowed to  request  via  AreaFix.
  However,  you can turn on areas manually in other groups
  active  for  this  node.   Also,  groups  are  used  for
  internal maintenance.
*P

  If  you  have named your groups, you will be prompted to
  tag the groups by name.

  You may  either  tag  each  group  with  'Space'  or  by
  pressing  the  equivalent key. You can select all groups
  with 'ALT-A' or clear all selections with 'ALT-C'.
*E
*B 51,Kill Dupes
  Kill Dupes
  ────────────────────────────────────────────────────────

  Enabling this option, FastEcho will delete all  imported
  echomails  that  reach  your  system more than once, in-
  stead of putting them into your ^Dupe-Board^.
*E
*B 52,Temp. Outb.
  Temporary Outbound                        * Nodes only *
  ────────────────────────────────────────────────────────

  This  is  the  path, which is used for storing generated
  outgoing PKTs temporarily  while  tossing/scanning/pack-
  ing. If set, it should ONLY be set  to  a  RAM-DISK  for
  speed-benefits - NOT to a harddisk (more overhead) !

  * This is neither needed, nor useful for point-systems *
*E
*B 53,Help-File
  Help-File                                 * Nodes only *
  ────────────────────────────────────────────────────────

  Here  you specify the name of the file that will be sent
  if a user is requesting help via AreaFix !

  Example: C:\FD\FASTECHO\AREAFIX.HLP
*E
*B 54,Security-Level
  Security-Level                            * Nodes only *
  ────────────────────────────────────────────────────────

  This  level  is used for  Area-Management and is closely
  related to ^Groups^. A user can only request areas  with a
  Read-Security equal to or less than this number (must be
  between 0 and 65535).

  See also:  ^Security (Echo)^
*E
*B 55,Group
  Group
  ────────────────────────────────────────────────────────

  This  field  can be between 'A' and 'Z'.  It is used for
  area-management for downlinks.  Also, it can be used for
  'global' changes to a group of areas.

  See also:  ^Groups^
*E
*B 56,Storage
  Storage                                   * Nodes only *
  ────────────────────────────────────────────────────────

  Here you can define where to store the messages.

  The »QBBS« messagebase  is  used  by  many  popular  BBS
  systems  like QuickBBS, SuperBBS, Remote Access etc.  It
  can hold up to 200 echomail-areas and stores all data in
  5 files. This is the fastest type of messagebase.
*P

  »Fido *.MSG« is an old standard way  to  store  messages
  (used  typically  for netmails).  Each message is stored
  into one file (1.MSG, 2.MSG etc.) and thus  it  needs  a
  lot of diskspace and processing is very slow compared to
  the other types.
*P

  Messages in a »Squish« messagebase are stored in 2 files
  each  area  and  are faster than Fido *.MSG, slower than
  QBBS but more secure.  Squish style areas are  currently
  used by Maximus CBCS (whose author is  the  inventor  of
  'Squish') and ProBoard 1.31.
*P

  »JAM« is a new messagebase format introduced  by  Remote
  Access(tm)  2.00. It's similar to Squish (data is stored
  in 4 files) in features and performance.  However,  it's
  easier  to  handle  and will probably be more widespread
  sooner or later.
*P

  »Passthrough«  means,  that  the messages are not stored
  locally.  Messages in this areas are only processed  and
  forwarded to other systems.

  See also:  ^Path^
*E
*B 57,Path
  Path
  ────────────────────────────────────────────────────────

  This is only used either with *.MSG style or with Squish
  or JAM style areas  (see ^Storage^ for details).  In *.MSG
  mode  it specifies the full path to the stored messages.
  In Squish and JAM mode it contains the  full  path-  and
  filename of the area without extension.
*E
*B 58,Use Aka
  Use Aka
  ────────────────────────────────────────────────────────

  This is the your aka that is used in conjunction to this
  area. For example, it is  used for the ^Origin^, that will
  be inserted when exporting echomails.

  * Point-Akas cannot export mails to multiple downlinks *
*E
*B 59,Type
  Type
  ────────────────────────────────────────────────────────

  »Echomail«

  Mails in this board can be exported and imported without
  any restriction.
*P

  »Netmail«

  Mails  in  this board will be exported as netmail, which
  means they  will be exported to  your ^Netmail^ to be pro-
  cessed like normal netmails.
*P

  »Local«

  Mails in this board  can  be imported, but  won't be ex-
  ported to up/downlinks.
*P

  »Badmail« and »Dupe-Board«

  You  MUST  define one area as ^Badmail-Board^ in order  to
  run  FastEcho properly.
  You  CAN   define one area as ^Dupe-Board^ for mails
  received in duplicate.
*E
*B 60,Security (Echo)
  Security (Echo)                           * Nodes only *
  ────────────────────────────────────────────────────────

  This  is  the  security  used  for  area-management with
  downlinks. A system can only request an area with 'Read'
  being less or equal to its own security level.  Further,
  (with  ^Security^  set  at least  to »Norm«), if  a system
  sends mails in an area  with  a  'Write'-security  being
  higher than its own level, these mails will be tossed to
*P

  your ^Badmail-Board^. This  is  an easy way to set an area
  to 'Read-only' for your downlinks (points).

  Beware: If an area is an echomail-area, don't forget  to
  set   the ^Security-Level^ of your uplink higher than or
  equal to the 'Write'-level !
*E
*B 61,Logging
  Logging
  ────────────────────────────────────────────────────────

  This  is  the level at which the log information will be
  written to the ^Logfile^ and ^AreaFix Log^.

  With »Norm« only essential information will  be  logged.
  This  will keep your ^Logfile^ short, but will also hide
  interesting information.
*E
*B 62,Umlaut (Netmail)
  Umlaut (Netmail)
  ────────────────────────────────────────────────────────

  This feature may only be interesting for people  writing
  in  German.   As  some mailreaders are unable to process
  German 'Umlauts' (ÄäÖöÜüß), you may want to turn this on
  to convert them while packing netmails

  See also:  ^Node-Manager^
*E
*B 63,New Area Default Group
  New Area Default Group
  ────────────────────────────────────────────────────────

  When  FastEcho  automatically creates a new area (either
  with ^Auto-Area-Create^ or with ^Forward AreaFix-Requests^),
  the  new  area will be preset with  the  default  values
  specified for this group.

  See also:  ^Group Area Defaults^
*E
*B 64,Allow Area-Create
  Allow Area-Create
  ────────────────────────────────────────────────────────

  Means: "System is allowed to send new areas".

  If  set to 'Yes'  and ^Auto-Area-Create^ enabled,  unknown
  areas received from this system will be created.
*E
*B 65,Find Area
  Find Area
  ────────────────────────────────────────────────────────

  You may type the full name of this are or abbreviate  it
  by using the '*' and/or '?' wildcards (*IX style).

  For example 'FAST*' will find the first area that begins
  with  these characters. If you then press Shift-F4 it'll
  search for the next area listed after the found area.
*P

  Examples:             ?.GER.*.MAIL.*
                        *.024
*E
*B 66,Allow Rescan
  Allow Rescan                              * Nodes only *
  ────────────────────────────────────────────────────────

  If set to 'Yes', systems are  allowed  to  rescan  areas
  from  your  messagebase by using the %RESCAN-metacommand
  of  FastEcho's  AreaFix. You may exclude a downlink from
  this by selecting ^Disable Rescan^.

  NOTE: A rescan CAN'T be performed on Passthrough-areas !
*E
*B 67,Keep requests
  Keep requests                             * Nodes only *
  ────────────────────────────────────────────────────────

  If set to 'Yes', AreaFix-request-mails will be marked as
  'Rcvd'  after  being  processed.  By  default  they  are
  killed.
*E
*B 68,Keep receipts
  Keep receipts                             * Nodes only *
  ────────────────────────────────────────────────────────

  If set to 'No', AreaFix-receipt-mails generated by  your
  system  will  be  marked as 'Kill/Sent' - otherwise they
  will be kept after being sent.
*E
*B 69,Detailed List
  Detailed List                             * Nodes only *
  ────────────────────────────────────────────────────────

  This  will enable a detailed list being sent to a system
  requesting '%LIST' (by showing your 'Comments').

  If you've named your groups, the list will be sorted  by
  group instead of being sorted by name.
*E
*B 70,Group names
  Group names
  ────────────────────────────────────────────────────────

  You may name your groups. This makes it easier to select
  the right ^Groups^ in the ^Node-Manager^ and the right ^Group^
  in the ^Area-Manager^.

  Also, this  enables a ^Detailed List^ for  your downlinks'
  AreaFix-requests.
*E
*B 71,Forward AreaFix-Requests
  Forward AreaFix-Requests                  * Nodes only *
  ────────────────────────────────────────────────────────

  In  the  registered  version  FastEcho's AreaFix has the
  ability to forward requests. If one of your uplinks does
  have  the  requested area, but you are not linked to it,
  FastEcho will automatically create this area  as  'Pass-
  through'  on  your system and will request the link from
  your uplink.
*P

  All you need is a file from your uplink in which all his
  areas are listed.

  The  downlink,  who requests the area, must be qualified
  by the groups and by the security level you specify  for
  the  uplink.  One  uplink  may  be defined multiple with
  different lists.
*P

  Also,  FastEcho  will  set an Passthrough-Area 'Passive'
  and unlink this echo from the uplink, if the last  down-
  link  sends a unlink-request.  As soon as a new downlink
  requests this area, it will be switched to 'Active'  and
  will be requested from your uplink again.

  See also:  ^Area List^  ^Area Manager^  ^List type^
*E
*B 72,Area Manager
  Area Manager                              * Nodes only *
  ────────────────────────────────────────────────────────

  This is the name of the Area-manager your  uplink  uses.
  It  will  be  used  to  address  the request your system
  will generate.

  Normally every Area-manager should at least be  able  to
  be addressed as 'AreaFix'.
*E
*B 73,Area List
  Area List                                 * Nodes only *
  ────────────────────────────────────────────────────────

  This  is  the  file in which the available areas of your
  uplink are listed.
  Currently  two  different  formats  for  this  file  are
  supported.

  See also:  ^List type^  ^Unconditional^
*E
*B 74,List type
  Area List                                 * Nodes only *
  ────────────────────────────────────────────────────────

  AREAS.BBS

  FastEcho expects a file of the following format:

                "<something> <Area Name> <...>"
*P

  The string <something> is  ignored but necessary to scan
  the  file,  so  it  must be present. The string <...> is
  ignored as well and does not need to be present.

  It doesn't matter if your uplink has an QBBS-compatible,
  and/or a Squish/*.MSG-style mail processor.
*P

  Arealisting

  This  may be an list of areas  generated  by  the  email
  processor or an external utitilty from your uplink.

  FastEcho expects a file of the following format:

                "<Area Name> <Description>"
*P

  If given, the description will be automatically inserted
  into FastEcho's setup.
*E
*B 75,CPD
  CPD (Circular Path Detection)             * Nodes only *
  ────────────────────────────────────────────────────────

  This  is  a method of preventing duplicate messages from
  being processed and exported by your system. Each system
  that forwards an echomail message adds  its  address  to
  the  ^^APATH  information  in  the  message.  If  CPD  is
  enabled, FastEcho will consider  messages  that  already
  have your address in them as duplicates while tossing.
*E
*B 76,Tiny SEEN-BY
  Tiny SEEN-BY                              * Nodes only *
  ────────────────────────────────────────────────────────

  If  set  to 'Yes', FastEcho will remove all systems that
  are not listed in your export-to list from  the  SEEN-BY
  information  when forwarding a message to other systems.
  This is useful if you are a gateway for  echomail  areas
  between  networks,  but  can  also  be  used between HUB
  systems to decrease the size of echomail packets.
*E
*B 77,Share QBBS-Base
  Share QBBS-Base
  ────────────────────────────────────────────────────────

  This  option  allows FastEcho to be run in a multiline-/
  multitasking-environment with shared access of different
  programs to your  messagebase.  The locking procedure is
  fully   RemoteAccess(tm)  1.11/2.00  compatible  !  Read
  FASTECHO.DOC for  information  about  the  the  QBBSLOCK
  environment variable !
*E
*B 78,Force Mailer rescan
  Force Mailer rescan
  ────────────────────────────────────────────────────────

  Enabling this option will  make  FastEcho  create  sema-
  phorefiles,  which  instruct  your  mailer to rescan the
  netmail-directory immediately.  Currently, in FrontDoor-
  environments,  FDRESCAN.NOW  and  FMRESCAN.NOW  will  be
  created,  and in D'Bridge-environments DBRIDGE.RSN. They
  will be created in your ^Semaphores^-Path.
*E
*B 79,Semaphores
  Semaphores
  ────────────────────────────────────────────────────────

  This  is  the  path, were the semaphore-files created by
  FastEcho will be placed. This is usually the  systempath
  of  your ^Mailer^,  and only useful when  running multiple
  tasks.

  See also:  ^Mailer's semaphores^
*E
*B 80,Disable Rescan
  Disable Rescan                            * Nodes only *
  ────────────────────────────────────────────────────────

  You  may  disable the %RESCAN feature of the AreaFix for
  one  (or  more)  node(s)  while  keeping  this   feature
  available for the others.

  Of course, the global ^Allow Rescan^ must be enabled  to
  make this 'local' restriction active.
*E
*B 81,Maximum .PKT size
  Maximum .PKT size
  ────────────────────────────────────────────────────────

  This will limit the maximum size of each outbound packet
  (.PKT) created by FastEcho.  The limit  may  be  set  to
  values ranging from 32kB thru 2MB.
  However,  this limitation needn't be very strict, as you
  can't force packets (the included messages) to  have  an
  exact size. Thus, the actual size of the .PKTs may vary.
*E
*B 82,Passive (Area)
  Passive (Area)                            * Nodes only *
  ────────────────────────────────────────────────────────

  This  flag  is only available to 'Passthrough'-areas and
  closely related to the ^Forward AreaFix-Requests^-feature.

  An  area is passive, if only the uplink is listed in the
  ^Export to^ list  so the  mails  will  be  tossed  without
  storing or forwarding them.
*P

  FastEcho  detects this during processing of the AreaFix-
  Requests and tries  to  unlink  you  from  the  echo  by
  sending an AreaFix-Request to your uplink.

  As soon as one downlink requests this area, it  will  be
  set  to  active and a new request to your uplink will be
  sent.
*P

  All this can only be done, if the uplink  is  listed  in
  the ^Forward AreaFix-Requests^ list.

  See also:  ^Disable Passive^
*E
*B 83,Area List (Node)
  Area List (Node)
  ────────────────────────────────────────────────────────

  This  list  gives  you a direct overview about all areas
  available  to  this  node  regarding  the  settings   of
  ^Groups^ and ^Security-Level^.
  You may add/delete the node from each area by tagging it
  with 'Space', select all areas with 'ALT-A' or clear all
  selections with 'ALT-C'.
*E
*B 84,User names
  User names
  ────────────────────────────────────────────────────────

  These are the names of the system users. The first  name
  is  typically your name (the SysOp). Also, you can enter
  other people working with FastEcho and/or your mailer or
  your handles here.

  See also:  ^Exclude users^  ^Keep users^
*E
*B 85,Name
  Name
  ────────────────────────────────────────────────────────

  This is the name of the SysOp of this system.

  See also:  ^Exclude SysOps^  ^Node-Manager^
*E
*B 86,Exclude users
  Exclude users
  ────────────────────────────────────────────────────────

  When importing *.MSG netmail  messages from your ^Netmail^
  into a  QBBS netmail board  with FEUtil Import,  you can
  exclude  netmails destinated to one of the names defined
  in ^User names^ by enabling this option.
*E
*B 87,Exclude SysOps
  Exclude SysOps
  ────────────────────────────────────────────────────────

  When importing *.MSG netmail messages  from your ^Netmail^
  into a QBBS netmail board with  FEUtil Import,  you  can
  exclude  netmails destinated to one of the names defined
  in the ^Name^ field of  the node manager  by enabling this
  option.
*E
*B 88,Keep SEEN-BY
  Keep SEEN-BY
  ────────────────────────────────────────────────────────

  This flag indicates if the 'SEEN-BY' lines  of  the  im-
  ported  echomail should be stored in your messagebase or
  not.  SEEN-BY's are typically not very  interesting  and
  take  pretty much space in your messagebase, so it shall
  only be necessary to keep them for debugging of the mail
  routing or similar purposes.
*E
*B 89,Check .PKT destination
  Check .PKT destination
  ────────────────────────────────────────────────────────

  This  flag  indicates  if FastEcho should check incoming
  packets for the destination address  when  tossing.   If
  the  destination  address of a mail-packet is not one of
  your akas, this .PKT will be refused.

  See also:  ^Security^
*E
*B 90,Comment
  Comment
  ────────────────────────────────────────────────────────

  This  field  may  be  used  to  describe the area or its
  purpose.   This  description  will  be added to the area
  listing generated by AreaFix when a user requests  %LIST
  with ^Detailed List^ turned on.
*E
*B 91,Update BBS Config
  Update BBS Config
  ────────────────────────────────────────────────────────

  If this option is enabled, FastEcho  will  automatically
  add  new  areas  created  by  ^Auto-Area-Create^  to  your
  BBS area configuration depending  on  the  settings  for
  ^BBS Software^.

  See also:  ^New area defaults (BBS)^
*E
*B 92,New area defaults (BBS)
  New area defaults (BBS)
  ────────────────────────────────────────────────────────

  These  are  the defaults that will be used for new areas
  added to your BBS area configuration.

  Please refer  to your ^BBS Software^ package's  manual for
  detailed  description  of  the  purpose  and use of each
  flag.
*E
*B 93,BBS Software
  BBS Software
  ────────────────────────────────────────────────────────

  FastEcho's ^Auto-Area-Create^ supports following BBS Soft-
  ware packages:   RemoteAccess(tm) 1.11/2.00
                   QuickBBS(tm)     2.76
                   SuperBBS(tm)     1.17
                   ProBoard(tm)     1.22/1.30
                   T.A.G.(tm)       2.6d
*E
*B 94,Secure Inb.
  Secure Inbound
  ────────────────────────────────────────────────────────

  This path will be searched for  inbound  mail  like  the
  ^Inbound^. In difference to that,  .PKTs that are found in
  that  path  will  NOT  be  checked  according  to   your
  ^Security^ settings.  So be sure,  that all incoming .PKTs
  in  this path are secure. It is useful for .PKTs created
  by local programs like .TIC announcers etc.
*E
*B 95,DB Queue
  DB Queue
  ────────────────────────────────────────────────────────

  This is the path to your  D'Bridge(tm)  queue  directory
  where  D'Bridge  stores its outbound queue. When running
  on a D'Bridge system, FastEcho  can  create  and  insert
  outgoing   mail-bundles   according   to  the  DB  Xmail
  specifications,  instead of  creating  *.MSG-style file-
  attach messages created for FrontDoor(tm) systems.
*P

  In  following  cases  FastEcho will create a *.MSG file-
  attach though:

     - one of the base36 numbers is greater than 46655
     - a point is not a point of your main address
*E
*B 96,Use EMS for buffering
  Use EMS for buffering
  ────────────────────────────────────────────────────────

  Here you can disable the automatic usage of  all  avail-
  able  expanded  memory  (EMS)  for  write buffering when
  creating outbound mail packets.
  FastEcho  can use upto 64kB and at minimum 16kB for each
  packet  it  opens  and adjusts the size to the amount of
  available memory.
*E
*B 97,Kill grunged date
  Kill grunged date
  ────────────────────────────────────────────────────────

  With this option enabled, FEUtil  PURGE  will  kill  all
  messages that have a grunged date.

  That is a date either bad (32-13-1991) or a date in  the
  future (01-01-2001).
*E
*B 98,Mandatory
  Mandatory                                 * Nodes only *
  ────────────────────────────────────────────────────────

  With  this  flag  enabled, all AreaFix 'unlink'-requests
  from  downlinks  that  are  linked  to that area will be
  rejected. You only can unlink a  system  from  that area
  with FESetup.
*E
*B 99,Keep users
  Keep users
  ────────────────────────────────────────────────────────

  With this flag enabled, FEUtil PURGE will NOT  kill  any
  mails  in  this  area  that are addressed to one of your
  ^User names^ and currently  NOT read (received),  even  if
  they  would  be  killed  according  to  your settings of
  ^Purging^ or ^Kill read^.
*E
*B 100,Seen-by
  Seen-by
  ────────────────────────────────────────────────────────

  Here you can select the akas that will be added  to  the
  SEEN-BYs  of all echomails that pass your system in that
  area. This normally is only needed on multiline  systems
  to avoid problems with  the  dupe-detection  by  SEEN-BY
  checking.
*E
*B 101,Allow Remote Maintenance
  Allow  Remote  Maintenance                * Nodes only *
  ────────────────────────────────────────────────────────

  With  this  flag  enabled,  this  system  is  allowed to
  perform changes remotely for other systems  via  AreaFix
  requests ("%FROM <address>").

  Only  enable  this  if really needed and if you are sure
  about that system as it's possible to cause a lot harm.
*E
*B 102,List Prefix
  List Prefix
  ────────────────────────────────────────────────────────

  Most  Compression  Programs have the capability to use a
  textfile  in  which  all  the files to be compressed are
  listed, rather than specifying each file in  the command
  line.  This  speeds  up  compressing  many .PKTs for one
  system  at one time as the program has only to be called
  once.
*P

  The commandline will look like this:

         program <options> archive [prefix]listfile

  Most wide-spread Compression Programs support '@' as the
  list prefix. Check out your tool's documentation if  you
  are in doubt.
*P

  If this prefix is not specified, FastEcho will call  the
  packer  specifying each filename on the command line and
  calling the packer as long as there are .PKTs left.
*E
*B 103,Allow %PWD
  Allow %PWD                                * Nodes only *
  ────────────────────────────────────────────────────────

  If this option is enabled, your downlinks are allowed to
  change their ^AreaFix-Password^ using the %PWD  metacom-
  mand in their requests.
*E
*B 104,Allow %PKTPWD
  Allow %PKTPWD                             * Nodes only *
  ────────────────────────────────────────────────────────

  If this option is enabled, your downlinks are allowed to
  change  their  ^ARCmail-Password^  using the %PKTPWD meta-
  command in their requests.
*E
*B 105,Unconditional
  Unconditional                             * Nodes only *
  ────────────────────────────────────────────────────────

  If  this flag is enabled, a requested area, which is not
  listed in one of the list files, will  be  forwarded  to
  this uplink if downlink's the security and groups match.
  Further you don't have to specify a ^Area List^ if you set
  this   flag as the request would be  forwarded  uncondi-
  tionally (only security and groups have to match).
*E
*B 106,Group Area Defaults
  Group Area Defaults
  ────────────────────────────────────────────────────────

  One  of  the  advanced abilities of FastEcho is the Area
  Grouping. You can assign each group specific values  for
  the area field entries, which will be used when manually
  adding/editing an (new) area or via ^Auto-Area-Create^.
  When manually editing your areas, you will  be  prompted
  to take over the group's defaults or not.
*P

  One  main goal of this is the flexibility when using the
  ^Auto-Area-Create^ functions.  You can specify which  kind
  of area the newly created  areas  are  (Local/Echomail),
  define  the  type of storage, preset the flags and auto-
  matically forward the new area to the systems listed  in
  'Export-to',  this  reduces  the  need  of manual inter-
  action to a minimum.
*P

  To use this flexibility, you  should assign  each uplink
  a different  ^New areas' default Group^ and  modify  the
  settings for this specific group to fit your needs.

  See also:  ^Board (default)^  ^Export to (default)^
*E
*B 107,Board (default)
  Board (default)
  ────────────────────────────────────────────────────────

  When using QBBS as ^Storage^, you can instruct FastEcho to
  take the first  unused  QBBS  board  starting  from  the
  specified  number. Thus the new areas will appear sorted
  according to the uplink.  For example  a  value  of  150
  would  cause  ^Auto-Area-Create^  to search  for the first
  free QBBS board beginning with 150.  If no board >=  150
*P

  is free, the messages are tossed to the badmailboard for
  further processing.

  See also:  ^Board^
*E
*B 108,Export to (default)
  Export to (default)
  ────────────────────────────────────────────────────────

  The entries in this field will be copied to a new  area.
  For  example, if  you  are  a mail-server, you can auto-
  matically forward each new area you  receive  from  your
  uplink to your downlinks, if you enter them here.

  See also:  ^Export to^
*P

  Note:  This field is only used  for ^Auto-Area-Create^ and
         NOT for ^Forward AreaFix-Requests^, forwarded areas
         will only have the uplink and  the  downlink, who
         requested that area, set active !
*E
*B 109,Default for rescan
  Default for rescan                        * Nodes only *
  ────────────────────────────────────────────────────────

  When a user requests the %RESCAN of areas without giving
  neither  a  value for %DAYS nor %MSGS, normally FastEcho
  will  rescan  ALL  messages in each area. If you want to
  restrict the rescan by default, you can select how  many
  messages  should  be  rescanned  by  default  by  either
  specifying a ^Default for %DAYS^ or ^Default for %MSGS^.
*E
*B 110,Default for %DAYS
  Default for %DAYS                         * Nodes only *
  ────────────────────────────────────────────────────────

  This is the default value for %DAYS which will  be  used
  if  neither  %DAYS  nor %MSGS is specified in an AreaFix
  %RESCAN request and ^Default for rescan^ is set to %DAYS.
*E
*B 111,Default for %MSGS
  Default for %MSGS                         * Nodes only *
  ────────────────────────────────────────────────────────

  This is the default value for %MSGS which will  be  used
  if  neither %DAYS  nor %MSGS is specified for an AreaFix
  %RESCAN request and ^Default for rescan^ is set to %MSGS.
*E
*B 112,Maximum for %DAYS
  Default for %DAYS                         * Nodes only *
  ────────────────────────────────────────────────────────

  This  is the maximum value for %DAYS to which the values
  specified in AreaFix requests will be restricted.
*E
*B 113,Maximum for %MSGS
  Default for %MSGS                         * Nodes only *
  ────────────────────────────────────────────────────────

  This  is the maximum value for %MSGS to which the values
  specified in AreaFix requests will be restricted.
*E
*B 114,Kill read
  Kill read
  ────────────────────────────────────────────────────────

  If  you have enabled this option, FEUTIL PURGE will kill
  all  messages  that have been read by you. That means it
  takes the LASTREAD.BBS pointer of this area and  deletes
  all  messages that are located  before  it.  The  normal
  ^Purging^ functions have no effect for these messages !
*E
*B 115,Keep netmails
  Keep netmails
  ────────────────────────────────────────────────────────

  With  this switch turned on, FEUtil IMPORT will NOT kill
  netmails  after  being  imported from *.MSG to your QBBS
  netmail boards.
  Note that the remaining mails will be imported everytime
  you run FEUtil IMPORT !
*E
*B 116,Secure TOSS mode
  Secure TOSS mode                            * obsolete *
  ────────────────────────────────────────────────────────

  If  this  switch  is  turned ON FastEcho TOSS will store
  some info about the  currently  processed  .PKT  between
  each  message.  If FastEcho is interrupted (by error for
  example), it will restart at the last processed  message
  to avoid dupes and to speed the  further  processing  of
  the  interrupted  file.   However this can slow down the
*P

  tossing  especially  if  you  don't use a harddisk cache
  with staged write.
*E
*B 117,Disable Passive
  Disable Passive
  ────────────────────────────────────────────────────────

  With this switch you can disable the automatic switching
  of  Passthrough  areas to Passive when the last downlink
  unlinks this area via AreaFix.

  See also:  ^Passive (Area)^
*E
*B 118,Maximum open .QQQs
  Maximum open .QQQs                        * Nodes only *
  ────────────────────────────────────────────────────────

  This is the number of outbound .QQQ files (these are the
  packets  that  contain the processed mails for the other
  systems and will later on be renamed to .PKT) which  are
  held  open  simultaneously  by  FastEcho. By default one
  file  for  each system will  be  held  open  for  faster
  processing.  Of course the number of open filehandles is
*P

  limited to your FILES setting in CONFIG.SYS and FastEcho
  will stop with an error  if  it  runs  out  of  handles.
  However,  for  speed purposes it's better to adjust your
  FILES setting to a  higher  value  than  to  limit  this
  maximum number.
  I suggest that you only use this limit if you  run  into
  non-recoverable errors like 'Sharing Buffer Overflow' in
  some LAN environments !
*E
*B 119,Send Notify
  Send Notify                               * Nodes only *
  ────────────────────────────────────────────────────────

  This setting instructs FastEcho NOTIFY to  send  AreaFix
  link  information  to this system if you call it without
  any parameters. By default, FastEcho  NOTIFY  will  send
  this info to all listed systems.
*E
*B 120,Sorting
  Sorting
  ────────────────────────────────────────────────────────

  The area list can be sorted in 3 different ways:

                1) by Name
                2) by Group
                3) by Board
*P

  If you choose 'by Name' you can 'type-ahead' the name of
  the  wanted  areas  character  by character. The current
  mask will be displayed at the bottom of the border.

  If you choose 'by Group' you can  quickly  jump  to  the
  first  area  belonging  to another group by pressing the
  corresponding key.
*E
*B 121,Tag
  Tag
  ────────────────────────────────────────────────────────

  You  can  automatically  tag  areas  whose names match a
  special  pattern or belong to a special group to perform
  'Changes' on them.

  If tagging by name, wildcards as '*' and '?'  are  valid
  (*IX style) like FE_*, *.024, ?.ENG.*.MAIL.* etc.
*E
*B 122,Add '+'
  Add '+'                                   * Nodes only *
  ────────────────────────────────────────────────────────

  By  default  FastEcho will use the '<area>' command when
  requesting a new area from your uplink.

  Some  AreaFix processors, however, need a preceeding '+'
  to process the request correctly. This will be added  if
  you set this option ('+<area>').
*E
*B 123,After Unpack
  After Unpack (External Programs)
  ────────────────────────────────────────────────────────

  Here  you can specify a program (or batch file) which is
  called by FastEcho  TOSS  directly  after  unpacking  of
  compressed mailbundles is finished.

  Using  this  feature  you can process all incoming .PKTs
  for example to create statistics, split large .PKTs etc.
*P

  You may type the full command-line including all kind of
  switches  etc.  The full path to the program has only to
  be  given if it cannot be found by means of your  'PATH'
  environment variable.

  See also:  ^Before Pack^
*E
*B 124,Before Pack
  Before Pack (External Programs)
  ────────────────────────────────────────────────────────

  Here  you can specify a program (or batch file) which is
  called by  FastEcho  just  before  packing  of  outgoing
  compressed mailbundles is started (TOSS/SCAN/PACK/AFIX).

  The  purpose is the same as ^After Unpack^,  but be  aware
  that all outgoing packets still have a .QQQ extension !
*P

  You may type the full command-line including all kind of
  switches  etc.  The full path to the program has only to
  be  given if it cannot be found by means of your  'PATH'
  environment variable.
*E
*B 125,Send Help
  Send Help                                 * Nodes only *
  ────────────────────────────────────────────────────────

  This  setting  instructs  FastEcho  HELP to send AreaFix
  help information to this system if you call  it  without
  any parameters. By default, FastEcho HELP will send this
  info to all listed systems.
*E
*B 126,AreaFix-Status
  AreaFix-Status                            * Nodes only *
  ────────────────────────────────────────────────────────

  Here you can set up which status the netmail receipts by
  FastEcho's AreaFix will have.

  Make sure that you set at least »Direct« if you normally
  route  netmail for this system via others to ensure that
  your passwords (AreaFix Notify) are kept secret.
*E
*B 127,Status
  Status
  ────────────────────────────────────────────────────────

  ^ARCmail-Status^ - status of ARCmail attaches
  ^AreaFix-Status^ - status of AreaFix receipt netmails

  See also:  ^Node-Manager^
*E
*B 128,Add '---'
  Add '---'                                 * Nodes only *
  ────────────────────────────────────────────────────────

  By default FastEcho doesn't append a tearline  '---'  at
  the  end  of AreaFix requests when requesting a new area
  from your uplink.

  Some  AreaFix  processors, however, need the tearline to
  process the request correctly.
*E
*B 129,Allow %COMPRESS
  Allow %COMPRESS                           * Nodes only *
  ────────────────────────────────────────────────────────

  If this option is enabled, your downlinks are allowed to
  change  their ^Packer^ using the %COMPRESS  metacommand in
  their requests.
*E
*B 130,Be 'quiet'
  Be 'quiet'
  ────────────────────────────────────────────────────────

  With this setting you can disable the output of external
  programs run from  FastEcho.  The  output  will  be  re-
  directed  to  NUL,  which  is supported by most programs
  not writing directly to the screen.
*E
*B 131,Temp. Inb.
  Temporary Inbound
  ────────────────────────────────────────────────────────

  If specified, FastEcho TOSS will extract the .PKTs  from
  the mail bundles found in your ^Inbound^ to this directory
  instead  of  the normal inbound directory. This may be a
  local harddisk in a  LAN  environment  or  a  2nd  local
  harddrive to speed up tossing.  You shall not use a ram-
  disk for this.
*E
*B 132,Update mailer config
  Update mailer config
  ────────────────────────────────────────────────────────

  When creating a new area via ^Auto-Area-Create^,  FastEcho
  will  update FrontDoor's, InterMail's or D'Bridge's area
  configuration files, if this option is enabled.
*E
*B 133,Toss Buffers
  Toss Buffers
  ────────────────────────────────────────────────────────

  You  can  select 3 different sizes for the internal TOSS
  buffers for .PKT and messagebase access. It's  suggested
  to reduce the size only if you are short on memory.

  However,  you may not notice big differences in speed if
  you are using a bigger staged write harddisk cache.
*E
*B 134,Use arrival date
  Use arrival date
  ────────────────────────────────────────────────────────

  In JAM areas FastEcho can store the date when a echomail
  message  has  been  tossed.  If  you enable this option,
  FEUtil PURGE will use this date instead of the date when
  the message was originally written.
*E
*B 135,Scan before tossing
  Scan before tossing
  ────────────────────────────────────────────────────────

  Normally,  FastEcho  TOSS  will process AreaFix messages
  after all mail is  tossed.  With  this  setting  enabled
  FastEcho  will scan the netmail directory before tossing
  the inbound mail and  therefore  changes  requested  via
  AreaFix will be used for the new inbound mail.
*E
*B 136,Max. Receipt size
  Max. Receipt size                         * Nodes only *
  ────────────────────────────────────────────────────────

  Some systems are not capable to process netmail messages
  bigger  than  a  certain  size  (typically  8-16kB).  As
  especially AreaFix %LIST receipts can break this  limit,
  FastEcho  can  split  the  netmail  it  creates  if they
  become bigger than the value specified.
*E
*B 137,Archive extensions
  Archive extensions
  ────────────────────────────────────────────────────────

  ARCmail  bundles  are  usually named like "xxxxxxxx.??y"
  where 'xxxxxxxx' is a hexadecimal number, '??'  the  day
  (abbreviated) and 'y' some kind of counter.

  All  echomail processors support a decimal number as 'y'
  (0-9, ARCmail standard), some processors  a  hexadecimal
*P

  number  (0-9  &  A-F)  and  a  minor  number  support  a
  alphanumerical character (0-9 & A-Z).

  Therefore you can tell FastEcho which range to use  when
  creating  ARCmail  bundles  and  which range to use when
  deciding whether an archive in the ^Inbound^  directory is
  a valid ARCmail bundle or not.
*E
*B 138,Mailer's semaphores
  Mailer's semaphores
  ────────────────────────────────────────────────────────

  FastEcho  has  the  ability  to  check  semaphore  files
  created  by  your mailer to see if a system is currently
  online.  Therefore it can skip  an  online  system  when
  adding .PKTs to the ARCmail bundles to prevent potential
  loss of data. This works with the multiline (commercial)
  version of FrontDoor(tm) and in Binkley-environments.
*P

  Further, FastEcho can create these semaphore files while
  adding  mail  to  prevent the mailer from calling out to
  the currently processed system.

  See also:  ^Semaphores^
*E
*B 139,Check complete files
  Check complete files
  ────────────────────────────────────────────────────────

  If enabled, FastEcho TOSS will check  the  inbound  mail
  archives  if  they  are  complete or if they are damaged
  (incomplete) and skip incomplete files.  It's  meant  to
  prevent dupes and allow a proper (ZModem) resume after a
  mail session has been interrupted.
*E
*B 9000,Paths
  Paths
  ────────────────────────────────────────────────────────

  All  paths  may  be  specified as usual.  A trailing '\'
  will be deleted.

  A special feature of FastEcho is that macros like '%FD%'
  can be used. These macros will be translated at run-time
  using   the   current   definition   of   the  specified
*P

  environment variable.  For example %FD%\NETMAIL with SET
  FD=C:\FRODO will  be  expanded  to  C:\FRODO\NETMAIL  at
  run-time.

  This  feature  makes  it  easier  to work with different
  configurations   and/or  in  a  network-  or  multiline-
  environment.
*E
*B 9999,NoHelp




             No help for this topic available
*E
