*I
Copyright·,2IndexZ.dGeneral ConfigurationVΦSystem AddressesÅXΘMain Address\[ΩAkas·\LDomain Manager¬^MDomain NameíeNAKA List (Domain)µgOZones (Domain)╖iPOutbound (Domain)Mk░Subdirectories╗m▒Hudson Message Basemp▓Net Mail Messagesr│Secure Inbound Files┬s┤Unsecure Inbound Filessu╡Temp inbound Packets#w╢Outbound Net Filesrx╖Temp Outbound Packets\}╕Dupe data baseæ╣Semaphore directoryπü║Netmail semaphore filepä╗IMAIL Log File Name@å╝Echotoss Log File NameÑç╜Path to ECHOMAIL.JAM^ë╛Path to user basekï┐Areas Action Log¿î└Local Inbound╤Ä┴Rules path╡ÉArealink optionsLÆKeep AreaLink Reply
òKeep AreaLink Request@ùPassword Expiration Days╫ÖForward every request6£Unlink Requests╧₧AreaLink Help TextÇúRemote Maint Help Text╘ÑAllow +* requestsX¿Ignore unknown systems&¬Area-Ignorelist┼½Sort Area lists╖¡ Unlink Hudson to passth(»xProduct codes▓░▄No import Names	╡@Sysop Namesñ╖rToss settings-║sHandle PKTs not for us╗tCheck for personal mail╟╛uDelete empty netmails√┴vUse Crc file names├ñSystem parametersΩ┼ÑMulti-tasking/Networké╟ªBBS-software used¥╔ºEnvironmentí╦¿Swap Optionsz╤⌐Direct screen-writing9╫¬Close graphic windowÿ╪½Setup Password ┌¼Sysop Nameµ█¡Default Originå▌«Before Toss╓▐»Before Toss II┬Γ░Quiet Packers¡Σ╓Dupe settings.µ╫Number of Dupe Records║τ╪Dupe Ring Handling┬Θ┘Circular Path Detection∞Miscellaneous∩	ARCmail 0.6 Compatibilityk≡
Kill Dead handling≤Handle sent ARCmail╜⌡Send Return Receiptπ°
Add Via LinesV√Use FTSC product namesì²Delete Squish/Msg/Jam-basesΣDeadlink days<:NodeMgr Defaultsp;Max. Packet Size╟<Max. Arcmail Sizeò=Nr. of PKTs to pack per call╬
>Default Message Status?Default Attach Status┐lLog Options≈m! Fatal errorsXn? Other errorsεo$ Accounting infoπp* Sent/Rcvd filesöq+ Brief messagesmr- Trivial messagess: Transaction infoçt# Password errors▌u~ Security/Dupe info7 v/ Spawning infoO"wDEBUG Logging₧#₧Space settingsσ%ƒMax. Message Size∩&áSingle Bundle Extracts)íMax. nr. of files/directoryÇ+óCompress after each Packet82úDiskspace before Unpackß4ñDiskspace before Toss½6ÑDiskspace before Compress╗;ªUse IMCOMP if less disk-space
=ºStop TOSS after x msgs╜?¿Stop TOSS after x netmailsçB╚Archive programsKE╨Compression programsδF╤Compression defaultsM╕Decompression programs;O╣Decompression defaultsóUÉArea ManagerÜWáArea Manager Keylist
bAreatagÜfComment]iOrigin LinebnActive¿q	Group²s
SecureSxMsgBase{Type6|
Board≈Path≤äDaysòëMsgsîHidden·ìUnlinkedáÅAutounlink5ÆMandatoryºôRead only5òTiny SBπûImport SBLÖKill DeadzÜHide SBΦ£Manualp₧Zone GateSáNo PAUSE>úDupecheck3ÑDupe MSGIDªªSquish Kill$⌐ Read/Write Security╡¬!Read/Write Security∙«"Area Origin Address=│#Area Seen-Bys\╡$Area Linked Systemsó╢%Rulenamex╕7System address (link list)φ║8Sysop name (link list)╝9Export onlyä╜:Import only╘╛;Paused┘┐<DeniedΓ└iArea Find Record├jArea List Recordî┼kArea Flow Statistic╩öGlobal Linked SystemsΩ╦òGlobal Add Node╬ûGlobal Delete NodeD╧ùGlobal Replace Nodew╨₧Global Area Switches╣╤ƒGlobal Active¿╓áGlobal Security┘íGlobal Hidden╔█óGlobal Unlinkedv▌úGlobal AutounlinkαñGlobal MandatoryPßÑGlobal Read OnlyµΓªGlobal Tiny SB¢ΣºGlobal Import SBτ¿Global Hide SB5Φ⌐Global Manual┬Θ¬Global Zone Gate¡δ½Global No %Pause⌐ε¼Global DupecheckÑ≡¡Global Squish Kill ≥«Global Dupe MsgId■≤▓Global Text Fieldsâ÷│Global Origin Line╗°┤Global ORIGIN ADDRESSφ√╡Global Seen-BysΘ²╢Global Message path ╝Global Digit Fields┤╜Global #Days╧╛Global #Msgs)┐Global Kill Dead■└Global Read SecurityT
┴Global Write Security≡
┬Global Group (By Group)Ä├Global Group (By Areatag)á⌠Node Manager«êNode Manager Keylist░φAddress█εSysop¬∩Pkt Origin Address╠≡Pack Priorityâ ±Node Domainφ"≥PKT Routing%≤AreaLink Passwordº)⌠Packet Passwordq+⌡GroupsG-÷Area Security
0≈Check PKT Password2°Notifyn4∙Remote Maint6·Change packer▓8√Check echo for ALNK-Msgv:ⁿExt. Arcmail Names<²Max. Mail Packet size@■Max. Arcmail sizeB PKTs To Pack Per CalloDRescan OK╞FAdd to new areasjHForward RequestsJCreate new areasÆKNew Areas GroupQMUplinkOProgram name■PFSC-0057 CompatibleèRMessage StatusoV	Attach Status░Z
Packer,_Capability7cCW Handling≡h
Alnk with '+'°lSend rules^nQFind Node RecorddrSList Node Record╕sTEdit/Show Linked AreasSvUNode STATISTIC╙y|Global groupsZ{}Global Add Groups│}~Global Remove Groups─~Global Change Groups▄ÇGlobal Set GroupsπÇüGlobal Autocreate Group≡üåGlobal node switchesâçGlobal Rescan OKùäêGlobal Create new areasåëGlobal UplinkæçèGlobal Forward RequestsUëïGlobal Change packer£èîGlobal Ext. Arcmail Names+îìGlobal Add to new areasΓÄÄGlobal NotifyVÉÅGlobal Remote Maintenance╙æÉGlobal FSC-0057 CompatibleFöæGlobal Alnkcheck Echo[ûÆGlobal Check PKT Password4ÿôGlobal Alnk with '+'_ÜöGlobal Send rules╩¢ÜGlobal node fieldsΦ₧¢Global Pkt Origin Address¿á£Global Message Status0ú¥Global Attach StatusnÑ₧Global PackerººƒGlobal Capability⌐áGlobal CW Handling∙¬íGlobal Program namew¼óGlobal Node Domain╦¡ñGlobal digit fields╩»ÑGlobal Area Securityà▒ªGlobal max. Arcmail sized│ºGlobal Max. Packet Sizeÿ╡¿Global Pack Priorityi╖⌐Global PKTs To Pack Per Call¡╣XGroup Manager╨╗╒Group Descriptionü╛╓Group Secure»┐╫Group Msgbasee┬╪Group Boards¿├┘Group PathÑ┼┌Group Days≤╞█Group Msgsp╔▄Group Hiddenf╦▌Group Autounlink
═▐Mandatoryx╬▀Read only╨αGroup Tiny SB┤╤ßGroup Zonegate$╘ΓGroup Import SB╫πGroup Hide SBC╪ΣGroup No %PAUSE╦┘σGroup Dupecheck┐█µGroup Kill dead0▌τGroup kill on the fly°▀ΦGroup Dupecheck on Msgid─ßΘGroup manual<ΣΩGroup Read Security3µδGroup Write Securitypτ∞Group Origin Address«ΦφGroup Seen-Bys╟Ω╝Forward Manager∞╜Forward Manager Keylist·≡YUplink Address╨≥ZUplink Namei⌠[Areas file}÷\Send to`·]Password3ⁿ^Access Groupî²_Create GroupA  Pack Routingó@Route DescriptionƒARoute via>	BRouted Systemsñ
CExcepted SystemsσäImport/Export Functions╫àSelect GroupsY(#Export Areas.Bbscî#Export GoldED Areafileö≡#Export FidoNet.na╤T$Export timEd Areafile
╕$Import Areas.BbsrτExit to Dos«τExit to Dos    
*B 0,No help
 NO HELP                                                ^Index^
 ────────────────────────────────────────────────────────────

 At this time, help isn't available for this point.
 Inform the author!

*E
*B 1,Copyright
 COPYRIGHT                                              ^Index^
 ────────────────────────────────────────────────────────────

 IMAIL - The "Semi-Intuitive" Mail Processor  Version  1.70b

 (C) Copyright 1992-1995 by Andreas Klein, Freising, Germany.

 All Rights Reserved.

 Documentation written by Klaus Bader, 2:2480/7

*E
*B 50,Index
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────

 ^! Fatal errors^                ^# Password errors^
 ^$ Accounting info^             ^* Sent/Rcvd files^
 ^+ Brief messages^              ^- Trivial messages^
 ^/ Spawning info^               ^: Transaction info^
 ^? Other errors^                ^~ Security/Dupe info^
 ^AKA List (Domain)^             ^ARCmail 0.6 Compatibility^
 ^Access Group^                  ^Active^
 ^Add Via Lines^                 ^Add to new areas^
 ^Address^                       ^Akas^
 ^Allow +* requests^             ^Alnk with '+'^
 ^Archive programs^              ^Area Find Record^
 ^Area Flow Statistic^           ^Area Linked Systems^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Area List Record^              ^Area Manager Keylist^
 ^Area Manager^                  ^Area Origin Address^
 ^Area Security^                 ^Area Seen-Bys^
 ^Area-Ignorelist^               ^AreaLink Help Text^
 ^AreaLink Password^             ^Arealink options^
 ^Areas Action Log^              ^Areas file^
 ^Areatag^                       ^Attach Status^
 ^Autounlink^                    ^BBS-software used^
 ^Before Toss II^                ^Before Toss^
 ^Board^                         ^CW Handling^
 ^Capability^                    ^Change packer^
 ^Check PKT Password^            ^Check echo for ALNK-Msg^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Check for personal mail^       ^Circular Path Detection^
 ^Close graphic window^          ^Comment^
 ^Compress after each Packet^    ^Compression defaults^
 ^Compression programs^          ^Copyright^
 ^Create Group^                  ^Create new areas^
 ^DEBUG Logging^                 ^Days^
 ^Deadlink days^                 ^Decompression defaults^
 ^Decompression programs^        ^Default Attach Status^
 ^Default Message Status^        ^Default Origin^
 ^Delete Squish/Msg/Jam-bases^   ^Delete empty netmails^
 ^Denied^                        ^Direct screen-writing^
 ^Diskspace before Compress^     ^Diskspace before Toss^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Diskspace before Unpack^       ^Domain Name^
 ^Domain Manager^                ^Dupe MSGID^
 ^Dupe Ring Handling^            ^Dupe data base^
 ^Dupe settings^                 ^Dupecheck^
 ^Echotoss Log File Name^        ^Edit/Show Linked Areas^
 ^Environment^                   ^Excepted Systems^
 ^Exit to Dos^                   ^Export Areas.Bbs^
 ^Export FidoNet.na^             ^Export GoldED Areafile^
 ^Export only^                   ^Export timEd Areafile^
 ^Ext. Arcmail Names^            ^FSC-0057 Compatible^
 ^Find Node Record^              ^Forward Manager Keylist^
 ^Forward Manager^               ^Forward Requests^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Forward every request^         ^General Configuration.^
 ^Global #Days^                  ^Global #Msgs^
 ^Global Active^                 ^Global Add Groups^
 ^Global Add Node^               ^Global Add to new areas^
 ^Global Alnk with '+'^          ^Global Alnkcheck Echo^
 ^Global Area Security^          ^Global Area Switches^
 ^Global Attach Status^          ^Global Autocreate Group^
 ^Global Autounlink^             ^Global CW Handling^
 ^Global Capability^             ^Global Change Groups^
 ^Global Change packer^          ^Global Check PKT Password^
 ^Global Create new areas^       ^Global Delete Node^
 ^Global Digit Fields^           ^Global Dupe MsgId^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Global Dupecheck^              ^Global Ext. Arcmail Names^
 ^Global FSC-0057 Compatible^    ^Global Forward Requests^
 ^Global Group (By Areatag)^     ^Global Group (By Group)^
 ^Global Hidden^                 ^Global Hide SB^
 ^Global Import SB^              ^Global Kill Dead^
 ^Global Linked Systems^         ^Global Mandatory^
 ^Global Manual^                 ^Global Max. Packet Size^
 ^Global Message Status^         ^Global Message path^
 ^Global No %Pause^              ^Global Node Domain^
 ^Global Notify^                 ^Global ORIGIN ADDRESS^
 ^Global Origin Line^            ^Global PKTs To Pack Per Call^
 ^Global Pack Priority^          ^Global Packer^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Global Pkt Origin Address^     ^Global Program name^
 ^Global Read Only^              ^Global Read Security^
 ^Global Remote Maintenance^     ^Global Remove Groups^
 ^Global Replace Node^           ^Global Rescan OK^
 ^Global Security^               ^Global Seen-Bys^
 ^Global Send rules^             ^Global Set Groups^
 ^Global Squish Kill^            ^Global Text Fields^
 ^Global Tiny SB^                ^Global Unlinked^
 ^Global Uplink^                 ^Global Write Security^
 ^Global Zone Gate^              ^Global digit fields^
 ^Global groups^                 ^Global max. Arcmail size^
 ^Global node fields^            ^Global node switches^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Group Autounlink^              ^Group Boards^
 ^Group Days^                    ^Group Description^
 ^Group Dupecheck on Msgid^      ^Group Dupecheck^
 ^Group Hidden^                  ^Group Hide SB^
 ^Group Import SB^               ^Group Kill dead^
 ^Group Manager^                 ^Group Msgbase^
 ^Group Msgs^                    ^Group No %PAUSE^
 ^Group Origin Address^          ^Group Path^
 ^Group Read Security^           ^Group Secure^
 ^Group Seen-Bys^                ^Group Tiny SB^
 ^Group Write Security^          ^Group Zonegate^
 ^Group kill on the fly^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Group manual^                  ^Group^
 ^Groups^                        ^Handle PKTs not for us^
 ^Handle sent ARCmail^           ^Hidden^
 ^Hide SB^                       ^Hudson Message Base^
 ^IMAIL Log File Name^           ^Ignore unknown systems^
 ^Import Areas.Bbs^              ^Import SB^
 ^Import only^                   ^Import/Export Functions^
 ^Index^                         ^Keep AreaLink Reply^
 ^Keep AreaLink Request^         ^Kill Dead handling^
 ^Kill Dead^                     ^List Node Record^
 ^Local Inbound^                 ^Log Options^
 ^Main Address^                  ^Mandatory^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Mandatory^                     ^Manual^
 ^Max. Arcmail Size^             ^Max. Arcmail size^
 ^Max. Mail Packet size^         ^Max. Message Size^
 ^Max. Packet Size^              ^Max. nr. of files/directory^
 ^Message Status^                ^Miscellaneous^
 ^MsgBase^                       ^Msgs^
 ^Multi-tasking/Network^         ^Net Mail Messages^
 ^Netmail semaphore file^        ^New Areas Group^
 ^No PAUSE^                      ^No import Names^
 ^Node Domain^                   ^Node Manager Keylist^
 ^Node Manager^                  ^Node STATISTIC^
 ^NodeMgr Defaults^              ^Notify^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Nr. of PKTs to pack per call^  ^Number of Dupe Records^
 ^Origin Line^                   ^Outbound (Domain)^
 ^Outbound Net Files^            ^PKT Routing^
 ^PKTs To Pack Per Call^         ^Pack Priority^
 ^Pack Routing^                  ^Packer^
 ^Packet Password^               ^Password Expiration Days^
 ^Password^                      ^Path to ECHOMAIL.JAM^
 ^Path to user base^             ^Path^
 ^Paused^                        ^Pkt Origin Address^
 ^Product codes^                 ^Program name^
 ^Quiet Packers^                 ^Read only^
 ^Read only^                     ^Read/Write Security^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Read/Write Security^           ^Remote Maint Help Text^
 ^Remote Maint^                  ^Rescan OK^
 ^Route Description^             ^Route via^
 ^Routed Systems^                ^Rulename^
 ^Rules path^                    ^Secure Inbound Files^
 ^Secure^                        ^Semaphore directory^
 ^Send Return Receipt^           ^Send rules^
 ^Send to^                       ^Setup Password^
 ^Single Bundle Extract^         ^Sort Area lists^
 ^Space settings^                ^Squish Kill^
 ^Stop TOSS after x msgs^        ^Stop TOSS after x netmails^
 ^Subdirectories^                ^Swap Options^
 ...
*P
 INDEX                                              ^Copyright^
 ────────────────────────────────────────────────────────────
 ...
 ^Sysop Name^                    ^Sysop Names^
 ^Sysop name (link list)^        ^Sysop^
 ^System Addresses^              ^System address (link list)^
 ^System parameters^             ^Temp Outbound Packets^
 ^Temp inbound Packets^          ^Tiny SB^
 ^Toss settings^                 ^Type^
 ^Unlink Hudson to passth^       ^Unlink Requests^
 ^Unlinked^                      ^Unsecure Inbound Files^
 ^Uplink Address^                ^Uplink Name^
 ^Uplink^                        ^Use Crc file names^
 ^Use FTSC product names^        ^Use IMCOMP if less disk-space^
 ^Zone Gate^                     ^Zones (Domain)^
*E
*B 100,General Configuration
 GENERAL CONFIGURATION                                 ^Index^
 ───────────────────────────────────────────────────────────

 This  option  leads to  another menu  which  allows  various
 systemwide parameters to be set.

 See also: ^System Addresses^          ^Domain Manager^
           ^Subdirectories^            ^Log options^
           ^Arealink Options^          ^Product Codes^
           ^No Import^                 ^Sysop Names^
           ^Dupe Settings^             ^NodeMgr Defaults^
           ^Space Settings^            ^Toss Settings^
           ^System Parameters^         ^Miscellaneous^
*E
*B 1000,System Addresses
 SYSTEM ADDRESSES                                       ^Index^
 ────────────────────────────────────────────────────────────

 The "System Addresses" menu allows you to define  up  to  50
 network addresses. The first of the addresses  is  known  as
 your primary address. It should  be  the  same  as  the  one
 defined as your primary in your mailer and / or BBS program.
 The  other  addresses  given  are  your  system's  AKAs  (or
 aliases).

 When IMSETUP detects that you made changes to  the  list  of
 system addresses, the area database, the group database  and
 the domain information will be corrected automatically.

 See also: ^Main Address^
           ^AKAs^
*E
*B 1001,Main Address
 MAIN ADDRESS                                           ^Index^
 ────────────────────────────────────────────────────────────

 Addresses should be given in the form:

         zone:net/node.point

 Addresses may be in different zones, and even  in  different
 domains (or networks). At least the primary address must  be
 specified.

 See also: ^System Addresses^
           ^AKAs^
*E
*B 1002,Akas
 AKAs                                                   ^Index^
 ────────────────────────────────────────────────────────────

 Addresses should be given in the form:

         zone:net/node.point

 Addresses may be in different zones, and even  in  different
 domains (or networks). At least the primary address must  be
 specified.

 See also: ^System Addresses^
           ^Main Address^
*E
*B 1100,Domain Manager
 DOMAIN MANAGER                                         ^Index^
 ────────────────────────────────────────────────────────────

 In  this  menu  the  domain(s)  to  which  you  belong   are
 specified. The word "domain" is used to distinguish  between
 different amateur networks such as SIGnet and FidoNet.

 Here, you should indicate the domains of  which  you  are  a
 part, the zones belonging to these  domains,  your  AKAs  in
 this domain, and the outbound directory for each domain. You
 should also specify  those  domains  to  which  you  do  not
 belong, but with which you exchange mail.

 IMAIL  uses  this  information  for   MSGID   kludges   when

 ...
*P
 DOMAIN MANAGER                                         ^Index^
 ────────────────────────────────────────────────────────────
 ...

 generating net mail  messages.

 More  importantly, outbound mail for  a specific domain will
 be placed in the directory you specify here.

 If you are in doubt of which zone you belong  to,  or  which
 domain, please contact your nearest Coordinator or Host.

 See also: ^Domain Name^          ^Zones (Domain)^
           ^AKA List (Domain)^    ^Outbound (Domain)^

 For available keys see next help page...
*P
 DOMAIN MANAGER KEYLIST                                 ^Index^
 ────────────────────────────────────────────────────────────
 ...

 Available keys:

 <ENTER>      Edit               <F1>         Help
 <ESC>        Exit w/o save      <F10>        Save and Exit
 <INS>        Add Record         <DEL>        Delete Record
 <HOME>       First Record       <END>        Last Record
 <CRSR UP>    Previous Record    <CRSR DOWN>  Next Record
 <CRSR RIGHT> Previous Record    <CRSR LEFT>  Next Record
*E
*B 1101,Domain Name
 DOMAIN NAME                                            ^Index^
 ────────────────────────────────────────────────────────────

 Specify  the name of  the  domain.  No universally  accepted
 standard seems  to exist,  but some  examples  are:  FidoNet
 for zone 1 to 7, and so on.

 The name  must not  contain  the  character '@';  everything
 before that  character and  itself will be  deleted when you
 save your configuration.

 See also: ^Domain Manager^       ^Zones (Domain)^
           ^AKA List (Domain)^    ^Outbound (Domain)^
*E
*B 1102,AKA List (Domain)
 AKA LIST (DOMAIN)                                      ^Index^
 ────────────────────────────────────────────────────────────

 Here you  enter the selection window for the addresses which
 belong to  each domain.  In that window,  you toggle-mark an
 address  with space.  Leave the  window with  ESC or save it
 with F10.

 See also: ^Domain Manager^       ^Outbound (Domain)^
           ^Zones (Domain)^       ^Domain Name^
*E
*B 1103,Zones (Domain)
 ZONES (DOMAIN)                                         ^Index^
 ────────────────────────────────────────────────────────────

 You enter a window in which  you specify all the zones which
 belong to this domain. For example, for FidoNet, these would
 be 1 to 7.

 See also: ^Domain Manager^       ^Outbound (Domain)^
           ^AKA List (Domain)^    ^Domain Name^
*E
*B 1104,Outbound (Domain)
 OUTBOUND (DOMAIN)                                      ^Index^
 ────────────────────────────────────────────────────────────

 If you belong to  more than one domain,  it might be wise to
 keep the  outbound  mail for  each domain  separate. In this
 case, specify each directory here. In Binkley mode, mail for
 points will be place "under" these directories.

 If this  field is  left  empty,  IMAIL will  default  to the
 directory specified as Outbound Net Files (see below).

 See also: ^Domain Manager^       ^Zones (Domain)^
           ^AKA List (Domain)^    ^Domain Name^
*E
*B 1200,Subdirectories
 SUBDIRECTORIES                                         ^Index^
 ────────────────────────────────────────────────────────────

 In this menu, specify the paths to the various  files  IMAIL
 needs to use  during  execution.  Most  of  the  fields  are
 required  and  you  should  NOT  use   the   same   physical
 directories for more than one entry. It's also NOT useful if
 other  programs  use   the   IMAIL   temporary   directories
 (especially the FrontDoor packet directory must not be  used
 by IMAIL).

 When   specifying   subdirectories,   you   may   omit   the
 trailingbackslash.

 For more Information enter menu and press F1.
*E
*B 1201,Hudson Message Base
 HUDSON MESSAGE BASE                                    ^Index^
 ────────────────────────────────────────────────────────────

 Specify the  path to the  Hudson format  message base files.
 These message base files are  searched for outgoing messages
 when you run the IMAIL SCAN function. If you are not using a
 Hudson message base, this field may be left empty.
*E
*B 1202,Net Mail Messages
 NET MAIL MESSAGES                                      ^Index^
 ────────────────────────────────────────────────────────────

 The path to where your  mailer stores  its net  mail message
 ( *.MSG)  files.  IMAIL will use  this  when  searching  for
 existing  file  attaches,  when  creating  new  file  attach
 messages, or when it generates outgoing net mail of its own.

 -> This field is required. <-
*E
*B 1203,Secure Inbound Files
 SECURE INBOUND FILES                                   ^Index^
 ────────────────────────────────────────────────────────────

 This is  where your  mailer  stores inbound  compressed mail
 files and packets from a password  protected  session. IMAIL
 will look here when you run the TOSS function.

 NOTE: Please do =not= run IMAIL from this directory!

 ->  This field is required. <-
*E
*B 1204,Unsecure Inbound Files
 UNSECURE INBOUND FILES                                 ^Index^
 ────────────────────────────────────────────────────────────

 If your mailer knows a seperate  inbound  directory  for un-
 protected  sessions,  you can  specify  it here.  IMAIL only
 accepts  uncompressed packets  from  this  directory and any
 echomail in  such packets  is automatically  moved  into the
 badmail area.
*E
*B 1205,Temp inbound Packets
 TEMP INBOUND PACKETS                                   ^Index^
 ────────────────────────────────────────────────────────────

 This directory  is used by  IMAIL TOSS  to store  packets as
 they are extracted from ARCmail files,  and  before they are
 processed.

 -> This field is required. <-
*E
*B 1206,Outbound Net Files
 OUTBOUND NET FILES                                     ^Index^
 ────────────────────────────────────────────────────────────

 This subdirectory is  where your mailer  normally  looks for
 outbound  compressed  files. These  files  may  be generated
 by all of IMAIL's functions.

 This  CANNOT  be the same  subdirectory  as the  Inbound Net
 Files directory,  otherwise IMAIL will process the  files as
 if they were FOR your system.

 Note that if you are running in a Binkley  environment, this
 will  be the  subdirectory in  which outgoing  mail for your
 PRIMARY zone will be placed.  Mail addressed  to other zones

 ...
*P
 OUTBOUND NET FILES                                     ^Index^
 ────────────────────────────────────────────────────────────
 ...

 will be placed in other subdirectories, having the same root

 name as the one specified in this field, but with a  3-digit
 hexadecimal extension (the zone of the destination address).
 For more details, please refer to the Binkley documentation.

 This subdirectory will be  used whenever you  do not specify
 an outgoing subdirectory in the Domains menu (see above).

 -> This field is required. <-

 See also: ^Domains^
*E
*B 1207,Temp Outbound Packets
 TEMP OUTBOUND PACKETS                                  ^Index^
 ────────────────────────────────────────────────────────────

 This is the directory in which  IMAIL and  IMPACK will build
 outbound  packets prior  to compression  into ARCmail files.
 This  directory  must  NOT  be  the  same  as  your  mailers
 temporary  packet  directory,  nor may  it be  the  same  as
 IMAIL's  Temporary  Inbound  Packet  directory.  If omitted,
 IMAIL will default to the Outbound Net Files directory.

 -> This field is required. <-
*E
*B 1208,Dupe data base
 DUPE DATA BASE                                         ^Index^
 ────────────────────────────────────────────────────────────

 Enter a directory for the  dupe database files if you do not
 want  them to  be stored  in the home  directory of IMAIL at
 runtime  which means  that TOSS  copies the  database to the
 defined directory at start and moves it back at the end.  In
 local area networks, it can speed up things tremendously  if
 you place the dupe database on a local harddisk.

 If the database should not be moved, leave this field empty!
*E
*B 1209,Semaphore directory
 SEMAPHORE DIRECTORY                                    ^Index^
 ────────────────────────────────────────────────────────────

 This  directory is used to  store and create all semaphores.
 Also the mailer  rescan semaphore as  defined  below will be
 created in this directory.

 For  FrontDoor 2.20c  and Intermail,  this is  the semaphore
 directory as defined in the  FrontDoor setup,  for FrontDoor
 2.12 this is the directory where the FD environment variable
 points to.

 For other mailers check their documentation, especially when
 they use a semaphore directory for inter-task communication.
*E
*B 1210,Netmail semaphore file
 NETMAIL SEMAPHORE FILE                                 ^Index^
 ────────────────────────────────────────────────────────────

 If IMAIL  should tell your  mailer that  netmails  have been
 created  or  updated,  you should  specify  the name  of the
 necessary semaphore  file here.  IMAIL will create it in the
 semaphore directory if necessary.

 For FrontDoor this is FDRESCAN.NOW
 For InterMail this is IMRESCAN.NOW
*E
*B 1211,IMAIL Log File Name
 IMAIL LOG FILE NAME                                    ^Index^
 ────────────────────────────────────────────────────────────

 If you  wish IMAIL  to log  its  activity  to file,  you may
 specify  the name  of the log  file here.  The log file must
 be specified with a complete path.

 See also: ^Log Options^
*E
*B 1212,Echotoss Log File Name
 ECHOTOSS LOG FILE NAME                                 ^Index^
 ────────────────────────────────────────────────────────────

 Here you define the  name of the echotoss log file  which is
 used by  IMAIL to  determine  Jam,  Squish  and  *.MSG areas
 where new messages have  been entered. Your  editor and your
 bbs should use the same file name for this file.

 See also: ^Path to ECHOMAIL.JAM^
*E
*B 1213,Path to ECHOMAIL.JAM
 PATH TO ECHOMAIL.JAM                                   ^Index^
 ────────────────────────────────────────────────────────────

 When having entered mails in JAM areas, many editors and BBS
 programs create a file called ECHOMAIL.JAM. There, the areas
 with newly entered mails are  specified for SCAN ( Kinda the
 same as 'Echotoss log file name').

 Enter  the path  to this file  here ( Could well be the home
 directory of your BBS program).

 See also: ^Echotoss Log File Name^
*E
*B 1214,Path to user base
 PATH TO USER BASE                                      ^Index^
 ────────────────────────────────────────────────────────────

 Here you define,  where IMAIL can find the user base of your
 BBS Software.

 If you not define any file,  IMAIL search in the hudson base
 directory.
*E
*B 1215,Areas Action Log
 AREAS ACTION LOG                                       ^Index^
 ────────────────────────────────────────────────────────────

 In this file, IMAIL stores the following actions:

      Autoadding of an area        ADD
      Area requested               REQUEST
      Forward request              FWDREQ
      Unlink request               UNLINK
      Deletion of a dead area      DEAD
      Remote deletion of an area   REMOVE
      Relink of an unlinked area   RELINK
      Deadlink request             DEADLINK
*E
*B 1216,Local Inbound
 LOCAL INBOUND                                          ^Index^
 ────────────────────────────────────────────────────────────

 This local  inbound is  intended for PKTs generated by local
 utilities (file  announcements and other automatic messages)
 on which the security check would fail. IMAIL TOSS will only
 accept *.PKTs  from this  directory and  no security  checks
 will be done.

 DO NOT USE THIS INBOUND FOR ANY OF YOUR MAILER INBOUND!

*E
*B 1217,Rules path
 RULES PATH                                             ^Index^
 ────────────────────────────────────────────────────────────

 When you want to use the IMALNK area  rules feature,  IMALNK
 needs  to know the path where it  find the area  rules which
 are expected as textfiles.  This path is defined here and an
 empty field will disable the IMALNK area rules support.
*E
*B 1300,Arealink options
 AREALINK OPTIONS                                       ^Index^
 ────────────────────────────────────────────────────────────

 The options in this menu regard IMAIL's ^Area Manager^, called
 AREALINK. This function will do for IMAIL what AreaFix  does
 for other systems.

 Your downlinks will be able to request  that  new  areas  be
 sent to them, or that areas no longer be sent. Besides, they
 may request information on  which  areas  are  available  to
 them, and have a  list  of  the  areas  they  are  currently
 receiving. AreaLink can also request areas not available  on
 your system from your uplinks, thus further automating  your
 system.
*E
*B 1301,Keep AreaLink Reply
 KEEP AREALINK REPLY                                    ^Index^
 ────────────────────────────────────────────────────────────

 If you  enable this  option (set it to 'Y'), then IMAIL will
 not mark its outgoing messages as KILL/SENT. In other words,
 once the message has been sent,  it will remain in  your net
 mail directory for you to  see it.  Note that this  is valid
 only for  the messages  generated by  AreaLink,  but not for
 those it has processed.

 See also: ^Arealink Options^    ^Keep Arealink Request^
*E
*B 1302,Keep AreaLink Request
 KEEP AREALINK REQUEST                                  ^Index^
 ────────────────────────────────────────────────────────────

 This  switch  controls  whether  IMALNK  will  keep incoming
 arealink  requests  instead of  deleting  them.  IMALNK will
 process the message and

    None       delete it afterwards,
    All        keep it or
    With msg   keep it only if an additional msg to the
               was found Sysop.

 Note that this is only valid for the incoming messages which
 are processed by AreaLink, but not for those it has created.

 See also: ^Arealink Options^    ^Keep Arealink Reply^
*E
*B 1303,Password Expiration Days
 PASSWORD EXPIRATION DAYS                               ^Index^
 ────────────────────────────────────────────────────────────

 This allows you to specify that your downlinks should change
 their AreaLink password after a specified number of days. If
 set to 0,  this feature  is disabled.  AreaLink  will  still
 allow a system  to use AreaLink  if the deadline has passed,
 but it will add a warning saying that the password should be
 changed.  A sysop may change  his password  automatically by
 using the %PWD meta-command.

 See also: ^Arealink Options^
*E
*B 1304,Forward every request
 FORWARD EVERY REQUEST                                  ^Index^
 ────────────────────────────────────────────────────────────

 If this field  is set to yes, IMALNK forwards  area requests
 when  the area  is not known and regardless whether the area
 can be  found in  one  of  the  lists  given in  the Forward
 Manager.  By setting  this switch  to no,  IMALNK  will only
 request areas which can be found in the forward lists.

 The request is sent to the first matching uplink  (means the
 first uplink which  is in the  same domain as the requester)
 defined in the ^Forward Manager^.

 See also: ^Arealink Options^
*E
*B 1305,Unlink Requests
 UNLINK REQUESTS                                        ^Index^
 ────────────────────────────────────────────────────────────

 Here you can  specify  whether  AreaLink should  check areas
 ( whenever one user  requests to unlink from  an area and at
 least  once  per day  after  midnight  during  the statistic
 update)  whether you have areas with  only one system in the
 list of linked systems.

 If this single system is also listed in the ^Forward Manager^,
 IMAIL marks  this area unlinked and  sends an unlink request
 to this system.

 You can specify whether this function should  not to be run,

 ...
*P
 UNLINK REQUESTS                                        ^Index^
 ────────────────────────────────────────────────────────────
 ...

 only affect passthrough areas or all areas. Moreover you can
 exclude  single areas  or groups  from this  function in the
 ^Area Manager^/^Group Manager^ by setting the field "Autounlink"
 to 'N'.

 Using this feature you can  prevent areas  from being tossed
 into the NUL device and consequently  reducing the amount of
 mail.

 See also: ^Arealink Options^   ^Unlink Hudson to passth^
*E
*B 1306,AreaLink Help Text
 AREALINK HELP TEXT                                     ^Index^
 ────────────────────────────────────────────────────────────

 In this field  you may  specify the  name of a  text file to
 send if a user  requests help  with AreaLink.  If no name is
 specified,  then AreaLink will respond to a request for help
 with a standard help message.

 If a file is specified,  it must be located in the directory
 pointed to  by the  IMAIL  environment  variable,  or in the
 directory which is current when IMAIL is run.

 See also: ^Arealink Options^
*E
*B 1307,Remote Maint Help Text
 REMOTE MAINT HELP TEXT                                 ^Index^
 ────────────────────────────────────────────────────────────

 In this field  you may  specify the  name of a text  file to
 send if a user requests help with AreaLink if this users has
 remote  maintenance  rights on  your  system.  If no name is
 specified,  then AreaLink will take the file specified under
 AreaLink Help Text.

 If a file is specified,  it must be located in the directory
 pointed to  by the  IMAIL  environment  variable,  or in the
 directory which is current when IMAIL is run.

 See also: ^Arealink Options^
*E
*B 1308,Allow +* requests
 ALLOW +* REQUEST                                       ^Index^
 ────────────────────────────────────────────────────────────

 This switch controls the use of '+*'  (link all areas) in an
 arealink request.  You can allow or disable  the use of this
 command.  This can  be useful  on high  traffic  systems  to
 prevent a  downlink from linking  all areas at once with one
 command.

 See also: ^Arealink Options^
*E
*B 1309,Ignore unknown systems
 IGNORE UNKNOWN SYSTEMS                                 ^Index^
 ────────────────────────────────────────────────────────────

 If this switch  is set to Yes,  IMALNK  simply ignores  ALNK
 requests  from systems  not  defined  in  the  ^Node Manager^,
 otherwise it  will respond  to  the  requesting system  that
 it has no allowance to do so.

 See also: ^Arealink Options^
*E
*B 1310,Area-Ignorelist
 AREA-IGNORELIST                                        ^Index^
 ────────────────────────────────────────────────────────────

 If you  want certain areas not to be requested  or autoadded
 to  all, create a  file  which contains the echotags of this
 areas  ( one per line) and  specify it  name here.  This can
 prevent the periodic recreation  of previosly deleted areas,
 since downlinks seem to have elephant's memories...

 See also: ^Arealink Options^
*E
*B 1311,Sort Area lists
 SORT AREA LISTS                                        ^Index^
 ────────────────────────────────────────────────────────────

 Arealink normally sorts the link, query and unlinked reports
 by areatag.  When you toggle this switch, Arealink will sort
 them by group first and then by areatag.

 See also: ^Arealink Options^
*E
*B 1312,Unlink Hudson to passth
 UNLINK HUDSON TO PASSTH                                ^Index^
 ────────────────────────────────────────────────────────────

 This switch allows (when  Unlink  Requests is set to All) to
 set Hudson  areas automatically  to passthrough  when Hudson
 areas are unlinked to free the associated board number.

 See also: ^Arealink Options^   ^Unlink Requests^
*E
*B 1400,Product codes
 PRODUCT CODES                                          ^Index^
 ────────────────────────────────────────────────────────────

 This small and apparently insignificant menu is really  very
 important. It allows you to indicate programs which  produce
 Type  2+  information  in  the  packet  header.  (For   more
 information about this and the Capability Word, see  Chapter
 15. Section a.) With this information, IMAIL TOSS will  know
 how to correctly process incoming mail. If it finds a packet
 with no capability word, it will scan the  list  of  product
 codes defined in this menu  to  see  if  the  packet  really
 contains zone and  point  information.  If  the  packet  was
 produced by one of the programs whose code is  listed  here,
 then it will treat the  packet  as  it  is  fully  Type  2+.

 ...
*P
 PRODUCT CODES                                          ^Index^
 ────────────────────────────────────────────────────────────
 ...

 Otherwise it will be treated as "Stone Age".

 Note that the product codes must be entered in hexadecimal.
*E
*B 1500,No import Names
 NO IMPORT NAMES                                        ^Index^
 ────────────────────────────────────────────────────────────

 In this  screen,  you  specify  the  names  of  persons  (or
 programs) which IMTHINGS IMPORT should ignore. For  example,
 if you  wish  messages  addressed  to  AreaLink  not  to  be
 imported into your net mail area, you would specify AREALINK
 here (case is not significant). Similarly,  if  you  do  not
 want net mail addressed to you to be imported, specify  your
 name in this menu.

 If you specify a '*' wildcard at the end of a name, anything
 starting with that name will not be imported.
*E
*B 1600,Sysop Names
 SYSOP NAMES                                            ^Index^
 ────────────────────────────────────────────────────────────

 In this screen,  you can specify up to  20 names  IMAIL TOSS
 should search for with the PERSMAIL function.

 When mail for one of these names is found  in incoming mail,
 it is either copied  into a separate area,  a netmail to the
 sysop is  created,  the fact is  only logged  or  it will be
 ignored altogether.

 NOTE!  Since every incoming message is checked against every
 single name herein,  this could slow down TOSS considerably!

 See also: ^Check for personal mail^
*E
*B 1650,Toss settings
 TOSS SETTINGS                                          ^Index^
 ────────────────────────────────────────────────────────────

 Here you define various parameters  directly affecting IMAIL
 TOSS.
*E
*B 1651,Handle PKTs not for us
 HANDLE PKTS NOT FOR US                                 ^Index^
 ────────────────────────────────────────────────────────────

 This option tells IMAIL how to handle PKTs which are not for
 one of "our" akas. You have the following three options:

   Toss:    TOSS processes these PKTs as if they were
            addressed to you.
   Forward: TOSS moves these PKTs to the Temporary Packet
            Outbound, so they're compressed for their real
            destination by IMCOMP.
   Rename:  TOSS renames to *.BAD.

 Note that  if this  option is  not set  to Forward,  it will
 ...
*P
 HANDLE PKTS NOT FOR US                                 ^Index^
 ────────────────────────────────────────────────────────────
 ...

 become impossible  to route echo mail packets,  because they
 will be processed  by IMAIL,  and the messages will probably
 end up in your Bad Message board.
*E
*B 1652,Check for personal mail
 CHECK FOR PERSONAL MAIL                                ^Index^
 ────────────────────────────────────────────────────────────

 While tossing,  IMAIL has the  capability  to check  whether
 there are new messages for the user  defined  as  sysop.

 You have four options

    None      Disable this feature
    Log       Write a log entry if a message was found
    Netmail   Create a netmail containing the headers of the
              new messages
    Copy      Copy each new message to a special area

 ...
*P
 CHECK FOR PERSONAL MAIL                                ^Index^
 ────────────────────────────────────────────────────────────
 ...

 The last  option  requires  the  special  area  PERSMAIL
 defined in the ^Area Manager^.

 See also: ^Sysop Names^
*E
*B 1653,Delete empty netmails
 DELETE EMPTY NETMAILS                                  ^Index^
 ────────────────────────────────────────────────────────────

 While  extracting  netmails from  inbound PKTs,  IMAIL  TOSS
 checks whether  they are empty  and whether they are for one
 of our akas.  If these criterias meet  and if this option is
 set to yes, TOSS will delete them.
*E
*B 1654,Use Crc file names
 USE CRC FILE NAMES                                     ^Index^
 ────────────────────────────────────────────────────────────

 This switch determines  the way  IMAIL assignes a name for a
 new messagebase. If you specify "No", IMAIL uses the echotag
 to create a  new  messagebase.  The areatag "SYSOPS.GER" may
 result in an filename like "...path\SYSOPSG.xxx".

 Setting this switch to "Yes",  IMAIL will calculate a CRC32-
 checksum over  the areatag  and will  then use  this somehow
 cryptic sum as filename or pathname (in case of *.MSG)  like
 "...path\74EF0AC1.xxx".
*E
*B 1700,System parameters
 SYSTEM PARAMETERS                                      ^Index^
 ────────────────────────────────────────────────────────────

 This menu assigned for various  options  which  control  the
 general behavior of IMAIL.

 Most of the options available are of the "on/off"  type;  in
 other words, specifying 'Y' will enable  the  option,  while
 'N' will disable it.
*E
*B 1701,Multi-tasking/Network
 MULTI-TASKING/NETWORK                                  ^Index^
 ────────────────────────────────────────────────────────────

 If  you  are  running  IMAIL in a  multi-tasking  or network
 environment ( i.e. LAN), then set this to Yes. It will force
 IMAIL  to  make more  checks for  locked  files;  the  IMAIL
 semaphore will only be created if this  flag is enabled.  In
 this case it is either necessary that SHARE.EXE is loaded or
 that the network drivers direct support sharing and locking.
*E
*B 1702,BBS-software used
 BBS-SOFTWARE USED                                      ^Index^
 ────────────────────────────────────────────────────────────

 When updating the  user base  while packing  or  sorting the
 message  base,  IMTHINGS needs  to know  which message  base
 is used by your system or BBS software because Remote Access
 2.xx or  ProBoard 2.xx  use different  structures (but still
 the  same file name).  Select Remote  Access 2.xx  for these
 type of BBS software, other for all others.
*E
*B 1703,Environment
 ENVIRONMENT                                            ^Index^
 ────────────────────────────────────────────────────────────

 By  selecting 'Binkley'  or 'McMail',  IMAIL will create  so
 called  "flow files"  in your outbound directory, containing
 lists of  files which  the mailer  should send.  The Binkley
 mode should  be used for  domain-aware binkley-style mailers
 like

    Xenia
    Bink+

 The McMail mode does not use the information from the domain
 manager as some binkley-style mailers do not support domains.
 ...
*P
 ENVIRONMENT                                            ^Index^
 ────────────────────────────────────────────────────────────
 ...

 At the moment, this are

    McMail
    Portal of Power

 By  selecting  'FrontDoor'  or  'Intermail',  IMAIL  creates
 attach netmails for the  arcmail bundles.  The FrontDoor and
 Intermail  mode differ because  FrontDoor and  Intermail use
 different naming shemes to generate the  busy-flags in multi
 line environments. This method can be used for other mailers
 which use file attach messages rather than "flow files".
 ...
*P
 ENVIRONMENT                                            ^Index^
 ────────────────────────────────────────────────────────────
 ...

 This setting  will  also control the  style of the IMAIL log
 file  and  moreover the  multitasking of  IMAIL. Check  your
 mailer documentation for details.

 See also: ^Multi-Tasking/Network^
*E
*B 1704,Swap Options
 SWAP OPTIONS                                           ^Index^
 ────────────────────────────────────────────────────────────

 Before calling any external programs, IMAIL  and IMPACK will
 swap most of themselves out of memory, to leave room for the
 program called. Once the  program has completed,  IMAIL ( or
 IMPACK) will be reloaded into memory and continue execution.

 EMS - Expanded Memory (EMS).  If you specify EMS, IMAIL will
       try to allocate a  certain number  of EMS pages to try
       to swap  itself into.  If this fails,  it will swap to
       disk. (Note:  You will need  a custom driver to access
       your hardware  EMS or  a memory  manager to emulate it
       from XMS (such as EMM386.EXE or QEMM)).

 ...
*P
 SWAP OPTIONS                                           ^Index^
 ────────────────────────────────────────────────────────────
 ...

 XMS - Extended memory.  If you  specify this  option,  IMAIL
       will try to swap to extended memory. If this fails, it
       will swap to disk. (Note: You will  need a driver such
       as HIMEM.SYS in order for it to work.)

 EMS & This  indicates  that IMAIL  should try  both EMS  and
 XMS   extended memory, in that order. If both fail, swapping
       to disk will occur.

 Disk  IMAIL  will  swap its  overlay  buffers  to disk  when
       needed.  This is  the default, and also the slowest of
       the options.
*E
*B 1705,Direct screen-writing
 DIRECT SCREEN-WRITING                                  ^Index^
 ────────────────────────────────────────────────────────────

 If set to Yes,  IMAIL writes  direct to  the  screen memory,
 otherwise the (slower) BIOS functions are used.  Set this to
 'N' if you experience problems or to eliminate CGA-"snow".
*E
*B 1706,Close graphic window
 CLOSE GRAPHIC WINDOW                                   ^Index^
 ────────────────────────────────────────────────────────────

 With this switch, you control the  behaviour of  the graphic
 status window whenever IMAIL or IMTHINGS terminate. When you
 set it to yes,  the window will close and the screen will be
 cleared, otherwise the screen will remain.
*E
*B 1707,Setup Password
 SETUP PASSWORD                                         ^Index^
 ────────────────────────────────────────────────────────────

 Here  you  can  define a password  to  prevent  unauthorized
 access to IMSETUP.  The defined  password is  asked whenever
 IMSETUP is  started and  access is  denied when  the correct
 password cannot be entered.  You also need the password when
 you want to disable the password check again.
*E
*B 1708,Sysop Name
 SYSOP NAME                                             ^Index^
 ────────────────────────────────────────────────────────────

 This field  is  required,  as it  is used by IMAIL  for  the
 generation  of  automatic  messages and  so on.  IMAIL  also
 uses it to validate your registration key.

 Your ID-card will help you filling out this field, but check
 it with a mirror...
*E
*B 1709,Default Origin
 DEFAULT ORIGIN                                         ^Index^
 ────────────────────────────────────────────────────────────

 This is the Origin line which  IMAIL will use if one or more
 of your areas have no Origin line defined. You can define an
 own Origin line for each area in the ^Area Manager^.
*E
*B 1710,Before Toss
 BEFORE TOSS                                            ^Index^
 ────────────────────────────────────────────────────────────

 This  option was  included to  allow sysops  to run a  "mail
 mangler" on extracted packets before  IMAIL  processes them.
 If you wish to use this feature, then specify  the full path
 name of the executable program here, including arguments. If
 you need to give the name  of the PKT file,  then place a %P
 on the command line. For example:

 MY_PROG.EXE %P /ZAP

 The %P will expand to the name of the packet file. Note that
 the program called MUST NOT delete the  packet file!

 ...
*P
 BEFORE TOSS                                            ^Index^
 ────────────────────────────────────────────────────────────
 ...

 If you specify  a batch file as  Before Toss command,  IMAIL
 will automatically  call the command  processor by using the
 environment  variable COMSPEC ( or COMMAND.COM if COMSPEC is
 undefined).
*E
*B 1711,Before Toss II
 BEFORE TOSS II                                         ^Index^
 ────────────────────────────────────────────────────────────

 Unlike 'Before Toss',  this  program  will only  be executed
 ONCE after  IMAIL unpacked  the mailbundles.  It is designed
 designed for  programs like  PKTSORT, which  are only called
 once before tossing.  TOSS switches to the temporary inbound
 packet directory before calling the program defined here.

 See ^Before Toss^
*E
*B 1712,Quiet Packers
 QUIET PACKERS                                          ^Index^
 ────────────────────────────────────────────────────────────

 When you  enable this switch,  IMAIL will pipe the output of
 the  compression  and  decompression  programs to NUL.  This
 works for every  program writing  to stdout,  programs using
 direct screen write cannot be piped.
*E
*B 1750,Dupe settings
 DUPE SETTINGS                                          ^Index^
 ────────────────────────────────────────────────────────────

 This menus allows to  define the basic handling of the IMAIL
 dupe detection while tossing echomail, detection by

    - Crc over header and/or MSGID
    - Dupe ring checking (SEEN-BYs)
    - Circular path detection (PATH)
*E
*B 1751,Number of Dupe Records
 NUMBER OF DUPE RECORDS                                 ^Index^
 ────────────────────────────────────────────────────────────

 This field indicates how  many dupe  records IMAIL will save
 in the file  IMAIL.DP  for dupe  checking.  You can  enter a
 value  between  0 and  999.999,  but  IMAIL  will  slow down
 noticeably if set higher than  130.000. If the number is set
 to zero, no dupe checking  will be performed; this will make
 IMAIL faster, but certainly less secure.
*E
*B 1752,Dupe Ring Handling
 DUPE RING HANDLING                                     ^Index^
 ────────────────────────────────────────────────────────────

 This option  tells IMAIL how  to handle  echo mail if one of
 the downlinks  is already  listed in  the  SEEN-BYs  of this
 mail. You have four options:

    None         Disable this check.
    Copy         Copy the message to the dupe area.
    Kill         Do not export to this downlink.
    Copy&Kill    Do not export to this downlink and  copy
                 the message to the dupe area.
*E
*B 1753,Circular Path Detection
 CIRCULAR PATH DETECTION                                ^Index^
 ────────────────────────────────────────────────────────────

 Here you can specify whether  IMAIL  should  check  also the
 PATH lines of  each message for  circular paths.  IMAIL then
 searches the PATH line for your origin address in this echo.
 If it finds your origin address,  it also checks whether the
 system before  and after your  address can  be found  in the
 export list  of this echo.  If this is the case,  a circular
 path has been detected. You have the following four options:

    None         Disable this check.
    Copy         Copy the message to the dupe area.
    Kill         Do not export to this downlink.
    Copy&Kill    Option 'Copy' and 'Kill' together.
*E
*B 1800,Miscellaneous
 MISCELLANEOUS                                          ^Index^
 ────────────────────────────────────────────────────────────

 This menu contains the miscellaneous settings for IMAIL.

 Usually, you can leave things as they  are,  but  READ  this
 section to know what IMAIL is capable of.
*E
*B 1801,ARCmail 0.6 Compatibility
 ARCMAIL 0.6 COMPATIBILITY                              ^Index^
 ────────────────────────────────────────────────────────────

 If this option is set, IMAIL  will generate  compressed mail
 bundles that conform  to  the  ARCmail  0.6  naming standard
 when sending to systems marked in the ^Node Manager^ as "Stone
 Age", or to systems not listed in  the ^Node Manager^. Systems
 listed as "Type 2+" will have a special naming scheme.

 If this is set to "No",  then  IMAIL will always use its own
 internal method for the naming of outbound compressed files.
 When generating ARCmail  for point addresses, IMAIL =always=
 uses its own scheme.
*E
*B 1802,Kill Dead handling
 KILL DEAD HANDLING                                     ^Index^
 ────────────────────────────────────────────────────────────

 This field controls  how to handle  "dead" areas, i.e. areas
 that didn't carry mails for a defined amount of time.

    None         The kill dead function will be disabled.
    Forward      Only  areas  with  a   pending   #forward
                 request will be deleted.
    All          All areas will be processed.

 Kill Dead  will also  only work,  if the number of kill dead
 days (configureable  for each  area in  the ^Area Manager^) is
 not zero. Otherwise the area remains untouched.
*E
*B 1803,Handle sent ARCmail
 HANDLE SENT ARCMAIL                                    ^Index^
 ────────────────────────────────────────────────────────────

 When  ARCmail is sent  by your  mailer,  the file is usually
 'Truncate'd (= its length is set to zero). This allows IMAIL
 to avoid  using the  same  filename  twice which  can  cause
 conflicts when calling the system again and the mail was not
 processed as some mailers do not rename duplicate files.  So
 IMCOMP uses  a different  file  name  if it  processes  more
 outbound  mail for  the same system.  If for any  reason you
 want the mailer to delete the file instead of truncating it,
 set this option to 'Delete'.

        ! However, it is NOT suggested to do this !
        !   Use   this   option   with   caution  !
*E
*B 1804,Send Return Receipt
 SEND RETURN RECEIPT                                    ^Index^
 ────────────────────────────────────────────────────────────

 If a net  mail messages  arrives with  the  "Request  Return
 Receipt" flag  set,  IMAIL  will  automatically   generate a
 net mail message to the originating system, stating that the
 message  arrived.  If a file  named IMAIL.CFM  exists in the
 IMAIL home directory, this file will be appended to the msg.

 Note that the FLAGS RRQ kludge is not  supported by IMAIL in
 the current version. Since the message attribute is defined,
 I decided to support it.
*E
*B 1805,Add Via Lines
 ADD VIA LINES                                          ^Index^
 ────────────────────────────────────────────────────────────

 Registered users of IMAIL may disable the insertion of a Via
 kludge in forwarded net mail by setting this option to:

    Export   Via lines added by IMPACK when pack-routing
             netmail,
    Import   VIA lines added by IMAIL TOSS when netmail is
             found in inbound mail-bundles,
    Always   Import and Export enabled (see above),
    None     Via lines are NOT added.
*E
*B 1806,Use FTSC product names
 USE FTSC PRODUCT NAMES                                 ^Index^
 ────────────────────────────────────────────────────────────

 This options controls whether or not IMAIL TOSS will display
 product names when  processing inbound  packets  of mail. If
 enabled,  TOSS will  show the  name of the  program  used to
 create the  PKT file;  otherwise,  it will simply  show  the
 program's product code.

 In order  to use  this  option,  you must have a file called
 FTSCPROD.??? available in the IMAIL home directory; if found
 IMAIL will compile this file into IMAIL.PR ( after which you
 may  remove  the  FTSCPROD.???  file).  If the  file  is not

 ...
*P
 USE FTSC PRODUCT NAMES                                 ^Index^
 ────────────────────────────────────────────────────────────
 ...

 available  for compilation,  IMAIL will behave as if you had
 set this option to No.

 The  newest  version  of  the  FTSC  product  code  list  is
 distributed  by the  FidoNet  Standard  Committee, it can be
 requested at many systems (FTSCPROD.A??).
*E
*B 1807,Delete Squish/Msg/Jam-bases
 DELETE SQUISH/MSG/JAM-BASES                            ^Index^
 ────────────────────────────────────────────────────────────

 When automatically deleting Squish,  Msg or Jam areas, IMAIL
 can also  delete the  message  bases of these  areas  if you
 specify Yes. This frees the harddisk of 'forgotten' areas.
*E
*B 1808,Deadlink days
 DEADLINK DAYS                                          ^Index^
 ────────────────────────────────────────────────────────────

 If a (forward-)requested area is dead for the specified days
 IMAIL suspects the  link to have failed.  This situation (an
 area has  been unlinked by  the uplink  due to  an error) is
 called 'deadlink'.

 IMAIL then  tries to  reattach that area  from every  system
 being in the linked systems list and in the ^Forward Manager^.

 If you enter a zero, IMAIL will ignore a detected deadlink.
*E
*B 1850,NodeMgr Defaults
 NODEMGR DEFAULTS                                       ^Index^
 ────────────────────────────────────────────────────────────

 Here you define several defaults for the ^Node Manager^ which
 are  used when  you enter  new systems and when mail has to
 handled for systems not defined in the ^Node Manager^.
*E
*B 1851,Max. Packet Size
 MAX. PACKET SIZE                                       ^Index^
 ────────────────────────────────────────────────────────────

 With this option, you can specify the  maximum  size  of the
 packet files (*.PKT) that  IMAIL  will  create.  Use this if
 your up and/or down  links  are  short  on  disk space.

 The number should indicate a size  in  kilobytes.  If a zero
 (0) is specified, there will be no limit imposed.
*E
*B 1852,Max. Arcmail Size
 MAX. ARCMAIL SIZE                                      ^Index^
 ────────────────────────────────────────────────────────────

 Setting this to a  non-zero  value tells  IMCOMP  not to add
 further arcmail PKTs to a  compressed  ARCmail bundle if its
 size is bigger  than  specified ( in kB).  IMCOMP  will then
 create a  new bundle. Using  this feature you  can limit the
 size of the arcmail  bundles and therefore reducing the time
 which is  needed to transfer the bundle  again  if a session
 was interrupted.
*E
*B 1853,Nr. of PKTs to pack per call
 NR. OF PKTS TO PACK PER CALL                           ^Index^
 ────────────────────────────────────────────────────────────

 Here you can define how many PKTs should be packed  with one
 call of a compression program when IMAIL compresses the out-
 going PKTs into  arcmail  bundles.  If you set this value to
 zero, all PKTs for  the destination node  are  packed in one
 packer call.
*E
*B 1854,Default Message Status
 DEFAULT MESSAGE STATUS                                 ^Index^
 ────────────────────────────────────────────────────────────

 This  switch  controls the  default status  of messages from
 IMALNK or IMTHINGS have created to your links. It may be:

        Normal              No Status
        Hold                Hold message for pick up
        Crash               Send message 'crash'
        Direct              Send message directly
        Immediate           Set the 'Immediate' flag

 See also: ^Default Attach Status^
*E
*B 1855,Default Attach Status
 DEFAULT ATTACH STATUS                                  ^Index^
 ────────────────────────────────────────────────────────────

 With  this  switch,  you  control  the default status of the
 attaches for the ARCmail-bundles to your links. It may be:

        Normal              No Status
        Hold                Hold message for pick up
        Crash               Send message 'crash'
        Direct              Send message directly
        Immediate           Set the 'Immediate' flag

 See also: ^Default Message Status^
*E
*B 1900,Log Options
 LOG OPTIONS                                            ^Index^
 ────────────────────────────────────────────────────────────

 In this menu you define what actions IMAIL will report/write
 into the IMAIL Logfile.

 See also: ^! Fatal errors^            ^? Other errors^
           ^$ Accounting info^         ^* Sent/Rcvd files^
           ^+ Brief messages^          ^- Trivial messages^
           ^: Transaction info^        ^# Password errors^
           ^~ Security/Dupe info^      ^/ Spawning info^

           ^Debug logging^             ^IMAIL Log File Name^
*E
*B 1901,! Fatal errors
 FATAL ERRORS ('!')                                     ^Index^
 ────────────────────────────────────────────────────────────

 Every  error  that  causes  IMAIL  to abort  or is nearly as
 severe is logged behind a '!'.  Examples  are  low memory or
 user break.

 This errors also lead to an ERRORLEVEL.

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1902,? Other errors
 OTHER ERRORS ('?')                                     ^Index^
 ────────────────────────────────────────────────────────────

 If IMAIL  encounters  a less severe error,  it will log this
 under  "Other errors".  Locked or  unaccessible message base
 files are  some examples.  If IMCOMP may  not compress  PKTs
 because of a running session wth this system, this will also
 be logged with a '?'.

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1903,$ Accounting info
 ACCOUNTING INFO ('$')                                  ^Index^
 ────────────────────────────────────────────────────────────

 The  dollar sign will  preceed the  statistical  information
 IMAIL  gives:  Messages per  secound  in  and  out,  deleted
 messages,  total size of inbound  and outbound  messages and
 overall runtime.

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1904,* Sent/Rcvd files
 SENT/RCVD FILES ('*')                                  ^Index^
 ────────────────────────────────────────────────────────────

 When this  switch  is set to  'Y',  IMAIL logs  the names of
 inbound and outbound PKTs  and their compressed/uncompressed
 size along with their addresses and origin.

 This  category also includes  creating  or updating  of file
 attaches.

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1905,+ Brief messages
 BRIEF MESSAGES ('+')                                   ^Index^
 ────────────────────────────────────────────────────────────

 These short notes are mostly created by IMALNK when creating
 or deleting an area, linking or unlinking a node.

 If an area  has no defined  PATH,  IMAIL will log  this in a
 brief message, too.

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1906,- Trivial messages
 TRIVIAL MESSAGES ('-')                                 ^Index^
 ────────────────────────────────────────────────────────────

 The free  diskspace and  the allocated  internal buffer size
 will  be logged  as well  as every  message scanned  out  by
 IMAIL SCAN.

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1907,: Transaction info
 TRANSACTION INFO (':')                                 ^Index^
 ────────────────────────────────────────────────────────────

 Here you  can switch  on the  logentries which  show traffic
 information (number of msgs, number of dupes, etc).

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1908,# Password errors
 PASSWORD ERRORS ('#')                                  ^Index^
 ────────────────────────────────────────────────────────────

 This one is quite simple for a change. IMAIL will simply log
 when it encounteres any kind of PKT password errors.

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1909,~ Security/Dupe info
 SECURITY/DUPE INFO ('~')                               ^Index^
 ────────────────────────────────────────────────────────────

 If a message is  considered  DUPE or BAD, IMAIL will log the
 number of the message  during this run of toss,  the areatag
 and the string "Duplicate" or "Security violation".

 If you  check your  DUPES and  BADMAIL folders reagulary and
 tend to ignore your logfile, you may well turn off this
 option.

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1910,/ Spawning info
 SPAWNING INFO ('/')                                    ^Index^
 ────────────────────────────────────────────────────────────

 If an  external program ( e.g. a compression program)  exits
 with an errorlevel and the complete commandline.

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1911,DEBUG Logging
 DEBUG LOGGING                                          ^Index^
 ────────────────────────────────────────────────────────────

 This switch  enable all log options.  This switch  will help
 to find any errors while runing IMAIL.

 When set  to 'Y',  IMAIL TOSS will  log the number of tossed
 mails in this run,  the areatag of this message and the type
 of message base for EVERY mail!

 Beware  of this  option,  your log  file may  well grow into
 sizes never imagined... :-)

 See also: ^Log Options^               ^IMAIL Log File Name^
*E
*B 1950,Space settings
 SPACE SETTINGS                                         ^Index^
 ────────────────────────────────────────────────────────────

 This menu  allows you to  define  all parameters  related to
 message size and disk space management.
*E
*B 1951,Max. Message Size
 MAX. MESSAGE SIZE                                      ^Index^
 ────────────────────────────────────────────────────────────

 Here you can  specify the  maximum message  size of messages
 generated by IMAIL.  The value entered here should be around
 10-15 kB.  If it  is too small,  IMAIL will produce  lots of
 mails and if it is too high,  some mail processors  will get
 trouble  with  these  mails.  This is of  course  a  way  of
 convincing downlinks to  switch to IMAIL,  but it is not the
 kindest way possible. ;-)

 Currently this value is only used by IMALNK and  by IMTHINGS
 POST.
*E
*B 1952,Single Bundle Extract
 SINGLE BUNDLE EXTRACT                                  ^Index^
 ────────────────────────────────────────────────────────────

 When enabled,  IMAIL will  extract the  packets  in a single
 compressed  file  before  processing,  but it  will  extract
 ALL the packets.

 Use this only  when  diskspace  is really tight,  because it
 will really slow down the tossing process. TOSS  has to stop
 its  work and  call the  decompressing  programm  for  every
 ARCmail bundle.
*E
*B 1953,Max. nr. of files/directory
 MAX. NR. OF FILES/DIRECTORY                            ^Index^
 ────────────────────────────────────────────────────────────

 A major  problem of  DOS is that it becomes slower  with the
 number of files per  directory. In a direcory with more than
 1000 files,  the deletion of a single file can take  up to 3
 seconds.

 To work around  this behavior,  you  can  specify  a maximum
 number of  files IMAIL  should create per directory. You can
 enter values 0 and 50-999.  With 0, the number of files will
 be ignored.  Below  50,  this feature  is useless  and above
 999, it will make no diffrence... :-)


 ...
*P
 MAX. NR. OF FILES/DIRECTORY                            ^Index^
 ────────────────────────────────────────────────────────────
 ...

 This only affects the (auto-)creation of Squish or Jam Areas
 by IMAIL or IMALNK and the path / filename suggestion in the
 ^Area Manager^.

 IMAIL will check  the number of  files in the  directory the
 new  area  should  be  created  in  according  to the  group
 manager.  If the number of existing files exceeds  the value
 given here,  IMAIL will create a new directory with the same
 name stem and an ascending extension.


 ...
*P
 MAX. NR. OF FILES/DIRECTORY                            ^Index^
 ────────────────────────────────────────────────────────────
 ...

 Example:

 If the new  area should be created in  '...\FIDO'  and  this
 directory is 'full', a new directory  '...\FIDO.001' will be
 created.   If  it  already   exists  and   also  is  'full',
 '...\FIDO.002'  will be tried,  until  a directory  is found
 which has less than the specified number of files.
*E
*B 1954,Compress after each Packet
 COMPRESS AFTER EACH PACKET                             ^Index^
 ────────────────────────────────────────────────────────────

 This option  lets  IMAIL  calling the  compression  function
 whenever a packet has been  processed and  there is outgoing
 mail waiting  in the  Temp Outbound.  Also,  the option 'Max
 ARCmail size' will be executed more precisely.

 But there is another side  to the coin: This option takes up
 a great deal of time.  Really lots of time. A disturbing lot
 of  time.  So use  it only  on systems  where disk  space is
 tight,  because it  will  slow  down  the  execution  of the
 program noticeably.
*E
*B 1955,Diskspace before Unpack
 DISKSPACE BEFORE UNPACK                                ^Index^
 ────────────────────────────────────────────────────────────

 This is a kind of emergency break. If you received more mail
 than your remaining harddisk space  can  accomodate when un-
 packed, you can  prevent the  TOSS operation.  This prevents
 loss of mail due to  harddisk overflow.  Specify the size in
 MB, disable the test by entering zero.
*E
*B 1956,Diskspace before Toss
 DISKSPACE BEFORE TOSS                                  ^Index^
 ────────────────────────────────────────────────────────────

 Together  with the  previous setting,  you can  handle tight
 diskspace intelligently and automatically.  Depending on the
 ratio of  received to  exported mail,  you can determine the
 space TOSS usually needs to distribute mails.

 It has to be enough to toss one packet,  but needs not to be
 enough  to  toss  all  the  mail.  It should  be lower  than
 "Diskspace before Unpack" minus unpacked mail. Otherwise you
 may end with a a lot of *.pkt and Imail will not toss them.


 ...
*P
 DISKSPACE BEFORE TOSS                                  ^Index^
 ────────────────────────────────────────────────────────────
 ...

 An example:  Your average  amount  of imported mail is  2000
 messages per day that need some 3MB space when unpacked. So,
 you set 'Diskspace before Unpack' to  3. TOSS  then creates,
 say 5000 messages to your downlinks (so  you have an import/
 export  ratio  of 1:2.5).  In  this  example,  it  would  be
 advisable to set this field to  8MB, this way getting things
 straight  for  =average=  dayly  operation.  If you  want to
 disable this check, set this field to zero.
*E
*B 1957,Diskspace before Compress
 DISKSPACE BEFORE COMPRESS                              ^Index^
 ────────────────────────────────────────────────────────────

 This  field  controls  how  much  diskspace  is required for
 IMCOMP to work.  Below this amount,  IMCOMP will  not run at
 all, it has no influence on TOSS.
*E
*B 1958,Use IMCOMP if less disk-space
 USE IMCOMP IF LESS DISK-SPACE                          ^Index^
 ────────────────────────────────────────────────────────────

 When IMAIL or IMPACK run into problems with diskspace ( even
 with the values that control diskspace), you can specify 'Y'
 here,  so IMCOMP will be called immediately  to compress the
 waiting PKTs in order to gain diskspace.

 When  this switch is set to 'No',  or the call of IMCOMP did
 not release  enough diskspace,  IMAIL and  IMPACK will abort
 immediately.

 This switch is especially useful if your harddisk for  'Temp
 outbound  Packets'  is different  from  your  'Outbound  Net
 Files' - directory.
*E
*B 1959,Stop TOSS after x msgs
 STOP TOSS AFTER X MSGS                                 ^Index^
 ────────────────────────────────────────────────────────────

 This value  is one of two kinds of emergency break for IMAIL
 and is intended to protect against mailbombs.

 When  tossing,  IMAIL  will  count  the  overall  number  of
 messages  proccessed  in all  PKTs during this call.  If the
 latter number is exceeded, the PKT is considered a mailbomb.
 The PKT will be renamed and IMAIL will abort.

 If the overall  number of mails ( both echomail and netmail)
 exceeds the first value,  IMAIL  will  create  the semaphore
 IMAIL.NRM and abort.

 See also: ^Stop TOSS after x netmails^
*E
*B 1960,Stop TOSS after x netmails
 STOP TOSS AFTER X NETMAILS                             ^Index^
 ────────────────────────────────────────────────────────────

 This value  is one of two kinds of emergency break for IMAIL
 and is intended to protect against mailbombs.

 When  tossing,  IMAIL  will  count  the  overall  number  of
 netmails  proccessed  in all  PKTs during this call.  If the
 latter number is exceeded, the PKT is considered a mailbomb.
 The PKT will be renamed and IMAIL will abort.

 If the overall  number of mails ( both echomail and netmail)
 exceeds the first value,  IMAIL  will  create  the semaphore
 IMAIL.NRM and abort.
         
 See also: ^Stop TOSS after x msgs^
*E
*B 200,Archive programs
 ARCHIVE PROGRAMS                                       ^Index^
 ────────────────────────────────────────────────────────────

 Here you define all Archive programs with all parameters for
 compressing/decompressing the outbound/inbound mail packets.

 See also: ^Compression Defaults^    ^Compression Programs^
           ^Decompression Defaults^  ^Decompression Programs^
*E
*B 2000,Compression programs
 COMPRESSION PROGRAMS                                   ^Index^
 ────────────────────────────────────────────────────────────

 In this section,  you may specify  the programs,  along with
 their  parameters,  to  use  in  the  creation  of  outbound
 compressed mail. Also a short name for each program is asked
 which  is  used  by IMALNK (remote change of compression).

 When  you run  IMSETUP  for the  first time,  it  will  show
 defaults for the following programs:

 ARC, Arj, LHarc, PKARC, PAK, PKZip, Rar, Sqz, Uc2 and Zoo.

 If you wish, you may add  other programs of your own choice,

 ...
*P
 COMPRESSION PROGRAMS                                   ^Index^
 ────────────────────────────────────────────────────────────
 ...

 but do not leave any entries  empty. Instead, if you do  not
 intend  to use  one ( or more) of the  predefined  programs,
 replace it with one that you do use.

 All of the programs you intend  to use must be present some-
 where in the DOS path,  because  IMSETUP does not allow  the
 input of pathnames.

 You will then select which of these programs to use for mail
 compression  on  a per-system  basis,  in  the  Node  Export

 ...
*P
 COMPRESSION PROGRAMS                                   ^Index^
 ────────────────────────────────────────────────────────────
 ...

 Manager. If IMAIL needs to  compress  mail for a  system not
 listed, it will use the first of those given in this menu.

 See also: ^Compression Defaults^    ^Decompression Programs^
*E
*B 2001,Compression defaults
 COMPRESSION DEFAULTS                                   ^Index^
 ────────────────────────────────────────────────────────────

 Arc.Exe        mw
 Arj.Exe        m -c -e+ -y -i -jm
 Lha.Exe        m /m2n1t1
 Pak.Exe        m /WN /ST /P
 PkArc.Exe      -ot m
 PkZip.Exe      -m- -~ -ex -o
 Rar.Exe        mf -m5 -ep1 -s -c -std -tl -cfg-
 Sqz.Exe        aM /p3
 Uc.Exe         A -F
 Zoo.Exe        aMPh:

 See also: ^Compression Programs^    ^Decompression Defaults^
           ^Decompression Programs^
*E
*B 3000,Decompression programs
 DECOMPRESSION PROGRAMS                                 ^Index^
 ────────────────────────────────────────────────────────────

 IMAIL automatically recognizes  compressed files produced by
 the following programs:

 ARC, Arj, LHarc, PKARC, PAK, PKZip, Rar, Sqz, Uc2 and Zoo.

 In this menu,  you may change the  name and parameters which
 will be executed when compressed mail files  are identified.

 It is also  possible  to define  a program  which  should be
 invoked  if  IMAIL  is not  able  to determine  the  type of
 compression used to create an ARCmail file. If this entry is

 ...
*P
 ...                                                    ^Index^
 ────────────────────────────────────────────────────────────

 not defined,  IMAIL will simply ignore the file.

 Be  VERY  careful when  changing these items,  for a mistake
 might produce very unexpected ( and often unwanted) results.
 Certainly do  NOT try to use one program instead of another.
 A compressed file  identified as have been created by LHarc,
 for example, cannot be decompressed by ARC! ( crazed idea of
 some dudes...)

 If  possible,  have  =all=  of  the  decompression  programs
 somewhere in the DOS path, unless you are absolutely certain

 ...
*P
 ...                                                    ^Index^
 ────────────────────────────────────────────────────────────

 that you will not be getting  mail compressed by one or more
 of  them ( and who  can be  =absolutely=  sure  of  anything
 nowadays???).

 See also: ^Decompression Defaults^  ^Compression Programs^
*E
*B 3001,Decompression defaults
 DECOMPRESSION DEFAULTS                                 ^Index^
 ────────────────────────────────────────────────────────────

 Arc.Exe        xw
 Arj.Exe        e -c -i -y
 Lha.Exe        e /c1m2n1
 Pak.Exe        e /WA
 PKUnZip.Exe    -ed -o
 PkXArc.Exe     -r
 Rar.Exe        e -o+ -y -ep1 -cfg- -std
 SQZ            e -o1
 Uc.Exe         E -F
 Zoo.Exe        eO

 See also: ^Compression Programs^    ^Compression Defaults^
           ^Decompression Programs^
*E
*B 400,Area Manager
 AREA MANAGER                                           ^Index^
 ────────────────────────────────────────────────────────────

 The Area Manager is one of the  most  important parts of the
 program, and also controls most of what IMAIL does.

 When you first run IMSETUP, no message areas are defined.You
 will see a screen with many  different fields,  all empty or
 set to certain default values.

 The Area Manager has two modi operandi: A BROWSE mode and an
 EDIT mode.

 When you  are in the  BROWSE mode,  you can jump between the

 ...
*P
 AREA MANAGER                                           ^Index^
 ────────────────────────────────────────────────────────────
 ...

 area records and use some function keys.

 The EDIT mode is just for editing a single record.

 The  mode is  displayed  in the  upper  left  corner  of the
 Manager Window.

 When  displaying  the area record, you will find some status
 information given in  square  brackets at the  bottom of the
 record window. These are:

 ...
*P
 AREA MANAGER                                           ^Index^
 ────────────────────────────────────────────────────────────
 ...

 [Fwd Req pendig]
        This flag indicates that this area has been requested
        automatically  from your  uplink due  to a request of
        one of your downlinks ( forward request), but no mail
        has arrived yet.

 [Dead: nnn]
        With this  flag,  IMSETUP informs you that  there has
        been no traffic in this area for 'nnn' days.


 ...
*P
 AREA MANAGER                                           ^Index^
 ────────────────────────────────────────────────────────────
 ...

 [Deadlink]
        This message will occur if the area has been dead for
        the days specified in  the area record  and IMAIL has
        tried to revive the  area by sending a request to the
        uplink.

 [Unlinked]
        When this status message is displayed,  this area has
        been unlinked automatically from your uplink, because
        there  were  no  systems  (downlinks)  this area  was

 ...
*P
 AREA MANAGER                                           ^Index^
 ────────────────────────────────────────────────────────────
 ...
        exported  to or  because  it was  'dead' for too many
        days.

 [Auto-Added]
        This  flag  also  informs   you  about  an  automatic
        measure:  This area  has been  created automatically.
        This could  be the result  of a forward  request or a
        remote creation.
                        
 See also: ^Area Manager Keylist^
*E
*B 4000,Area Manager Keylist
 AREA MANAGER KEYLIST                                   ^Index^
 ────────────────────────────────────────────────────────────

 BROWSE mode keys:

 <ENTER>          Edit           <F1>           Help
 <SH><F1>         Show Keys      <F2>           Find Record
 <F3>             Global         <F4>           List Records
 <F5>             Copy Record    <SH><F7>       Statistic
 <ESC>/<F10>      Exit           <INS>          Add Record
 <CTRL-A>/<ALT-A> jump AutoAdd   <DEL>          Delete Record
 <CTRL-U>/<ALT-U> jump Unlinked  <HOME>         First Record
 <CTRL-D>/<ALT-D> jump Dead      <END>          Last Record
 <CTRL-F>/<ALT-F> jump FwdReq    <PGUP>/<PGDN>  Prev/Next
 ...
*P
 AREA MANAGER KEYLIST                                   ^Index^
 ────────────────────────────────────────────────────────────
 ...

 EDIT mode keys:

 <>/<>/<>/<> \              <ENTER>         Change/Edit
 <PGUP>/<PGDN>    Move Bar      <ESC>           Abort
 <TAB>/<SH><TAB> /              <F1>            Help
                                <F10>           Save
                                
 See also: ^Area Manager^
*E
*B 4101,Areatag
 AREATAG                                                ^Index^
 ────────────────────────────────────────────────────────────

 This is the name of the message area, sometimes called "Area
 Tag".  The name may be up to 50 characters long;  it will be
 forced into  upper case.  You may use all characters for it,
 except  control characters  and the wildcards  '*', '?', '['
 and ']'. For the first character of an areatag, you may also
 not use '-', '+', '&', '~', '#', '%' and '='.

 Please be sure of the spelling of the name, since it is used
 to  identify  into which  area (board or  path) an  incoming
 message should be tossed.

 See also: ^Area Manager Keylist^
*E
*B 4102,Comment
 COMMENT                                                ^Index^
 ────────────────────────────────────────────────────────────

 Here you  may enter  a brief  description of the  area. This
 description is used by AreaLink when generating lists of the
 areas you  have available,  and may also  help remind you of
 the topic or purpose of the message area.

 Note that  if the area  was  auto-added,  created due  to an
 automatic  creation or  forward request by TOSS or AreaLink,
 the comment will be set to something like

        "Area autoadded by <node> on <date time>"
        "Area received from <node> on <date time>"
        "Area requested from <node> on <date time>"
 ...
*P
 COMMENT                                                ^Index^
 ────────────────────────────────────────────────────────────
 ...

 This way,  you have an  overview of what is going on.  IMAIL
 tries also  to determine  the description  from  the forward
 link request file (if defined).

 This field is optional. Unfortunately, it often will be left
 blank  or set to the entry given by  IMAIL.  This forces the
 downlinks to  guess at the  purpose of an area and puts him/
 her back to "trial and error".

 See also: ^Area Manager Keylist^
*E
*B 4103,Origin Line
 ORIGIN LINE                                            ^Index^
 ────────────────────────────────────────────────────────────

 Here you may specify up to  63 characters which will be used
 as the origin line for the area if it is an echo area.

 To this will be prefixed the string:

       * Origin:

 and your  origin address will be appended.  The total length
 must not exceed 79 characters.

 If you forget to define this field,  the default origin line

 ...
*P
 ORIGIN LINE                                            ^Index^
 ────────────────────────────────────────────────────────────
 ...

 will be used. Note that if the BBS or editor program used to
 write an echo message  already adds an origin line,  the one
 defined here will not be used.

 See also: ^Area Manager Keylist^
*E
*B 4104,Active
 ACTIVE                                                 ^Index^
 ────────────────────────────────────────────────────────────

 This by default is set to 'Y',  which means that the area is
 active. If set to 'N',  IMAIL will behave as if the area had
 not been defined.

 This will allow you to disable an echo area - for any reason
 you may wish - without  having to  actually  delete  it, and
 later re-enter it.

 Unlike unlinked or hidden areas,  inactive areas are ignored
 by AreaLink and cannot accessed by any downlink.

 See also: ^Area Manager Keylist^
*E
*B 4105,Group
 GROUP                                                  ^Index^
 ────────────────────────────────────────────────────────────

 A number between  1 and  255 which  identifies the  group to
 which this  message area belongs.  Groups are used primarily
 by the AreaLink function to indicate which nodes may request
 links to which echo areas, request areas  from which  uplink
 and generally simplifying their automatic handling.

 If the area was auto-added by  TOSS or AreaLink,  this field
 will be set to the group specified in the ^Node Manager^'s New
 Area Group field ( for the node which created the echo),  or
 to that  specified in the  Other Parameters menu.  If it was
 created due to a forward request, it will be assigned to the 
 ...
*P
 GROUP                                                  ^Index^
 ────────────────────────────────────────────────────────────
 ...

 group defined in the Arealink Option's Create Group field or
 to the one in the ^Node Manager^`s New  Area Group field.

 See also: ^Area Manager Keylist^
           ^Group Manager^
*E
*B 4106,Secure
 SECURE                                                 ^Index^
 ────────────────────────────────────────────────────────────

 If enabled, IMAIL will check the address of the system which
 sent the  message  in this area.  If it is among the  export
 nodes  listed in the  Export List,  it will be  imported and
 processed;  otherwise,  it  will  be  tossed  into  your Bad
 Message  Board.  Note  that  the  sender's  address  will be
 determined using the PKT-address,  not the address stated in
 the origin line.

 If this  switch is set to  N,  IMAIL  will  also  ignore the
 export only flag in the list of linked systems.

 See also: ^Area Manager Keylist^
*E
*B 4107,MsgBase
 MSGBASE                                                ^Index^
 ────────────────────────────────────────────────────────────

 This feature allows you to control the msgbase of this area:

 Passthrough, Hudson, Jam, Squish or *.MSG.

 See also: ^Area Manager Keylist^
*E
*B 4108,Type
 TYPE                                                   ^Index^
 ────────────────────────────────────────────────────────────

 In this field,  you will indicate the type of message  area.
 You may specify that an area is:

 Echo, Local or Netmail.

 This way,  you may include  ALL  of your  message  areas  in
 IMSETUP.  For the purpose of handling echo mail,  only those
 areas which are of type Echo will be considered. Local areas
 will be ignored by all IMAIL functions (except of IMTHINGS),
 but will ensure that you do not use a board number twice.
 The special boards BADMAIL, DUPES and PERSMAIL are an excep-

 ...
*P
 TYPE                                                   ^Index^
 ────────────────────────────────────────────────────────────
 ...

 tion to this rule, they are forced to be local by IMSETUP.
 Net mail areas are used by  the IMPORT function of IMTHINGS.

 See also: ^Area Manager Keylist^
*E
*B 4109,Board
 BOARD                                                  ^Index^
 ────────────────────────────────────────────────────────────

 If the area is of type Hudson, then in this field you should
 specify the board number corresponding to the message area.

 The board number  may be between  1 and  200 inclusive ( the
 upper limit is imposed by QuickBBS/RA).

 IMSETUP will  not let you  use the same  board number twice,
 because you would be cross-linking echo areas.  If you press
 F4,  a list of all unused  board numbers will be shown,  and
 you may  move around  using the  cursor keys  and select one
 from it  by pressing  ENTER.  If you are  changing the board

 ...
*P
 BOARD                                                  ^Index^
 ────────────────────────────────────────────────────────────
 ...

 number, the  highlight bar will be placed  on the  currently
 defined  board  number;  ESC will  allow you  to  retain the
 current definition.

 TOSS uses this number  when importing echo  messages,  since
 the   QuickBBS / RemoteAccess   message  bases   contain  no
 indication  of the area name.  Similarly,  SCAN uses this to
 derive the name of an echo area when exporting mail.

 See also: ^Area Manager Keylist^
*E
*B 4110,Path
 PATH                                                   ^Index^
 ────────────────────────────────────────────────────────────

 If the message area is of type *.MSG, JAM or Squish, then in
 this field you should specify the  directory or path name of
 the message base.

 If the area  is of  type *.MSG,  the directory  in which the
 messages will be placed should be specified. For Squish- and
 JAM-type areas, specify the directory and the base file name
 of the area (ie. directory plus file name without extension)

 If you change an Area from Hudson or Passthrough to Squish /
 Jam or MSG,  IMSETUP  will automatically  create a  path and

 ...
*P
 PATH                                                   ^Index^
 ────────────────────────────────────────────────────────────
 ...

 basename according to your settings in the ^Group Manager^ and
 the areatag.  If you have no entries in your  Group Manager,
 IMSETUP will not propose anything.

 If you  change  the area  path manually,  IMSETUP offers the
 possibility to move  the message base to the new path,  thus
 reducing error possibilities.

 See also: ^Area Manager Keylist^
*E
*B 4111,Days
 DAYS                                                   ^Index^
 ────────────────────────────────────────────────────────────

 This  item is  used by  IMTHINGS KILL /U to  determine which
 messages to kill: it will mark as deleted any messages older
 than the  number of  days specified here.  If this  field is
 left at  zero,  no  messages  will  be  killed,  unless  the
 "# Msgs" field below is specified.

 The maximum value which can be entered in this field is 255.
 If the  area is  marked  as  Passthrough,  this field has no
 meaning (kinda obviously).

 See also: ^Area Manager Keylist^
*E
*B 4112,Msgs
 MSGS                                                   ^Index^
 ────────────────────────────────────────────────────────────

 This is  used  by  IMTHINGS KILL /U  to determine  how  many
 messages to leave in  this board.  If this  field is left at
 zero,  it will be ignored,  and no messages will be  killed,
 unless the "# Days" field is specified.

 Naturally,  if the area is  Passthrough,  this field  has no
 meaning.

 See also: ^Area Manager Keylist^
*E
*B 4113,Hidden
 HIDDEN                                                 ^Index^
 ────────────────────────────────────────────────────────────

 Enable this option if this area  should not be  displayed in
 any AreaLink report  of available areas.  Moreover it cannot
 be linked  with a  wildcard request.  It can only  be linked
 when explicitly stating the full areatag.

 See also: ^Area Manager Keylist^
*E
*B 4114,Unlinked
 UNLINKED                                               ^Index^
 ────────────────────────────────────────────────────────────

 Together with  Autounlink,  this  field controls  the unlink
 status  for the  current area.  If this field is set to yes,
 IMAIL has unlinked  this area  after the  last downlink  has
 unlinked  it from your  system and  the remaining  system is
 listed as uplink in the ^Forward Manager^.

 The area  will still  appear in your list of available areas
 and  if a system  requests this area,  IMALNK  automatically
 requests this area from your uplink again.

 See also: ^Area Manager Keylist^
*E
*B 4115,Autounlink
 Autounlink                                             ^Index^
 ────────────────────────────────────────────────────────────

 If this option  is set to 'N'  the unlink check  is disabled
 for this area,  so it will remain linked to your system even
 when it is no more wanted by you or your downlinks.

 See also: ^Area Manager Keylist^
*E
*B 4116,Mandatory
 MANDATORY                                              ^Index^
 ────────────────────────────────────────────────────────────

 If you set this  field to yes,  no downlink can  unlink from
 this area  using the  AreaLink functions.  This can  only be
 done manually. This field is useful when you really  want an
 area to be read.

 See also: ^Area Manager Keylist^
*E
*B 4117,Read only
 READ ONLY                                              ^Index^
 ────────────────────────────────────────────────────────────

 If this option is enabled,  every system  linking  this area
 gets an  export only flag ( which can be removed manually by
 the sysop).  This flag prevents unauthorized  downlinks from
 posting messages in restricted ( read only) areas.

 See also: ^Area Manager Keylist^
*E
*B 4118,Tiny SB
 TINY SB                                                ^Index^
 ────────────────────────────────────────────────────────────

 Enable this  option if  you want  to strip  all the  SEEN-BY
 information from  an  incoming  echo  message  before  it is
 re-exported.

 In this case,  the outgoing  message will  contain  only the
 SEEN-BYs of your downlinks. Note, however,  that if the area
 is not marked  as  passthrough,  and if the Import SB option
 (below) is active,  the message will  be =imported= with the
 original SEEN-BY information.

 See also: ^Area Manager Keylist^
*E
*B 4119,Import SB
 IMPORT SB                                              ^Index^
 ────────────────────────────────────────────────────────────

 This switch controls whether the  SEEN-BYs are imported into
 the message base or whether they are stripped.

 See also: ^Area Manager Keylist^
*E
*B 4121,Kill Dead
 KILL DEAD                                              ^Index^
 ────────────────────────────────────────────────────────────

 IMAIL  allows you  to delete  areas  without traffic after a
 definable number  of days.  During the midnight  maintenance
 IMAIL marks areas without traffic.

 A value  of 0  disables the  function  for  this  area,  the
 maximum number of days is 256.

 Dead  areas are  marked in the  Area Manager,  do not forget
 that this  check is only  done during  midnight  maintenance
 and the Area Manager shows only full days.

 See also: ^Area Manager Keylist^
*E
*B 4120,Hide SB
 HIDE SB                                                ^Index^
 ────────────────────────────────────────────────────────────

 If this switch is  set to Yes,  IMAIL puts a CTRL-A in front
 of every SEEN-BY line.  This is useful for the BBS  software
 which should not display these hidden SEEN-BYs to the normal
 users then.

 See also: ^Area Manager Keylist^
*E

*B 4122,Manual
 MANUAL                                                 ^Index^
 ────────────────────────────────────────────────────────────

 This  switch gives  you the  total control over the links to
 this area.  With this one  set to Yes,  the area is visible,
 but totally unaccessible for IMALNK.

 You can  use this  to ensure  that only adult links read the
 x-rated areas or to establish some  kind of closed-usergroup

 See also: ^Area Manager Keylist^
*E
*B 4123,Zone Gate
 ZONE GATE                                              ^Index^
 ────────────────────────────────────────────────────────────

 This field  is similar  to the  Tiny SB field.  It indicates
 that  IMAIL should strip  all  information from  the SEEN-BY
 line when  exporting to  a system  which is  in a  different
 zone,  except for  your address  and  that  of the downlink.
 Currently, zonegating only works  with ONE node in the other
 zone,  because the new  SEEN-BYs will  only contain your own
 and the destination address.

 Note that  when the  message is imported in your messagebase
 ( if the area is not passthrough) the original SEEN-BY lines
 will be preserved.

 See also: ^Area Manager Keylist^
*E
*B 4124,No PAUSE
 NO %PAUSE                                              ^Index^
 ────────────────────────────────────────────────────────────

 This setting can be  used with important areas.  By default,
 your downlinks can prevent echo mails being exported to them
 using  the %PAUSE  meta-command with Arealink.  If you don`t
 want information in important areas to pass  your downlinks,
 you can inhibit the pausing of an area with this switch.

 See also: ^Area Manager Keylist^
*E
*B 4125,Dupecheck
 DUPECHECK                                              ^Index^
 ────────────────────────────────────────────────────────────

 This switch can be used to advise  IMAIL not to perform dupe
 checking on  an area.  This increases  the  speed of  TOSS a
 little, but increases the risk of dupes noticeably.

 See also: ^Area Manager Keylist^
*E
*B 4126,Dupe MSGID
 DUPE MSGID                                             ^Index^
 ────────────────────────────────────────────────────────────

 IMAIL has two ways of checking for Dupes:

 Either it  calculates the  crc  header  sum or it checks the
 MSGID.  Especially in gated areas,  dupes occur with changed
 headers, but identical MSGID.  For these areas,  you can set
 this switch  to 'Y'.  IMAIL  will then  check  every  single
 incoming  Msg in  this area  against the  MSGID's  stored in
 IMAIL.DP.  Not finding  it there,  the  header crc  will  be
 checked afterwards.

 See also: ^Area Manager Keylist^
*E
*B 4127,Squish Kill
 SQUISH KILL                                            ^Index^
 ────────────────────────────────────────────────────────────

 This switch  controls  whether  or not  IMAIL should use the
 squish  'kill  on  the  fly' - function  on  this  Area.  Of
 course,  this switch will only  affect Areas that are set to
 'Squish'.

 See also: ^Area Manager Keylist^
*E
*B 4128,Read/Write Security
 READ/WRITE SECURITY                                    ^Index^
 ────────────────────────────────────────────────────────────

 These  two  settings  control -  in  addition  to  the group
 characters - who may link to an area  and who  may  write in
 it.

 In the ^Node Manager^,  you  can specify  an  Area  Security
 Level for every system.

 Systems that have a security  level below the value given in
 'Read Sec'  will not  be  able  to  link to  that echo.  For
 systems with  a security level  higher or  equal than  'Read
 Sec',  but lower than  'Write Sec'  the area  will be linked

 ...
*P
 READ/WRITE SECURITY                                    ^Index^
 ────────────────────────────────────────────────────────────
 ...

 'Export Only'.  That means  the system will receive mails in
 that echo,  but messages  sent by  it will  be  tossed  into
 BADMAIL.

 WARNING: This two  settings have no  affect to linked  areas
          that have been linked manualy  in the ^Node Manager^!

 See also: ^Area Manager Keylist^
*E
*B 4129,Read/Write Security
 READ/WRITE SECURITY                                    ^Index^
 ────────────────────────────────────────────────────────────

 These  two  settings  control -  in  addition  to  the group
 characters - who may link to an area  and who  may  write in
 it.

 In the ^Node Manager^,  you  can specify  an  Area  Security
 Level for every system.

 Systems that have a security  level below the value given in
 'Read Sec'  will not  be  able  to  link to  that echo.  For
 systems with  a security level  higher or  equal than  'Read
 Sec',  but lower than  'Write Sec'  the area  will be linked

 ...
*P
 READ/WRITE SECURITY                                    ^Index^
 ────────────────────────────────────────────────────────────
 ...

 'Export Only'.  That means  the system will receive mails in
 that echo,  but messages  sent by  it will  be  tossed  into
 BADMAIL.

 WARNING: This two  settings have no  affect to linked  areas
          that have been linked manualy  in the ^Node Manager^!

 See also: ^Area Manager Keylist^
*E
*B 4130,Area Origin Address
 AREA ORIGIN ADDRESS                                    ^Index^
 ────────────────────────────────────────────────────────────

 Here you can choose the address to use in the origin line of
 the message.
    
 This address  will also be used in the PATH line of the echo
 message, as well as in the list of SEEN-BYs.

 Note that  only the  net and  node numbers will be placed in
 the  SEEN-BYs  and PATH  lines; the  use of  zone and  point
 numbers is not accepted.

 See also: ^Area Manager Keylist^
*E
*B 4131,Area Seen-Bys
 AREA SEEN-BYS                                          ^Index^
 ────────────────────────────────────────────────────────────

 This field pops up a window that allows you to choose one or
 more addresses to add to the SEEN-BY line for that area.
    
 See also: ^Area Manager Keylist^
*E
*B 4132,Area Linked Systems
 AREA LINKED SYSTEMS                                    ^Index^
 ────────────────────────────────────────────────────────────

 Here,  you may  specify up to 200 systems to which this echo
 will be exported.  At least one node must be defined to TOSS
 or SCAN to/from the area.
    
 You can move with  the cursor keys  including PgUp and PgDn,
 edit a single entry with Enter, insert a new entry  with Ins
 and delete an entry with Del.
*E
*B 4133,Rulename
 RULENAME                                               ^Index^
 ────────────────────────────────────────────────────────────

 When  the  IMALNK  area rules  support  is  enabled,  IMALNK
 expects  the file name  of the rule for  the current area in
 this field.  If the field is empty  or if the file cannot be
 found in  the path defined  as Rules Path,  IMALNK will send
 IMNORULE.HEA to the user when linking this area.

 When  sending a  rule file, IMALNK  searches for  IMRULE.HEA
 which is  expected in IMAIL  home  directory and  send it as
 header for the rule file.
*E
*B 4151,System address (link list)
 SYSTEM ADDRESS (LINK LIST)                             ^Index^
 ────────────────────────────────────────────────────────────

 Here you specify the address of a system where msgs of this
 area shall be exported to and/or accepted from.
*E
*B 4152,Sysop name (link list)
 SYSOP NAME (LINK LIST)                                 ^Index^
 ────────────────────────────────────────────────────────────

 By selecting this field, IMSETUP opens a list of all systems
 presently in  your node  database.  You can  select a system
 from your ^Node Manager^ and it will be included in the list
 of linked systems of the current area.
*E
*B 4153,Export only
 EXPORT ONLY                                            ^Index^
 ────────────────────────────────────────────────────────────

 "Export-only" means  that IMAIL  will  export  mail to  this
 system, but will not accept incoming mail, in this area from
 this system. This is only valid for "secured" areas.
*E
*B 4154,Import only
 IMPORT ONLY                                            ^Index^
 ────────────────────────────────────────────────────────────

 "Import-Only" indicates that IMAIL will accept incoming mail
 from the system, but will never export to it.
*E
*B 4155,Paused
 PAUSED                                                 ^Index^
 ────────────────────────────────────────────────────────────

 "Paused"  indicates  that  the  system  is  paused  and does
 neither send nor receive any mail from that echo.
*E
*B 4156,Denied
 DENIED                                                 ^Index^
 ────────────────────────────────────────────────────────────

 "Denied"  indicates that  the system  is neither  allowed to
 send msgs into that area nor to receive msgs from that area.
 It is also not allowed to change or remove that status using
 Arealink.  This feature allows to  prevent single nodes from
 access single  areas independend from  the group or security
 level  configuration and  without  the  need to  switch such
 areas to manual status.
*E
*B 4201,Area Find Record
 AREA FIND RECORD                                       ^Index^
 ────────────────────────────────────────────────────────────

 Pressing <F2> brings up a window in which you may specify an
 area  name.  If the  area  is found,  it will be  displayed.
 Wildcards may be used:  '*' expands to 0 or more characters,
 while '?' will match any single character.

 Note that a wildcard  search is slower than one in which the
 full area name is specified  ( but sometimes typing the name
 can be slower than searching with a wildcard, huh?)

 See also: ^Area Manager^   ^Area Manager Keylist^
*E
*B 4202,Area List Record
 AREA LIST RECORD                                       ^Index^
 ────────────────────────────────────────────────────────────

 The browse function will  allow you to examine a list of all
 the curently defined areas and to move to a specific record.
 The  window  shows some  information  about each  area.  For
 example, it might read:

     TEST_ECHO          Squish   X    AF  D:002
     MYPOINT_ECHO       Jam      X   RA  U

 The first field is the name of the area ( the areatag). This
 is followed  by the  type of  the area  and by  the group it
 belongs to.

 ...
*P
 AREA LIST RECORD                                       ^Index^
 ────────────────────────────────────────────────────────────
 ...

 Autoadded areas are indicated with an 'A' in the Flagcolumn.
 Areas for which a forward request is pending are tagged with
 'F',  unlinked areas with an 'U'.  The areas which have been
 'dead' for some days have an 'D:nnn' in their line, nn being
 the days inactive.  When a deadlink request has been issued,
 an 'R' will occur in the list.

 See also: ^Area Manager^   ^Area Manager Keylist^
*E
*B 4203,Area Flow Statistic
 AREA FLOW STATISTIC                                    ^Index^
 ────────────────────────────────────────────────────────────

 Pressing <SH><F7> pops up a small window which allows you to
 check the curent echomail flow  information for  the current
 area.  And that  is for  today, yesterday,  this week,  last
 week, this month, last month, this year and last year.

 See also: ^Area Manager^   ^Area Manager Keylist^
*E
*B 4500,Global Linked Systems
 GLOBAL LINKED SYSTEMS                                  ^Index^
 ────────────────────────────────────────────────────────────

 Here you can global  add,  delete  or  replace a node in the
 linked system list.

 In  almost  every  case,  the  changes  will  be  made  on a
 per-group basis. One or more groups may be specified and the
 modifications will be made  for all  echo areas which belong
 to the select(ed) group(s).

 See also: ^Global Add Node^        ^Global Delete Node^
           ^Global Replace Node^
*E
*B 4501,Global Add Node
 GLOBAL ADD NODE                                        ^Index^
 ────────────────────────────────────────────────────────────

 With  this  option you can  add a node to the  linked system
 list for a global group of areas.

 See also: ^Global Linked Systems^
*E
*B 4502,Global Delete Node
 GLOBAL DELETE NODE                                     ^Index^
 ────────────────────────────────────────────────────────────

 With  this  option you  can delete  a node  from  the linked
 system list for a global group of areas.

 See also: ^Global Linked Systems^
*E
*B 4503,Global Replace Node
 GLOBAL REPLACE NODE                                    ^Index^
 ────────────────────────────────────────────────────────────

 With this option you can  replace a node with an  other node
 in the linked system list for a global group of areas.

 See also: ^Global Linked Systems^
*E
*B 4510,Global Area Switches
 GLOBAL AREA SWITCHES                                   ^Index^
 ────────────────────────────────────────────────────────────

 Here you  can change  all switches for  an area specified by
 one or more group(s).

 In  almost  every  case,  the  changes  will  be  made  on a
 per-group basis. One or more groups may be specified and the
 modifications will be made  for all  echo areas which belong
 to the select(ed) group(s).

 See also:  ^Global Active^             ^Global Security^
            ^Global Unlinked^           ^Global Mandatory^
            ^Global Tiny SB^            ^Global Hide SB^
            ^Global Active^             ^Global Security^
 ...
*P
 GLOBAL AREA SWITCHES                                   ^Index^
 ────────────────────────────────────────────────────────────
 ...
            ^Global Hidden^             ^Global Unlinked^
            ^Global Autounlink^         ^Global Mandatory^
            ^Global Read Only^          ^Global Tiny SB^
            ^Global Import SB^          ^Global Hide SB^
            ^Global Manual^             ^Global Zone Gate^
            ^Global No %Pause^          ^Global Dupecheck^
            ^Global Squish Kill^        ^Global Dupe MsgId^
*E
*B 4511,Global Active
 GLOBAL ACTIVE                                          ^Index^
 ────────────────────────────────────────────────────────────

 This by default is set to 'Y',  which means that the area is
 active. If set to 'N',  IMAIL will behave as if the area had
 not been defined.

 This will allow you to disable an echo area - for any reason
 you may wish - without  having to  actually  delete  it, and
 later re-enter it.

 Unlike unlinked or hidden areas,  inactive areas are ignored
 by AreaLink and cannot accessed by any downlink.

 See also: ^Global Area Switches^
*E
*B 4512,Global Security
 GLOBAL SECURITY                                        ^Index^
 ────────────────────────────────────────────────────────────

 If enabled, IMAIL will check the address of the system which
 sent the  message  in this area.  If it is among the  export
 nodes  listed in the  Export List,  it will be  imported and
 processed;  otherwise,  it  will  be  tossed  into  your Bad
 Message  Board.  Note  that  the  sender's  address  will be
 determined using the PKT-address,  not the address stated in
 the origin line.

 If this  switch is set to  N,  IMAIL  will  also  ignore the
 export only flag in the list of linked systems.

 See also: ^Global Area Switches^
*E
*B 4513,Global Hidden
 GLOBAL HIDDEN                                          ^Index^
 ────────────────────────────────────────────────────────────

 Enable this option if this area  should not be  displayed in
 any AreaLink report  of available areas.  Moreover it cannot
 be linked  with a  wildcard request.  It can only  be linked
 when explicitly stating the full areatag.

 See also: ^Global Area Switches^
*E
*B 4514,Global Unlinked
 GLOBAL UNLINKED                                        ^Index^
 ────────────────────────────────────────────────────────────

 Together with  Autounlink,  this  field controls  the unlink
 status  for the  current area.  If this field is set to yes,
 IMAIL has unlinked  this area  after the  last downlink  has
 unlinked  it from your  system and  the remaining  system is
 listed as uplink in the ^Forward Manager^.

 The area  will still  appear in your list of available areas
 and  if a system  requests this area,  IMALNK  automatically
 requests this area from your uplink again.

 See also: ^Global Area Switches^
*E
*B 4515,Global Autounlink
 GLOBAL AUTOUNLINK                                      ^Index^
 ────────────────────────────────────────────────────────────

 If this option  is set to 'N' the  unlink check  is disabled
 for this area, so it will remain linked to your system.

 See also: ^Global Area Switches^
*E
*B 4516,Global Mandatory
 GLOBAL MANDATORY                                       ^Index^
 ────────────────────────────────────────────────────────────

 If you set this  field to yes,  no downlink can  unlink from
 this area  using the  AreaLink functions.  This can  only be
 done maτnually. This field is useful when you really  want an
 area to be read.

 See also: ^Global Area Switches^
*E
*B 4517,Global Read Only
 GLOBAL READ ONLY                                       ^Index^
 ────────────────────────────────────────────────────────────

 If this option is enabled,  every system  linking  this area
 gets an  export only flag ( which can be removed manually by
 the sysop).  This flag prevents unauthorized  downlinks from
 posting messages in restricted ( read only) areas.

 See also: ^Global Area Switches^
*E
*B 4518,Global Tiny SB
 GLOBAL TINY SB                                         ^Index^
 ────────────────────────────────────────────────────────────

 Enable this  option if  you want  to strip  all the  SEEN-BY
 information from  an  incoming  echo  message  before  it is
 re-exported.

 In this case,  the outgoing  message will  contain  only the
 SEEN-BYs of your downlinks. Note, however,  that if the area
 is not marked  as  passthrough,  and if the Import SB option
 is active,  the message will be =imported= with the original
 SEEN-BY information.

 See also: ^Global Area Switches^
*E
*B 4519,Global Import SB
 GLOBAL IMPORT SB                                       ^Index^
 ────────────────────────────────────────────────────────────

 This switch controls whether the  SEEN-BYs are imported into
 the message base or whether they are stripped.

 See also: ^Global Area Switches^
*E
*B 4520,Global Hide SB
 GLOBAL HIDE SB                                         ^Index^
 ────────────────────────────────────────────────────────────

 If this switch  is set to Yes,  IMAIL puts a CTRL-A in front
 of every SEEN-BY line.  This is useful for the BBS  software
 which should not display these hidden SEEN-BYs to the normal
 users then.

 See also: ^Global Area Switches^
*E
*B 4521,Global Manual
 GLOBAL MANUAL                                          ^Index^
 ────────────────────────────────────────────────────────────

 This  switch gives  you the  total control over the links to
 this area.  With this one  set to Yes,  the area is visible,
 but totally unaccessible for IMALNK.

 You can  use this  to ensure  that only adult links read the
 x-rated areas or to establish some  kind of closed-usergroup

 See also: ^Global Area Switches^
*E
*B 4522,Global Zone Gate
 GLOBAL ZONE GATE                                       ^Index^
 ────────────────────────────────────────────────────────────

 This field is  similar to  the Global Tiny SB field (above).
 It indicates that  IMAIL should  strip all  information from
 the SEEN-BY line when exporting to a system  which  is  in a
 different zone,  except for  your address  and  that  of the
 downlink.  Currently, zonegating only works with ONE node in
 the other zone,  because the new  SEEN-BYs will only contain
 your own and the destination address.

 Note that  when the  message is imported in your messagebase
 ( if the area is not passthrough) the original SEEN-BY lines
 will be preserved.

 See also: ^Global Area Switches^
*E
*B 4523,Global No %Pause
 GLOBAL NO %PAUSE                                       ^Index^
 ────────────────────────────────────────────────────────────

 This setting can be  used with important areas.  By default,
 your downlinks can prevent echo mails being exported to them
 using  the %PAUSE  meta-command with Arealink.  If you don`t
 want information in important areas to pass  your downlinks,
 you can inhibit the pausing of an area with this switch.

 See also: ^Global Area Switches^
*E
*B 4524,Global Dupecheck
 GLOBAL DUPECHECK                                       ^Index^
 ────────────────────────────────────────────────────────────

 This switch can be used to advise  IMAIL not to perform dupe
 checking on  an area.  This increases  the  speed of  TOSS a
 little, but increases the risk of dupes noticeably.

 See also: ^Global Area Switches^
*E
*B 4525,Global Squish Kill
 GLOBAL SQUISH KILL                                     ^Index^
 ────────────────────────────────────────────────────────────

 This switch  controls  whether  or not  IMAIL should use the
 Squish  'kill  on  the  fly' - function  on  this  Area.  It
 corresponds with the settings in the > Global Menu > special
 parameters.  Of course,  this switch will only  affect Areas
 that are set to 'Squish'.

 See also: ^Global Area Switches^
*E
*B 4526,Global Dupe MsgId
 GLOBAL DUPE MSGID                                      ^Index^
 ────────────────────────────────────────────────────────────

 IMAIL has two ways of checking for Dupes:

 Either it  calculates the  crc  header  sum or it checks the
 MSGID.  Especially in gated areas,  dupes occur with changed
 headers, but identical MSGID.  For these areas,  you can set
 this switch  to 'Y'.  IMAIL  will then  check  every  single
 incoming  Msg in  this area  against the  MSGID's  stored in
 IMAIL.DP.  Not finding  it there,  the  header crc  will  be
 checked afterwards.

 See also: ^Global Area Switches^
*E
*B 4530,Global Text Fields
 GLOBAL TEXT FIELDS                                     ^Index^
 ────────────────────────────────────────────────────────────

 Here you can change the origin line,  the origin address and
 the list of seen-bs.

 In  almost  every  case,  the  changes  will  be  made  on a
 per-group basis. One or more groups may be specified and the
 modifications will be made  for all  echo areas which belong
 to the select(ed) group(s).

 To get more information for  each option, highlight with the
 menu bar and press F1 for help.
*E
*B 4531,Global Origin Line
 GLOBAL ORIGIN LINE                                     ^Index^
 ────────────────────────────────────────────────────────────

 Here you may specify up to  63 characters which will be used
 as the origin line for the area if it is an echo area.

 To this will be prefixed the string:

       * Origin:

 and your  origin address will be appended.  The total length
 must not exceed 79 characters.

 If you forget to define this field,  the default origin line

 ...
*P
 GLOBAL ORIGIN LINE                                     ^Index^
 ────────────────────────────────────────────────────────────
 ...

 will be used. Note that if the BBS or editor program used to
 write an echo message  already adds an origin line,  the one
 defined here will not be used.

*E
*B 4532,Global ORIGIN ADDRESS
 GLOBAL ORIGIN ADDRESS                                  ^Index^
 ────────────────────────────────────────────────────────────

 Here you can choose the address to use in the Origin line of
 the message.
    
 This address  will also be used in the PATH line of the echo
 message, as well as in the list of SEEN-BYs.

 Note that  only the  net and  node numbers will be placed in
 the  SEEN-BYs  and PATH  lines; the  use of  zone and  point
 numbers is not accepted.
*E
*B 4533,Global Seen-Bys
 GLOBAL SEEN-BYS                                        ^Index^
 ────────────────────────────────────────────────────────────

 This field pops up a window that allows you to choose one or
 more addresses to add to the SEEN-BY line for that area.
*E
*B 4534,Global Message path
 GLOBAL MESSAGE PATH                                    ^Index^
 ────────────────────────────────────────────────────────────

 This function allows to replace parts of the message area
 paths (Squish/Msg/Jam). Example: Your current message bases
 are all under 'C:\MSGBASE\...' but you want to get them all
 to 'D:\MAIL\BASES\...'. This function allows to replace
 'C:\MSGBASE\' with 'D:\MAIL\BASES\' in all matching cases.
 You can also replace parts within the paths like '\BASES\'
 with '\BASE'.

 The function works on the areas of the selected groups and
 looks for the string to replace. This string is replaced by
 the new string.
*E
*B 4540,Global Digit Fields
 GLOBAL DIGIT FIELDS                                    ^Index^
 ────────────────────────────────────────────────────────────

 Here  you  can  change  all fields  with digit values in it.

 In  almost  every  case,  the  changes  will  be  made  on a
 per-group basis. One or more groups may be specified and the
 modifications will be made  for all  echo areas which belong
 to the select(ed) group(s).

 To get more information for  each option, highlight with the
 menu bar and press F1 for help.
*E
*B 4541,Global #Days
 GLOBAL #DAYS                                           ^Index^
 ────────────────────────────────────────────────────────────

 This  item is  used by  IMTHINGS KILL /U to  determine which
 messages to kill: it will mark as deleted any messages older
 than the  number of  days specified here.  If this  field is
 left at  zero,  no  messages  will  be  killed,  unless  the
 "# Msgs" field below is specified.

 The maximum value which can be entered in this field is 255.
 If the  area is  marked  as  Passthrough,  this field has no
 meaning (kinda obviously).
*E
*B 4542,Global #Msgs
 GLOBAL #MSGS                                           ^Index^
 ────────────────────────────────────────────────────────────

 This is  used  by  IMTHINGS KILL /U  to determine  how  many
 messages to leave in  this board.  If this  field is left at
 zero,  it will be ignored,  and no messages will be  killed,
 unless the "# Days" field is specified.

 Naturally,  if the area is  Passthrough,  this field  has no
 meaning.

*E
*B 4543,Global Kill Dead
 GLOBAL KILL DEAD                                       ^Index^
 ────────────────────────────────────────────────────────────

 IMAIL  allows you  to delete  areas  without traffic after a
 definable number  of days.  During the midnight  maintenance
 IMAIL marks areas without traffic.

 A value  of 0  disables the  function  for  this  area,  the
 maximum number of days is 256.

 Dead  areas are  marked in the  Area Manager,  do not forget
 that this  check is only  done during  midnight  maintenance
 and the Area Manager shows only full days.
*E
*B 4544,Global Read Security
 GLOBAL READ/WRITE SECURITY                             ^Index^
 ────────────────────────────────────────────────────────────

 These  two  settings  control -  in  addition  to  the group
 characters - who may link to an area  and who  may  write in
 it.

 In the ^Node Manager^,  you can specify an Area Security Level
 for every system.

 Systems that have a security  level below the value given in
 'Read Sec'  will not  be  able  to  link to  that echo.  For
 systems with  a security level  higher or  equal than  'Read
 Sec',  but lower than  'Write Sec'  the area  will be linked

 ...
*P
 GLOBAL READ/WRITE SECURITY                              ^Index^
 ────────────────────────────────────────────────────────────
 ...

 'Export Only'.  That means  the system will receive mails in
 that echo,  but messages  sent by  it will  be  tossed  into
 BADMAIL.
*E
*B 4545,Global Write Security
 GLOBAL READ/WRITE SECURITY                             ^Index^
 ────────────────────────────────────────────────────────────

 These  two  settings  control -  in  addition  to  the group
 characters - who may link to an area  and who  may  write in
 it.

 In the ^Node Manager^,  you can specify an Area Security Level
 for every system.

 Systems that have a security  level below the value given in
 'Read Sec'  will not  be  able  to  link to  that echo.  For
 systems with  a security level  higher or  equal than  'Read
 Sec',  but lower than  'Write Sec'  the area  will be linked

 ...
*P
 GLOBAL READ/WRITE SECURITY                              ^Index^
 ────────────────────────────────────────────────────────────
 ...

 'Export Only'.  That means  the system will receive mails in
 that echo,  but messages  sent by  it will  be  tossed  into
 BADMAIL.
*E
*B 4546,Global Group (By Group)
 GLOBAL GROUP (BY GROUP)                                ^Index^
 ────────────────────────────────────────────────────────────

 With this Option, you can change a group with another group.

 See also: ^Global Group (By Areatag)^
*E
*B 4547,Global Group (By Areatag)
 GLOBAL GROUP (BY AREATAG)                              ^Index^
 ────────────────────────────────────────────────────────────

 With  this  Option,  you can  change / set  a  group  for an
 areamask.

 See also: ^Global Group (By Group)^
*E
*B 500,Node Manager
 NODE MANAGER                                           ^Index^
 ────────────────────────────────────────────────────────────

 The  Node Manager  is used to specify information  regarding
 the systems  to  which  you  export  mail,  including  which
 program  will be  used  to compress  outbound  mail  for the
 system, as well as what type of file attach to generate.

 The Node Manager is divided into a BROWSE- and an EDIT mode.

 See also: ^Node Manager Keylist^
*E
*B 5000,Node Manager Keylist
 NODE MANAGER KEYLIST                                   ^Index^
 ────────────────────────────────────────────────────────────

 BROWSE mode keys:

 <ENTER>         Edit           <F1>            Help
 <SH><F1>        Show Keys      <F2>            Find Record
 <F4>            List Records   <F5>            Copy Record
 <F7>            Edit Areas     <SH><F7>        Statistic
 <F10>           Save           <ESC>           Exit
 <INS>           Add Record     <DEL>           Delete Record
 <HOME>          First Record   <END>           Last Record
 <PGUP>/<PGDN>   Prev/Next      <RIGHT/LEFT>    Prev/Next
 
 ...
*P
 NODE MANAGER KEYLIST                                   ^Index^
 ────────────────────────────────────────────────────────────
 ...

 EDIT mode keys:

 <>/<>/<>/<> \              <ENTER>         Change/Edit
 <PGUP>/<PGDN>    Move Bar      <ESC>           Abort
 <TAB>/<SH><TAB> /              <F1>            Help
                                <F10>           Save

 See also: ^Node Manager^
*E
*B 5101,Address
 ADDRESS                                                ^Index^
 ────────────────────────────────────────────────────────────

 Here you specify the address of the  system.  The  Zone, Net
 and node are  required.  If no point  is specified,  it will
 default to  0.  When  changing  a  node's  address,  IMSETUP
 will allow  to change  the nodenumber  in the  area records,
 too.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5102,Sysop
 SYSOP                                                  ^Index^
 ────────────────────────────────────────────────────────────

 This field allows you to specify  the name  of the  sysop of
 the system.  It is  used for  purely cosmetic  purposes,  by
 AreaLink and  when generating  net mail messages,  and so is
 not required.  But as  man usually  remembers  names  rather
 than numbers  it is  strongly recommended  that you fill out
 this field.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5103,Pkt Origin Address
 PKT ORIGIN ADDRESS                                     ^Index^
 ────────────────────────────────────────────────────────────

 Here you  can configure  one of  the  system  akas as  fixed
 origin address for the packets created for this system. Also
 the origin  address  of the area can be  used,  which is the
 default setting.  This feature allows to use always the same
 aka when sending packets to a specific system.

 Note that the  address specified here is  only used  for the
 *.PKTs;  this has nothing to do with the single mails or the
 sender of the compressed file (the ARCmail-bundle).

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5104,Pack Priority
 PACK PRIORITY                                          ^Index^
 ────────────────────────────────────────────────────────────

 This field  controls the  order in  which the tossed mail is
 compressed for the nodes. You can specify a  value between 0
 and 9. Nodes who have a "9"  will have their mail compressed
 first. This is useful for nodes who have a separate computer
 for  TOSSing and  whose  downlinks use  to call  immediately
 after the poll to the uplink. By this,  you can compress the
 mail for the pesters first.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5105,Node Domain
 NODE DOMAIN                                            ^Index^
 ────────────────────────────────────────────────────────────

 Here you can select the domain to which the system  belongs.
 This is  very important in  multi-domain  environments,  and
 when  you  have  different  outbound  directories  for  each
 domain.  Select the domain from  the list presented.  If the
 system belongs to  a domain which is not listed,  you should
 define it in the Domains menu.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5106,PKT Routing
 PKT ROUTING                                            ^Index^
 ────────────────────────────────────────────────────────────

 This function allows you to sent all PKTs for this system to
 the  address  specified here  instead  of  sending the  PKTs
 direct to the destination system. This is especially usefull
 of you have  a downlink which is  connected to more than one
 FTN-compatible network at your system and sends/receives his
 mail under different adresses,  but can only present one aka
 when calling your system (FTS-0001, FTS-0006 Yoohoo, etc.).

 In this case, you enter the  address used  when polling into
 PKT Routing for all other  records of  this downlink  in the
 Node Manager. IMCOMP will then pack all PKTs for the defined

 ...
*P
 PKT ROUTING                                            ^Index^
 ────────────────────────────────────────────────────────────

 aka allowing  the downlink to pick up the all his mail with-
 out further problems.  An example is Yuppie when the Yuppie-
 System is connected to different FTN-networks.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5107,AreaLink Password
 AREALINK PASSWORD                                      ^Index^
 ────────────────────────────────────────────────────────────

 If specified, this will be the password that the system will
 use when requesting areas or information from  Area Link. If
 no password is specified,  the  system  may  not request any
 areas, even if one or more groups have been enabled.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5108,Packet Password
 PACKET PASSWORD                                        ^Index^
 ────────────────────────────────────────────────────────────

 For added security, you may specify that packets to and from
 this node contain a password. The password may not be longer
 than 8 characters. This password will  ensure that mail from
 that  system  cannot  be  sent  by  someone else under false
 pretences.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5109,Groups
 GROUPS                                                 ^Index^
 ────────────────────────────────────────────────────────────

 A system must have at least one group enabled in order to be
 able to  request a  link to  any echo  area which is part of
 that group.

 Here  you can  access the  ^Group Manager^ which shows you the
 groups currently assigned  to that system and  allows you to
 add or remove certain groups very easy.

 <ENTER>/<SPACE> to select/deselect single groups
 <INS>/<DEL>     to select/deselect all groups
 <F10>           to accept the selection
 <ESC>           to skip the selection

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5110,Area Security
 AREA SECURITY                                          ^Index^
 ────────────────────────────────────────────────────────────

 The  value you  enter here  corresponds  directly  with  the
 fields ^Read/Write Security^  in the  area record. Here, you
 can  assign a  certain  security  level to  the  node  which
 controls which areas he/she can link.
 Apart from the groups,  this is a useful feature to restrict
 access to areas.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5111,Check PKT Password
 CHECK PKT PASSWORD                                     ^Index^
 ────────────────────────────────────────────────────────────

 You can control the  use  of the previously specified packet
 password with the  help of  this switch.  If you set this to
 "N",  incoming  packets  are  not  checked  for  the  packet
 password,  while  outgoing packets ( those created by IMAIL)
 will contain the specified password.  Setting this switch to
 "Y",  IMAIL  will   only  process   packets  with   matching
 passwords.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5112,Notify
 NOTIFY                                                 ^Index^
 ────────────────────────────────────────────────────────────

 This flag indicates whether or not the specified node should
 receive NOTIFY messages.  By default,  this is  set  to Yes,
 indicating  that  the  system  will  receive a  notification
 message from IMALNK.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5113,Remote Maint
 REMOTE MAINT                                           ^Index^
 ────────────────────────────────────────────────────────────

 IMAIL may allow systems to  carry  out  changes in the links
 for other systems. These changes may be  made  via AreaLink,
 using the %FROM meta-command.

 In order to enable a node  to  make  these changes for other
 systems, this field must be set to 'Y'; the default is 'N'.

 Remote Maint also allows the system to delete  an echo  area
 from your list,  or to change the name of  an  area. It thus
 allows a lot of control over your system.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5114,Change packer
 CHANGE PACKER                                          ^Index^
 ────────────────────────────────────────────────────────────

 Here  you can  control  whether  this  system is  allowed to
 change the  packer  using the  commands of  IMALNK.  This is
 useful for systems  which are  called by  you and  where you
 always want to use a very good packer.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5115,Check echo for ALNK-Msg
 CHECK ECHO FOR AREALINK-MESSAGES                       ^Index^
 ────────────────────────────────────────────────────────────

 This feature of  IMAIL  allows to check  every  message from
 this system whether it is  a  message to Arealink ( to avoid
 for  example   exporting   an   Arealink   request  that  an
 unexperienced  points has  posted in  an echo).  Use it with
 care because it requires some time while tossing.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5116,Ext. Arcmail Names
 EXTENDED ARCMAIL NAMES                                 ^Index^
 ────────────────────────────────────────────────────────────

 When  creating  ARCmail-bundles,  IMCOMP  uses the first two
 letters of the weekday and a consecutive one-digit number to
 determine the extension of the file.

 For example .MO0, .MO1, .MO2, .MO3, ...

 If IMCOMP  has to create  an eleventh bundle,  it can either
 continue with 'A' after '9' (up to 'Z')  or stop compressing
 and continue the next day.



 ...
*P
 EXTENDED ARCMAIL NAMES                                 ^Index^
 ────────────────────────────────────────────────────────────
 ...

 Some older mailprocessors have problems  identifying bundles
 with letters in the last digit of the extension, switch this
 toggle to 'N' for theses links.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5117,Max. Mail Packet size
 MAX. MAIL PACKET SIZE                                  ^Index^
 ────────────────────────────────────────────────────────────

 With this option, you can specify the  maximum  size  of the
 packet files (*.PKT) that  IMAIL  will  create.  Use this if
 your up and/or down  links  are  short  on  disk space.

 The number should indicate a size  in  kilobytes.  If a zero
 (0) is specified, there will be no limit imposed.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5118,Max. Arcmail size
 MAX. ARCMAIL SIZE                                      ^Index^
 ────────────────────────────────────────────────────────────

 Setting this to a  non-zero  value tells  IMCOMP  not to add
 further arcmail PKTs to a  compressed  ARCmail bundle if its
 size is bigger  than  specified ( in kB).  IMCOMP  will then
 create a  new bundle. Using  this feature you  can limit the
 size of the arcmail  bundles and therefore reducing the time
 which is  needed to transfer the bundle  again  if a session
 was interrupted.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5119,PKTs To Pack Per Call
 PKTS TO PACK PER CALL                                  ^Index^
 ────────────────────────────────────────────────────────────

 Together with  'Max. Arcmail Size', this  field controls the
 size of the outgoing ARCmail bundles.

 When set to  0,  IMCOMP will add  _all_  pending PKTs  to an
 existing ARCmail bundle or creating one single bundle.

 Setting  this  field to a  non-zero value,  IMCOMP will only
 process this number  of PKTs per call,  then again check the
 size of the created ARCmail bundle.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5120,Rescan OK
 RESCAN OK                                              ^Index^
 ────────────────────────────────────────────────────────────

 This flag indicates whether the  system is allowed to rescan
 echo mail from your system,  with  an AreaLink  request.  Of
 course, only those echoes to which this node has access will
 be rescanned.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5121,Add to new areas
 ADD TO NEW AREAS                                       ^Index^
 ────────────────────────────────────────────────────────────

 If you  wish this  system to be added to all new areas, then
 set this field to Yes.  Note that the node will only be auto
 added  if it  is in  the same  domain as  the  system  which
 "created" the new area.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5122,Forward Requests
 FORWARD REQUESTS                                       ^Index^
 ────────────────────────────────────────────────────────────

 This flag selects whether  this  system is allowed  to cause
 Forward  Link  Requests,  so you can prevent downlinks  from
 requesting areas from your uplink.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5123,Create new areas
 CREATE NEW AREAS                                       ^Index^
 ────────────────────────────────────────────────────────────

 If you  wish to  allow the  system to  create new  echo mail
 areas on your system, then set this flag to 'Y'.  Otherwise,
 mail in unknown  echo areas,  originating from this  system,
 will be tossed into the bad message area.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5124,New Areas Group
 NEW AREAS GROUP                                        ^Index^
 ────────────────────────────────────────────────────────────

 If you have  enabled the  Create New  option ( above),  this
 field  will  specify  the group  to be  used for  echo areas
 created by the node. If it is left empty, group will default
 to that specified in the Other Parameters menu).

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5125,Uplink
 UPLINK                                                 ^Index^
 ────────────────────────────────────────────────────────────

 Together with "Program Name" and "FSC-0057 compatible" these
 fields are used by the remote functions  of AreaLink.  If an
 area is remote created, renamed  or deleted,  IMAIL  informs
 your  links  about  this.  This field  selects whether  this
 system is one of your uplinks.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5126,Program name
 PROGRAM NAME                                           ^Index^
 ────────────────────────────────────────────────────────────

 This is the name of the AreaLink used by this system.  It is
 used by Arealink when forwarding  delete,  create or  change
 requests to the systems linked to a certain echo.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5127,FSC-0057 Compatible
 FSC-0057 COMPATIBLE                                    ^Index^
 ────────────────────────────────────────────────────────────

 This  flag  specifies  whether  this   system  is   FSC-0057
 compatible ( which  is only required  concerning  the remote
 delete, rename and create request).

 If such a function is executed on your system,  all affected
 downlinks are notified. If they are also FSC-0057 compatible
 and are not an uplink,  their AreaLink is also notified with
 a message.

 The table below shows how AreaLink works in this cases:


 ...
*P
 FSC-0057 COMPATIBLE                                    ^Index^
 ────────────────────────────────────────────────────────────
 ...

 Remote req      FSC-0057           not FSC-0057

 delete        delete request      unlink request
 create        create request       link request
 rename        rename request      --------------


 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5128,Message Status
 MESSAGE STATUS                                         ^Index^
 ────────────────────────────────────────────────────────────

 Here you can change the message status for messages  created
 by IMAIL  (like  AreaLink  replies).  By  default,  this  is
 "Normal", but you may select one of:

     Normal            No status
     Hold              Hold message for pick up
     Crash             Send message Crash
     Immediate         Set Immediate flag

 This  status  can  be  combined  with  a direct  status,  so
 messages created by IMAIL can be prevented from being routed

 ...
*P
 MESSAGE STATUS                                         ^Index^
 ────────────────────────────────────────────────────────────
 ...

 via other systems. The destination system must either pickup
 them at your system or you  will have to send these messages
 directly to their destination.

 Note that any systems not  defined in the  Node Manager will
 not have their messages marked DIRECT.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5129,Attach Status
 ATTACH STATUS                                          ^Index^
 ────────────────────────────────────────────────────────────

 This entry allows you to change the  file attach status.  By
 default,  this is also "Normal",  but you may select one of:

     Normal            No status
     Hold              Hold attach for pick up
     Crash             Send attach Crash
     Immediate         Send attach Immediately

 This can be combined with a direct status,  so file attaches
 will  never  be  routed  via  other  systems.  This  is  not
 available in a  Binkley environment because FLO-files are by

 ...
*P
 ATTACH STATUS                                          ^Index^
 ────────────────────────────────────────────────────────────
 ...

 default direct.

 It  is  STRONGLY  recommended  that echo mail NOT be routed,
 (pretty safe way to get guys angry)  so if the  node is your
 echo mail feed, it is best to mark it as Direct.

 Note that any systems not  defined in the  Node Manager will
 have their mail put on HOLD for pickup.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5130,Packer
 PACKER                                                 ^Index^
 ────────────────────────────────────────────────────────────

 Here you will be able  to select the program to use for mail
 compression. A list will appear, containing the programs you
 defined in the "Compression Programs" menu.

 If you make no selection,  by default the  first  program in
 the list will be used.

 Note that  is is  possible to  specify  that no  compression
 program be used (the last entry in the  list). In this case,
 PKT files  addressed to  the node being  edited will  not be
 compressed, and will simply be file attached to  the system.

 ...
*P
 PACKER                                                 ^Index^
 ────────────────────────────────────────────────────────────
 ...

 This  allows  simple  mail processors  to receive  mail from
 IMAIL  systems   without   needing  to  have   one  or  more
 decompression programs available.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5131,Capability
 CAPABILITY                                             ^Index^
 ────────────────────────────────────────────────────────────

 The Capability describes the other  system's mail processor.
 Currently, two types are defined:

         Stone Age
         Type 2+

 You  can set this field  according to  the capability of the
 remote system's mail processor, if known.
 If you are unsure, leave the field set to "Stone Age".

 Note,  that  it  is  possible  to  define  as  Type 2+  mail

 ...
*P
 CAPABILITY                                             ^Index^
 ────────────────────────────────────────────────────────────
 ...

 processors which are not normally detected as such but which
 have the zone and  point information.  This is  done in  the
 Product Code menu.

 For  more  information on the capability word,  refer to the
 FTSC documents  FSC-0039 and  FSC-0048.  See also  FTS-0001.
 These documents  may  be available  near you;  otherwise you
 should be able to file request them from 1:1/20.

 Note  also  that  IMAIL  will  always  generate " Type  2+ "

 ...
*P
 CAPABILITY                                             ^Index^
 ────────────────────────────────────────────────────────────
 ...

 information in the packet header,  and identify itself  as a
 Type 2+  mail processor,  regardless of the setting  of this
 field.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5132,CW Handling
 CW HANDLING                                            ^Index^
 ────────────────────────────────────────────────────────────

 This field allows you to  define  how  IMAIL  will  use  the
 setting  defined  in  the  Capability  field  when  handling
 inbound mail. If it is set to "Force", IMAIL will always use
 the setting defined in the Capability field,  regardless  of
 what the actual format of the inbound packet(s) might be.

 Instead, if set to "Auto", IMAIL will try to  determine  the
 type of packet by examining  the  Capability  Word  and  its
 validation copy and/or the product  code,  and  process  the
 file accordingly.


 ...
*P
 CW HANDLING                                            ^Index^
 ────────────────────────────────────────────────────────────
 ...

 Please note that IMAIL cannot  correctly handle points which
 use  "Stone Age"  mail  processors,  unless  they are  using
 fakenet addresses.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5133,Alnk with '+'
 ALNK with '+'                                          ^Index^
 ────────────────────────────────────────────────────────────

 Here  you can  define  whether  IMALNK  prefixes  area  link
 requests  with a '+'.  As  the  areafix  functions  of  some
 programs  do not  accept a  preceeding '+',  you can disable
 this here.

*E
*B 5134,Send rules
 SEND RULES                                             ^Index^
 ────────────────────────────────────────────────────────────

 When you enable this switch,  IMALNK will send  the rules of
 an area to this system  when it links an  area for the first
 time (not  on  update  requests).

 This IMALNK area  rules support  function will  only work if
 the global rules path  is defined and if  the file  name for
 the area  rule also is  defined in the  area record  for the
 area.  IMALNK will  add the  text  header IMRULE.HEA  if  it
 exists  in the  IMAIL  home  directory.  If no rule  name is
 defined in  the  area record  or if the rule  file cannot be
 found,  IMALNK will send IMNORULE.HEA which is also expected
 in the IMAIL home directory.
 ...
*P
 SEND RULES                                             ^Index^
 ────────────────────────────────────────────────────────────
 ...

 The remote user can toggle this switch using the metacommand

     %RULES <ON|OFF>.
*E
*B 5201,Find Node Record
 FIND NODE RECORD                                       ^Index^
 ────────────────────────────────────────────────────────────

 Pressing <F2> brings  up a window in which you may specify a
 node number. If the address is found, it will be displayed.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5203,List Node Record
 LIST NODE RECORD                                       ^Index^
 ────────────────────────────────────────────────────────────

 The browse function will allow you  to examine a list of all
 the  currently  defined  nodes  and  to  move  quickly  to a
 specific record. The window  shows some infomation about the
 system. For example, an entry might read:

        12:3456/789  Test User       C

 The  letter following  the sysop  name indicates  the attach
 status  ('H' means  Hold, 'C' stands for  Crash while 'N' is
 Normal. An additional 'D' means Direct).

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5204,Edit/Show Linked Areas
 EDIT/SHOW LINKED AREAS                                 ^Index^
 ────────────────────────────────────────────────────────────

 A window will pop  up with the area  record list. Every area
 this node is linked to will  be highlighted and preceeded by
 a '+'.  If this system is set to  "Import only"  or  "Export
 only"  or if  it has  set the  "Paused" flag,  this  will be
 indicated by the letters 'I', 'E' and 'P'.

 The following keys are available:

        <+>     to add the node to the list of linked systems
                for this area
        <->     to remove  the node  form the  list of linked
                systems for this area
        <I>     to set this link to Import Only
        <E>     to set this link to Export Only
        <P>     to pause this system for this area

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5205,Node STATISTIC
 NODE STATISTIC                                         ^Index^
 ────────────────────────────────────────────────────────────

 Pressing  <SH><F7>  while browsing through  the node records
 you will be confronted with a small window which informs you
 about the recent mailflow statistics of this node.

 See also: ^Node Manager^    ^Node Manager Keylist^
*E
*B 5500,Global groups
 GLOBAL GROUPS                                          ^Index^
 ────────────────────────────────────────────────────────────

 Here you  can global add,  delete or replace a group  in the
 records of the Node Manager.

 The changes will be made  on a  per-node base.  Nodes may be
 specified also using  the wildcard '*' and the modifications
 will be made for all nodes matching the entered sheme.

 See also: ^Global Add Groups^        ^Global Remove Groups^
           ^Global Change Groups^     ^Global Set Groups^
           ^Global Autocreate group^
*E
*B 5501,Global Add Groups
 GLOBAL ADD GROUPS                                      ^Index^
 ────────────────────────────────────────────────────────────

 With this option  you can add access to  groups for a global
 set of nodes.

 See also: ^Global Groups^
*E
*B 5502,Global Remove Groups
 GLOBAL REMOVE GROUPS                                   ^Index^
 ────────────────────────────────────────────────────────────

 With  this  option you  can remove  access  to groups  for a
 global set of nodes.

 See also: ^Global Groups^
*E
*B 5503,Global Change Groups
 GLOBAL CHANGE GROUPS                                   ^Index^
 ────────────────────────────────────────────────────────────

 With this option you can  change groups  for a global set of
 nodes.

 See also: ^Global Groups^
*E
*B 5504,Global Set Groups
 GLOBAL SET GROUPS                                      ^Index^
 ────────────────────────────────────────────────────────────

 With this option you can set  the groups for a global set of
 nodes.

 See also: ^Global Groups^
*E
*B 5505,Global Autocreate Group
 GLOBAL AUTOCREATE GROUP                                ^Index^
 ────────────────────────────────────────────────────────────

 With  this option  you can  set  the autocreate group  for a
 global set of nodes.

 See also: ^Global Groups^
*E
*B 5510,Global node switches
 GLOBAL NODE SWITCHES                                   ^Index^
 ────────────────────────────────────────────────────────────

 Here you can change all switches for a set of nodes

 The changes will be made  on a  per-node base.  Nodes may be
 specified also using  the wildcard '*' and the modifications
 will be made for all nodes matching the entered sheme.
*E
*B 5511,Global Rescan OK
 GLOBAL RESCAN OK                                       ^Index^
 ────────────────────────────────────────────────────────────

 This flag indicates whether the  system is allowed to rescan
 echo mail from your system,  with  an AreaLink  request.  Of
 course, only those echoes to which this node has access will
 be rescanned.
*E
*B 5512,Global Create new areas
 GLOBAL CREATE NEW AREAS                                ^Index^
 ────────────────────────────────────────────────────────────

 If you  wish to  allow the  system to  create new  echo mail
 areas on your system, then set this flag to 'Y'.  Otherwise,
 mail in unknown  echo areas,  originating from this  system,
 will be tossed into the bad message area.
*E
*B 5513,Global Uplink
 GLOBAL UPLINK                                          ^Index^
 ────────────────────────────────────────────────────────────

 Together with "Program Name" and "FSC-0057 compatible" these
 fields are used by the remote functions  of AreaLink.  If an
 area is remote created, renamed  or deleted,  IMAIL  informs
 your  links  about  this.  This field  selects whether  this
 system is one of your uplinks.
*E
*B 5514,Global Forward Requests
 GLOBAL FORWARD REQUESTS                                ^Index^
 ────────────────────────────────────────────────────────────

 This flag selects whether  this  system is allowed  to cause
 Forward  Link  Requests,  so you can prevent downlinks  from
 requesting areas from your uplink.
*E
*B 5515,Global Change packer
 GLOBAL CHANGE PACKER                                   ^Index^
 ────────────────────────────────────────────────────────────

 Here  you can  control  whether  this  system is  allowed to
 change the  packer  using the  commands of  IMALNK.  This is
 useful for systems  which are  called by  you and  where you
 always want to use a very good packer.
*E
*B 5516,Global Ext. Arcmail Names
 GLOBAL EXTENDED ARCMAIL NAMES                          ^Index^
 ────────────────────────────────────────────────────────────

 When  creating  ARCmail-bundles,  IMCOMP  uses the first two
 letters of the weekday and a consecutive one-digit number to
 determine the extension of the file.

 For example .MO0, .MO1, .MO2, .MO3, ...

 If IMCOMP  has to create  an eleventh bundle,  it can either
 continue with 'A' after '9' (up to 'Z')  or stop compressing
 and continue the next day.

 Some older mailprocessors have problems  identifying bundles
 with letters in the last digit of the extension, switch this
 toggle to 'N' for theses links.
*E
*B 5517,Global Add to new areas
 GLOBAL ADD TO NEW AREAS                                ^Index^
 ────────────────────────────────────────────────────────────

 If you  wish this  system to be added to all new areas, then
 set this field to Yes.  Note that the node will only be auto
 added  if it  is in  the same  domain as  the  system  which
 "created" the new area.
*E
*B 5518,Global Notify
 GLOBAL NOTIFY                                          ^Index^
 ────────────────────────────────────────────────────────────

 This flag indicates whether or not the specified node should
 receive NOTIFY messages.  By default,  this is  set  to Yes,
 indicating  that  the  system  will  receive a  notification
 message from IMALNK.
*E
*B 5519,Global Remote Maintenance
 GLOBAL REMOTE MAINTENANCE                              ^Index^
 ────────────────────────────────────────────────────────────

 IMAIL may allow systems to  carry  out  changes in the links
 for other systems. These changes may be  made  via AreaLink,
 using the %FROM meta-command.

 In order to enable a node  to  make  these changes for other
 systems, this field must be set to 'Y'; the default is 'N'.

 Remote Maint also allows the system to delete  an echo  area
 from your list,  or to change the name of  an  area. It thus
 allows a lot of control over your system.
*E
*B 5520,Global FSC-0057 Compatible
 GLOBAL FSC-0057 COMPATIBLE                             ^Index^
 ────────────────────────────────────────────────────────────

 This  flag  specifies  whether  this   system  is   FSC-0057
 compatible ( which  is only required  concerning  the remote
 delete, rename and create request).

 If such a function is executed on your system,  all affected
 downlinks are notified. If they are also FSC-0057 compatible
 and are not an uplink,  their AreaLink is also notified with
 a message.
*E
*B 5521,Global Alnkcheck Echo
 GLOBAL ALNKCHECK ECHO                                  ^Index^
 ────────────────────────────────────────────────────────────

 This feature of  IMAIL  allows to check  every  message from
 this system whether it is  a  message to Arealink ( to avoid
 for  example   exporting   an   Arealink   request  that  an
 unexperienced  points has  posted in  an echo).  Use it with
 care because it requires some time while tossing.
*E
*B 5522,Global Check PKT Password
 GLOBAL CHECK PKT PASSWORD                              ^Index^
 ────────────────────────────────────────────────────────────

 You can control the  use  of the previously specified packet
 password with the  help of  this switch.  If you set this to
 "N",  incoming  packets  are  not  checked  for  the  packet
 password,  while  outgoing packets ( those created by IMAIL)
 will contain the specified password.  Setting this switch to
 "Y",  IMAIL  will   only  process   packets  with   matching
 passwords.
*E
*B 5523,Global Alnk with '+'
 GLOBAL ALNK with '+'                                   ^Index^
 ────────────────────────────────────────────────────────────

 Here  you can  define  whether  IMALNK  prefixes  area  link
 requests  with a '+'.  As  the  areafix  functions  of  some
 programs  do not  accept a  preceeding '+',  you can disable
 this here.
*E
*B 5524,Global Send rules
 GLOBAL SEND RULES                                      ^Index^
 ────────────────────────────────────────────────────────────

 When you enable this switch,  IMALNK will send  the rules of
 an area to this system  when it links an  area for the first
 time (not  on  update  requests).

 This IMALNK area  rules support  function will  only work if
 the global rules path  is defined and if  the file  name for
 the area  rule also is  defined in the  area record  for the
 area.  IMALNK will  add the  text  header IMRULE.HEA  if  it
 exists  in the  IMAIL  home  directory.  If no rule  name is
 defined in  the  area record  or if the rule  file cannot be
 found,  IMALNK will send IMNORULE.HEA which is also expected
 in the IMAIL home directory.
*E
*B 5530,Global node fields
 GLOBAL NODE FIELDS                                     ^Index^
 ────────────────────────────────────────────────────────────

 Here you  can global add,  delete or replace a group  in the
 records of the Node Manager.

 The changes will be made  on a  per-node base.  Nodes may be
 specified also using  the wildcard '*' and the modifications
 will be made for all nodes matching the entered sheme.
*E
*B 5531,Global Pkt Origin Address
 GLOBAL PKT ORIGIN ADDRESS                              ^Index^
 ────────────────────────────────────────────────────────────

 Here you  can configure  one of  the  system  akas as  fixed
 origin address for the packets created for this system. Also
 the origin  address  of the area can be  used,  which is the
 default setting.  This feature allows to use always the same
 aka when sending packets to a specific system.

 Note that the  address specified here is  only used  for the
 *.PKTs;  this has nothing to do with the single mails or the
 sender of the compressed file (the ARCmail-bundle).
*E
*B 5532,Global Message Status
 GLOBAL MESSAGE STATUS                                  ^Index^
 ────────────────────────────────────────────────────────────

 This  switch  controls the  default status  of messages from
 IMALNK or IMTHINGS have created to your links. It may be:

        Normal              No Status
        Hold                Hold message for pick up
        Crash               Send message 'crash'
        Direct              Send message directly
        Immediate           Set the 'Immediate' flag

 See also: ^Global Attach Status^
*E
*B 5533,Global Attach Status
 GLOBAL ATTACH STATUS                                   ^Index^
 ────────────────────────────────────────────────────────────

 With  this  switch,  you  control  the default status of the
 attaches for the ARCmail-bundles to your links. It may be:

        Normal              No Status
        Hold                Hold message for pick up
        Crash               Send message 'crash'
        Direct              Send message directly
        Immediate           Set the 'Immediate' flag

 See also: ^Global Message Status^
*E
*B 5534,Global Packer
 GLOBAL PACKER                                          ^Index^
 ────────────────────────────────────────────────────────────

 Here you will be able  to select the program to use for mail
 compression. A list will appear, containing the programs you
 defined in the "Compression Programs" menu.

 See also: ^Packer^
*E
*B 5535,Global Capability
 GLOBAL CAPABILITY                                      ^Index^
 ────────────────────────────────────────────────────────────

 The Capability describes the other  system's mail processor.
 Currently, two types are defined:

         Stone Age
         Type 2+

 You  can set this field  according to  the capability of the
 remote system's mail processor, if known.
 If you are unsure, leave the field set to "Stone Age".

 See also: ^Capability^
*E
*B 5536,Global CW Handling
 GLOBAL CW HANDLING                                     ^Index^
 ────────────────────────────────────────────────────────────

 This field allows you to  define  how  IMAIL  will  use  the
 setting  defined  in  the  Capability  field  when  handling
 inbound mail. Possible choices:

        Force
        Auto

 See also: ^CW Handling^
*E
*B 5537,Global Program name
 GLOBAL PROGRAM NAME                                    ^Index^
 ────────────────────────────────────────────────────────────

 This is the name of the AreaLink used by this system.  It is
 used by Arealink when forwarding  delete,  create or  change
 requests to the systems linked to a certain echo.
*E
*B 5538,Global Node Domain
 GLOBAL NODE DOMAIN                                     ^Index^
 ────────────────────────────────────────────────────────────

 Here you can select the domain to which the system  belongs.
 This is  very important in  multi-domain  environments,  and
 when  you  have  different  outbound  directories  for  each
 domain.  Select the domain from  the list presented.  If the
 system belongs to  a domain which is not listed,  you should
 define it in the Domains menu.
*E
*B 5540,Global digit fields
 GLOBAL DIGIT FIELDS                                    ^Index^
 ────────────────────────────────────────────────────────────

 Here you  can global add,  delete or replace a group  in the
 records of the Node Manager.

 The changes will be made  on a  per-node base.  Nodes may be
 specified also using  the wildcard '*' and the modifications
 will be made for all nodes matching the entered sheme.
*E
*B 5541,Global Area Security
 GLOBAL AREA SECURITY                                   ^Index^
 ────────────────────────────────────────────────────────────

 The  value you  enter here  corresponds  directly  with  the
 fields ^Read/Write Security^  in the  area record. Here, you
 can  assign a  certain  security  level to  the  node  which
 controls which areas he/she can link.
 Apart from the groups,  this is a useful feature to restrict
 access to areas.
*E
*B 5542,Global max. Arcmail size
 GLOBAL MAX. ARCMAIL SIZE                               ^Index^
 ────────────────────────────────────────────────────────────

 Setting this to a  non-zero  value tells  IMCOMP  not to add
 further arcmail PKTs to a  compressed  ARCmail bundle if its
 size is bigger  than  specified ( in kB).  IMCOMP  will then
 create a  new bundle. Using  this feature you  can limit the
 size of the arcmail  bundles and therefore reducing the time
 which is  needed to transfer the bundle  again  if a session
 was interrupted.
*E
*B 5543,Global Max. Packet Size
 GLOBAL MAX. PACKET SIZE                                ^Index^
 ────────────────────────────────────────────────────────────

 With this option, you can specify the  maximum  size  of the
 packet files (*.PKT) that  IMAIL  will  create.  Use this if
 your up and/or down  links  are  short  on  disk space.

 The number should indicate a size  in  kilobytes.  If a zero
 (0) is specified, there will be no limit imposed.
*E
*B 5544,Global Pack Priority
 GLOBAL PACK PRIORITY                                   ^Index^
 ────────────────────────────────────────────────────────────

 This field  controls the  order in  which the tossed mail is
 compressed for the nodes. You can specify a  value between 0
 and 9. Nodes who have a "9"  will have their mail compressed
 first. This is useful for nodes who have a separate computer
 for  TOSSing and  whose  downlinks use  to call  immediately
 after the poll to the uplink. By this,  you can compress the
 mail for the pesters first.
*E
*B 5545,Global PKTs To Pack Per Call
 GLOBAL PKTS TO PACK PER CALL                           ^Index^
 ────────────────────────────────────────────────────────────

 Together with  'Max. Arcmail Size', this  field controls the
 size of the outgoing ARCmail bundles.

 When set to  0,  IMCOMP will add  _all_  pending PKTs  to an
 existing ARCmail bundle or creating one single bundle.

 Setting  this  field to a  non-zero value,  IMCOMP will only
 process this number  of PKTs per call,  then again check the
 size of the created ARCmail bundle.
*E
*B 600,Group Manager
 GROUP MANAGER                                          ^Index^
 ────────────────────────────────────────────────────────────

 The Group Manager has two functions. It allows you to assign
 descriptions to  the various groups  which  can  be accessed
 from the  ^Area Manager^ and  from the  ^Node Manager^. Moreover
 you can define the  default settings which should be used if
 a new area arrives and is automatically created by IMAIL.

 You can assign each system  which is allowed to create areas
 a "New area group". Each area  created by  this  system will
 get this group and the defaults of  this group as defined in
 the Group Manager.
*E
*B 6101,Group Description
 GROUP DESCRIPTION                                      ^Index^
 ────────────────────────────────────────────────────────────

 Here you can enter a short description of the group,  it  is
 used when you select groups in the ^Area Manager^.

 See also: ^Group Manager^
*E
*B 6102,Group Secure
 GROUP SECURE                                           ^Index^
 ────────────────────────────────────────────────────────────

 If enabled, IMAIL will check the address of the system which
 sent  the  message in  this area.  If it is among the export
 nodes listed  in  the Export List, it  will be  imported and
 processed;  otherwise,  it will  be  tossed  into  your  Bad
 Message Board.

 Note that the sender's address  will be determined using the
 PKT-address, not the address stated in the origin line.

 If this  switch  is set to  N, IMAIL will  also  ignore  the
 export only flag in the list of linked systems.

 See also: ^Group Manager^
*E
*B 6103,Group Msgbase
 GROUP MSGBASE                                          ^Index^
 ────────────────────────────────────────────────────────────

 This feature allows you to control the areatype a  new  area
 gets:

 Passthrough, Hudson, Jam, Squish or *.MSG.

 See also: ^Messagebase Path^ ^Group Manager^
*E
*B 6104,Group Boards
 GROUP BOARDS                                           ^Index^
 ────────────────────────────────────────────────────────────

 These two fields are for people who prefer their hudson base
 to be structured.  You can specify a  range of board numbers
 the new area  should be  assigned to.  IMAIL will  chose the
 lowest board possible.  If no board  can be assigned  in the
 given range,  IMAIL will take the first board from the whole
 base.

 See also: ^Group Manager^

*E
*B 6105,Group Path
 GROUP PATH                                             ^Index^
 ────────────────────────────────────────────────────────────

 If you speciefied a *.MSG, Squish or JAM styled Message Base
 you can set here the default path,  where IMail  will create
 the new message area.

 See also: ^Group Manager^
*E
*B 6106,Group Days
 GROUP DAYS                                             ^Index^
 ────────────────────────────────────────────────────────────

 This  item is  used by  IMTHINGS KILL /U  to determine which
 messages to kill: it will mark as deleted any messages older
 than the  number of days  specified here.  If this  field is
 left  at  zero,  no  messages  will be  killed,  unless  the
 "# Msgs" field below is specified.

 The maximum value which can be entered in this field is 255.
 If the  area is  marked as  Passthrough,  this field  has no
 meaning (kinda obviously).

 See also: ^Msgs^ ^Group Manager^
*E
*B 6107,Group Msgs
 GROUP MSGS                                             ^Index^
 ────────────────────────────────────────────────────────────

 This is used  by  IMTHINGS  KILL  /U  to determine  how many
 messages to  leave  in  this board. If this field is left at
 zero,  it  will  be ignored, and no messages will be killed,
 unless  the  "# Days" field is specified.

 Naturally,  if the area is  Passthrough,  this field  has no
 meaning.

 See also: ^Days^ ^Group Manager^
*E
*B 6108,Group Hidden
 GROUP HIDDEN                                           ^Index^
 ────────────────────────────────────────────────────────────

 Enable this  option if this area should not be  displayed in
 any AreaLink report of available areas.  Moreover  it cannot
 be linked  with a  wildcard request.  It can only  be linked
 when explicitly stating the full areatag.

 See also: ^Group Manager^
*E
*B 6109,Group Autounlink
 GROUP AUTOUNLINK                                       ^Index^
 ────────────────────────────────────────────────────────────

 If this option  is set to 'N'  the unlink check  is disabled
 for this area,  so it will remain linked to your system even
 when it is no more wanted by you or your downlinks.

 See also: ^Group Manager^
*E
*B 6110,Mandatory
 MANDATORY                                              ^Index^
 ────────────────────────────────────────────────────────────

 If you set this field to yes,  no  downlink can  unlink from
 this area using  the AreaLink  functions.  This  can only be
 done manually. This field  is  useful  when  you really want
 an area to be read.

 See also: ^Group Manager^
*E
*B 6111,Read only
 READ ONLY                                              ^Index^
 ────────────────────────────────────────────────────────────

 If this option is enabled,  every  system  linking this area
 gets an export only  flag  (which  can  be  removed manually
 by the  sysop).  This  flag prevents unauthorized  downlinks
 from  posting messages in restricted (read only) areas.

 See also: ^Group Manager^
*E
*B 6112,Group Tiny SB
 GROUP TINY SB                                          ^Index^
 ────────────────────────────────────────────────────────────

 Enable this  option if  you want  to strip  all the  SEEN-BY
 information from  an  incoming  echo message  before  it  is
 re-exported.

 In this case,  the outgoing  message will  contain  only the
 SEEN-BYs of your  downlinks. Note, however, that if the area
 is not  marked as  passthrough,  and if  the Group Import SB
 option  (below)  is active,  the message  will be =imported=
 with the original SEEN-BY information.

 See also: ^Group Manager^
*E
*B 6113,Group Zonegate
 GROUP ZONEGATE                                         ^Index^
 ────────────────────────────────────────────────────────────

 This field is  imilar to the Group Tiny SB field (above). It
 indicates that IMAIL  should strip  all information from the
 SEEN-BY  line  when  exporting  to a  system  which  is in a
 different zone,  except for  your address  and  that  of the
 downlink. Currently,  zonegating only works with ONE node in
 the other zone,  because the new SEEN-BY's will only contain
 your own and the destination address.

 Note that when the message is  imported in your message base
 (if the area is not passthrough) the  original SEEN-BY lines
 will be preserved.

 See also: ^Group Manager^
*E
*B 6114,Group Import SB
 GROUP IMPORT SB                                        ^Index^
 ────────────────────────────────────────────────────────────

 This switch controls whether the SEEN-BYs  are imported into
 the message base or whether they are stripped.

 See also: ^Group Manager^
*E
*B 6115,Group Hide SB
 GROUP HIDE SB                                          ^Index^
 ────────────────────────────────────────────────────────────

 If this switch  is set to Yes,  IMAIL puts a CTRL-A in front
 of every SEEN-BY  line. This is useful for the BBS  software
 which should not display these hidden SEEN-BYs to the normal
 users then.

 See also: ^Group Manager^
*E
*B 6116,Group No %PAUSE
 GROUP NO %PAUSE                                        ^Index^
 ────────────────────────────────────────────────────────────

 This setting can be used with  important areas.  By default,
 your downlinks can prevent echo mails being exported to them
 using the %PAUSE  meta-command  with Arealink.  If you don`t
 want information in  important areas to pass your downlinks,
 you can inhibit the pausing of an area with this switch.

 See also: ^Group Manager^
*E
*B 6117,Group Dupecheck
 GROUP DUPECHECK                                        ^Index^
 ────────────────────────────────────────────────────────────

 This switch can be used to advise IMAIL not to  perform dupe
 checking  on an  area.  This increases  the speed  of TOSS a
 little, but increases the risk of dupes noticeably.

 See also: ^Group Manager^
*E
*B 6118,Group Kill dead
 GROUP KILL DEAD                                        ^Index^
 ────────────────────────────────────────────────────────────

 IMAIL allows  you to delete  areas without  traffic  after a
 definable number  of days.  During the midnight  maintenance
 IMAIL marks areas without traffic.

 A value of 0 disables this function,  the maximum  number of
 days is 256. Single areas can  also  be  excluded by setting
 the field Autounlink in the ^Area Manager^ to 'N'.

 Dead areas  are marked  in the  ^Area Manager^,  do not forget
 that this check is only done during midnight maintenance and
 the ^Area Manager^ shows only full days.

 See also: ^Group Manager^
*E
*B 6119,Group kill on the fly
 GROUP SQUISH KILL ON THE FLY                           ^Index^
 ────────────────────────────────────────────────────────────

 This switch  controls  whether  or not  IMAIL should use the
 Squish 'kill on the fly' - function in created areas.
 Of course, this switch will only  affect areas that  are set
 to 'Squish'.

 CAUTION! Using this function will slow down TOSS noticeably!

 See also: ^Group Manager^
*E
*B 6120,Group Dupecheck on Msgid
 GROUP DUPECHECK ON MSGID                               ^Index^
 ────────────────────────────────────────────────────────────

 IMAIL has two ways of checking for Dupes:

 Either it  calculates the  crc  header  sum or it checks the
 MSGID.  Especially in gated areas,  dupes occur with changed
 headers, but identical MSGID.  For these areas,  you can set
 this switch  to 'Y'.  IMAIL  will then  check  every  single
 incoming  Msg in  this area  against the  MSGID's  stored in
 IMAIL.DP.  Not finding  it there,  the  header crc  will  be
 checked afterwards.

 See also: ^Group Manager^
*E
*B 6121,Group manual
 GROUP MANUAL                                           ^Index^
 ────────────────────────────────────────────────────────────

 This switch  provides  another  bit of security  for you. It
 prevents  an  area  from   automatic  access  via  Arealink.
 Downlinks can only be linked to this area manually.  This is
 very useful when handling restricted or adultonly areas.

 This setting can serve as the counterpart to 'Mandatory'.

 See also: ^Group Manager^
*E
*B 6122,Group Read Security
 GROUP READ SECURITY                                    ^Index^
 ────────────────────────────────────────────────────────────

 Here you define the Security Level a System must have to get
 read access for this area/group.

 See also: ^Group Write Security^   ^Group Manager^
*E
*B 6123,Group Write Security
 GROUP WRITE SECURITY                                   ^Index^
 ────────────────────────────────────────────────────────────

 Here you define the Security Level a System must have to get
 write access for this area/group.

 See also: ^Group Read Security^    ^Group Manager^
*E
*B 6124,Group Origin Address
 GROUP ORIGIN ADDRESS                                   ^Index^
 ────────────────────────────────────────────────────────────

 Here you can choose the address to use in the Origin line of
 the message.
    
 This address  will also be used in the PATH line of the echo
 message, as well as in the list of SEEN-BYs.

 Note that  only the  net and  node numbers will be placed in
 the  SEEN-BYs  and PATH  lines; the  use of  zone and  point
 numbers is not accepted.

 See also: ^Group Manager^
*E
*B 6125,Group Seen-Bys
 GROUP SEEN-BYS                                         ^Index^
 ────────────────────────────────────────────────────────────

 This field pops up a window that allows you to choose one or
 more addresses to add to the SEEN-BY line for that area.
    
 See also: ^Group Manager^
*E
*B 700,Forward Manager
 FORWARD MANAGER                                        ^Index^
 ────────────────────────────────────────────────────────────

 Forward  Link  Requests  are  a   method   to   have   IMAIL
 automatically request  areas  from  your  area  uplinks.  If
 AreaLink processes a request for an echo area which  is  not
 listed in your configuration, it will search the  files  you
 have defined for this area. If found, it will send a request
 for that area to  the system listed.  Beside this, the lists
 defined are  also used  to determine  the description  of an
 area.  You can define  two groups (create  group and  access
 group).  The create  group is  assigned to the  new area and
 from which some defaults are taken. The access group is used
 to control the access to that forward entry.

 ...
*P
 FORWARD MANAGER                                        ^Index^
 ────────────────────────────────────────────────────────────
 ...

 To use more than one forward list, you can have more than
 forward entry for one uplink each with a different forward
 list and different group settings.

 ! Note that the requester and the Uplink have to belong
 ! to the same domain.

 See also: ^Forward Manager Keylist^
*E
*B 701,Forward Manager Keylist
 FORWARD MANAGER KEYLIST                                ^Index^
 ────────────────────────────────────────────────────────────

 Available keys:

 <ENTER>      Edit               <F1>         Help
 <ESC>        Exit w/o save      <F10>        Save and Exit
 <INS>        Add Record         <DEL>        Delete Record
 <HOME>       First Record       <END>        Last Record
 <CRSR UP>    Previous Record    <CRSR DN>    Next Record
*E
*B 7001,Uplink Address
 UPLINK ADDRESS                                         ^Index^
 ────────────────────────────────────────────────────────────

 This is the network  address of the uplink to where the link
 request for areas  in the  associated taglist  are adressed.
 This item will also allow you  to take over the password and
 the create group from the ^Node Manager^ record of the system.
*E
*B 7002,Uplink Name
 UPLINK NAME                                            ^Index^
 ────────────────────────────────────────────────────────────

 This item shows  the sysop  name of  the link  if it  can be
 found in the node database. If you select this item, you get
 a list of all systems defined in  the node database  and can
 select one of them.  This will overwrite the  uplink address
 and will allow you to take over the password  and the create
 group from the ^Node Manager^ record of the selected system.
*E
*B 7003,Areas file
 AREAS FILE                                             ^Index^
 ────────────────────────────────────────────────────────────

 This is the  file name of an Fidonet.na-type file containing
 the list of echo areas available on that system. IMALNK will
 search through the  list when a downlink requests an unknown
 area if

    - this downlink may initiate forward requests and
    - he has access to the access group specified later.

 If the requested area can be found, IMAIL will initiate a
 forward request and create the area in the area database
 using the description from the list (if found) and the
 defaults from the create group.
 ...
*P
 AREAS FILE                                             ^Index^
 ────────────────────────────────────────────────────────────
 ...

 This file is  expected in  the directory  pointed to  by the
 IMAIL environment variable.

 The format of the Fidonet.na file is:

       <AREATAG>    <DESCRIPTION>
*E
*B 7004,Send to
 SEND TO                                                ^Index^
 ────────────────────────────────────────────────────────────

 It defines  the name of the programm that should process the
 arealink request  messages at the uplinks system.  This name
 is  put in  the TO: field  of  automatic  arealink  messages
 created by  IMAIL and IMALNK.  Names  that usually  work are
 AreaMgr, AreaFix or the name of the program the uplink uses.
*E
*B 7005,Password
 PASSWORD                                               ^Index^
 ────────────────────────────────────────────────────────────

 The  password your  uplink requires  for processing arealink
 messages.  IMAIL writes  this pasword  in the SUBJ: field of
 the created messages to the arealink program for the uplink.
*E
*B 7006,Access Group
 ACCESS GROUP                                           ^Index^
 ────────────────────────────────────────────────────────────

 In order to  initiate a forward request  to this uplink, the
 requesting system  needs access to this group.  By this, you
 have another method of  dynamically assigning rights to your
 downlinks.  When empty,  every  downlink can  invoke forward
 requests from this uplink.
*E
*B 7007,Create Group
 CREATE GROUP                                           ^Index^
 ────────────────────────────────────────────────────────────

 This group is used to create new requested areas means the
 new area will belong to this group. IMALNK will also take
 over the defaults defined in the ^Group Manager^ for this
 group. When it is left empty, the new area will be assigned
 to the new area group entered in the ^Node Manager^ of the
 uplink where the area is requested from.

 The versability  of this setting  turnes out  when you enter
 different group:  you can assign an own group to areas which
 have been sent to you by your uplink without being requested
 by a downlink (they are assigned to the group entered in the
 ^Node Manager^) from those which have been requested from your
 system (they are assigned to this group).
*E
*B 800,Pack Routing
 PACK ROUTING                                           ^Index^
 ────────────────────────────────────────────────────────────

 In this menu you may specify  default routing for IMPACK; in
 other words, you may  specify that net mail  for one or more
 systems  be  compressed  in a  packet  addressed  to another
 system,  from  which  (presumably)  the  mail  will  be for-
 warded on.
 This can result in a great  speedup in the  handling of your
 netmail folder...
*E
*B 8000,Route Description
 ROUTE DESCRIPTION                                      ^Index^
 ────────────────────────────────────────────────────────────

 The screen  is composed  of two  "Pack  Via Nodes"  columns,
 which indicate  the nodes via which net mail will be routed.
 For reasons of space,  the routed  nodes and  exceptions are
 not shown unless the appropriate function key is pressed.

 To edit these entries,  position the  cursor on  the desired
 row and press ENTER or simply  press the character preceding
 the desired entry.
 You will then be able to edit the  "Route Via" address. Once
 finished,  you may  edit  the list  of  "Routed  System"  by
 pressing F2.  It is also  possible to  specify  one  or more

 ...
*P
 ROUTE DESCRIPTION                                      ^Index^
 ────────────────────────────────────────────────────────────
 ...

 "excepted systems" by pressing F3.

 If you want to insert new entries between  existing ones for
 reasons of  clearness,  do so  by pressing  INS,  and delete
 entries (permanently!) by pressing DEL.


 See also: ^Route via^
           ^Routed Systems^
           ^Excepted Systems^
*E
*B 8001,Route via
 ROUTE VIA                                              ^Index^
 ────────────────────────────────────────────────────────────

 Here you place the system,  which will route the netmail for
 the system, specified in ROUTED SYSTEMS.

 See also: ^Route Description^
           ^Routed Systems^
           ^Excepted Systems^
*E
*B 8002,Routed Systems
 ROUTED SYSTEMS                                         ^Index^
 ────────────────────────────────────────────────────────────

 Here you  specifie all systems,  which will route to the via
 node, speciefied under ROUTE VIA.

 IMSETUP supports  the use of the  "*"  macro when specifying
 the "Routed Systems". This macro may be used in place of the
 net, node or point fields (the zone should always be given).

 For example:

 2:*                   All net  mail  messages  addressed  to
                       systems in Zone 2

 ...
*P
 ROUTED SYSTEMS                                         ^Index^
 ────────────────────────────────────────────────────────────
 ...

 2:2480/*              All net mail messages addressed to the
                       nodes in Zone 2, Net 2480
 2:2480/100.*          All net mail messages addressed to the
                       points  of  node  2:2480/100. This  is
                       equivalent to:

 See also: ^Route Description^
           ^Route via^
           ^Excepted Systems^
*E
*B 8003,Excepted Systems
 EXCEPT SYSTEMS                                         ^Index^
 ────────────────────────────────────────────────────────────

 If you use the '*' macro in  ROUTED SYSTEMS like '2:*',  you
 can place here exceptions of this routing.

 Example:       Route Via:        2:2480/55
                Routed Systems:   2:*
                Excepted Systems: 2:245/* 2:242/*

 See also: ^Route Description^
           ^Route via^
           ^Routed Systems^
*E
*B 900,Import/Export Functions
 IMPORT/EXPORT FUNCTIONS                                ^Index^
 ────────────────────────────────────────────────────────────

 This menu helps you to Import / Export some configurations

 See also: ^Export Areas.Bbs^
           ^Export GoldED Areafile^
           ^Export FidoNet.Na^
           ^Export timEd Areafile^
           ^Import Areas.Bbs^
*E
*B 901,Select Groups
 SELECT GROUPS                                          ^Index^
 ────────────────────────────────────────────────────────────

 Here you can select the groups which should be included into
 the exported file by accessing the  ^Group Manager^. It allows
 you to select certain groups easy.

 <ENTER>/<SPACE> to select/deselect single groups
 <INS>/<DEL>     to select/deselect all groups
 <F10>           to accept the selection
 <ESC>           to return to the export/import menu
*E
*B 9000,Export Areas.Bbs
 EXPORT AREAS.BBS                                       ^Index^
 ────────────────────────────────────────────────────────────

 Here you can create a standard  Areas.Bbs file, IMSETUP will
 ask you for the name of the file.

 See also: ^Import/Export Functions^
*E
*B 9100,Export GoldED Areafile
 EXPORT GOLDED AREAFILE                                 ^Index^
 ────────────────────────────────────────────────────────────

 This function  creates an  include file  for GoldED and uses
 already the enhanced format (up from GoldED 2.41).

 See also: ^Import/Export Functions^
*E
*B 9200,Export FidoNet.na
 EXPORT FIDONET.NA                                      ^Index^
 ────────────────────────────────────────────────────────────

 This  function  creates  a standard  FidoNet.na  file  which
 contains the area tag and the description.

 See also: ^Import/Export Functions^
*E
*B 9300,Export timEd Areafile
 EXPORT TIMED AREAFILE                                  ^Index^
 ────────────────────────────────────────────────────────────

 This function  creates an  include file for  timEd.  You can
 include  this  file  via  the   command  'INCLUDE'  in  your
 'timed.cfg' configuration file.

 See also: ^Import/Export Functions^
*E
*B 9400,Import Areas.Bbs
 IMPORT AREAS.BBS                                       ^Index^
 ────────────────────────────────────────────────────────────

 Here,  you  can import a standard  Areas.Bbs file  into your
 area database. The actual area database will be deleted.

 See also: ^Import/Export Functions^
*E
*B 999,Exit to Dos
 EXIT TO DOS                                            ^Index^
 ────────────────────────────────────────────────────────────

 If you want to exit IMSETUP, you can choose this menu entry.
*E
