Page 1             TrapToss' Fantastic Manual              Page 1

















                                 TrapToss
                       The Real Amiga Packet Tosser
                               Version 1.50
                          Copyright (c) 1989-1993
                                 René Hexel
                            All rights reserved





                        TrapToss' Fantastic Manual
                                26 Mar 1993
                          Copyright (c) 1990-1993
                       René Hexel, Maximilian Hantsch
                            All rights reserved








                  This manual is intended to be read from
                    front to back for more convenience.


















     Page 2             TrapToss' Fantastic Manual              Page 2


  1. Introduction     

       This manual is a brief description of TrapToss Amiga,
     explaining how to set up the software in order to run a FidoNet
     compatible Node or Point System.  Please refer to the
     documentations of TrapDoor and Chameleon for additional
     information on Area bases, packet transfer, modems and other
     topics not discussed here. If you are not familiar with FidoNet
     or the Node/Point concept, please read FidoNet.Man first.  

       Please read the entire manual before using TrapToss.  

       TrapToss is a FidoNet compatible mail processor for Amiga
     systems. It has been designed to combine high performance and
     compatibility to existing software. You can use TrapToss to run
     a simple Point system as well as a complex, sometimes tricky
     Node setup. It will import messages from other systems to local
     message Areas and export messages from your Areas to other
     systems using FTS-0001 compatible packets and compressed Mail
     bundles. It handles both public EchoMail Areas and private
     Netmail (sometimes called Matrix Mail in this manual).  

       In a typical Point setup, TrapToss will merely replace older
     products like ConfMail and oMMM for the Amiga. In a Node
     environment, however, things may become a bit more complex...  







  2. Basics     

       TrapToss is a CLI based application, it cannot be run from
     Workbench. It accepts a wide range of keywords that allow easy
     and accurate configuration.  TrapToss supports the *new and
     improved* Global Configuration File standard (as used by
     programs like TrapList, TDSched and soon TrapDoor), thus
     enabling easy single-file configuration for a variety of FidoNet
     compatible applications.  

       Please note that the keywords are neither case sensitive nor
     -- with a few exceptions -- position dependent.  












     Basics


     Page 3             TrapToss' Fantastic Manual              Page 3


  3. Installation     

       Copy the executable and the key file to your harddisk or
     floppy drive.  Make sure that the key file is placed somewhere
     accessible through the path when TrapToss is executed. Then copy
     the supplied 'TrapToss.Cfg' file to your FidoNet base directory
     -- you need to assign 'MAIL:' to this directory before running
     TrapToss.  

     TrapToss will search for the configuration file in the current
     directory, i.e.  where the program has been started from, or in
     the 'MAIL:' directory. You may either call it 'Fido.Cfg' (for
     GCF compatibility) or 'TrapToss.Cfg' if you do not want to share
     the configuration file. In case you do not like any of those,
     use 'CONFIG <filename>' as described in the reference section to
     specify your own configuration file name.  

       If you do not possess a Keyfile, TrapToss will pop up a
     Requester each time it is started and will inform you of the
     concepts of ShareWare. You are requested to register your copy
     of TrapToss within a few weeks' evaluation period. For
     instructions and information about registration, see below.  

       Do not forget to assign 'MAIL:' to your FidoNet 'root'
     directory. Then configure the tosser as described in the next
     chapter. You may then use TrapToss for importing/exporting your
     FidoNet messages.  





























     Installation


     Page 4             TrapToss' Fantastic Manual              Page 4


  4. Configuration     

       There are two ways of configuring TrapToss. You can set up a
     Point system or a more complex Node system. For an exhaustive
     description of Nodes and Points, please have a look at
     'FidoNet.Man'.  

       The most important part of your Fido configuration is your
     system's FidoNet address (simply referred to as 'Address' from
     now on). An Address consists of four parts, the Zone, the Net,
     the Node and the Point (again: for a detailed description,
     please see 'FidoNet.Man'). The Point part of your Address is
     zero if you are a Node, non-zero if you are a Point.  

       Usually you cannot just use any Address you like; you are
     assigned one instead. This is either done by your Boss (if you
     are a Point) or by the Network-Coordinator (NC) for Nodes.  

  4.1. Specifying your Address   

       TrapToss needs to know the Address of your system, so you have
     to specify it in the GCF (Global Configuration File). Therefore
     'NODE' is one of TrapToss' few compulsory keywords. Here are two
     examples for valid Addresses: 

          NODE 2:310/6.4
          NODE 2:203/602

       The first line is a typical Point Address while the second
     line contains a Node Address with the Point part left out (and
     therefore implicitly assumed zero).  

  4.2. Fake and PointNet Addresses  

       For historical reasons even now many systems do not fully
     implement or support the 4 dimensional addressing. That means
     that many Mailers/Tossers do only support 3 dimensional Fido
     Addresses (without the Point part) or even only 2 dimensional
     Addresses (Net and Node parts only).  

       In order to support Point systems anyway, so called PointNet
     or FakeNet Addresses have been introduced. These Addresses fake
     Node Addresses for Points and therefore trick this oldstyle
     software into processing mail from Points, too.  

       Therefore, if you are a Point your Boss Node will tell you his
     FakeNet (or PointNet) Address. Specify this fake Address
     directly after the 'NODE' statement in your config file, like
     this: 

          NODE 2:310/6.4
          FAKE 3160/4

       In this case your fake Address is 3160/4. Should your Boss


     Configuration                        Fake and PointNet Addresses


     Page 5             TrapToss' Fantastic Manual              Page 5


     only tell you his PointNet number, you have to compose a fake
     Address yourself: let's say your Boss told you that your Address
     is 2:345/67.8 and his PointNet is 4711. Your configuration will
     then look like this: 

          NODE 2:345/67.8
          FAKE 4711/8

       As you can see, your fake Address consists of the PointNet
     number your Boss told you plus the Point part of your main
     Address.  

       Unlike Points, Nodes are 'real' and should not specify any
     FAKE Address.  In order to support Point systems, they can
     specify their PointNet.  This number will then be used by
     TrapToss to automatically translate fake Point-Addresses to
     'real' 4D-Addresses.  

       To stress the above example again, if you're the Boss of the
     above Point, your main Address is 2:345/67, your PointNet is
     4711.  Use the TrapToss POINTNET statement for your setup: 

          NODE 2:345/67
          POINTNET 4711

        Unlike FAKE, POINTNET does not need any Node part; it is just
     a number TrapToss will use for translating Addresses. Points
     should not specify any POINTNET in their configuration; in other
     words, it's as easy as this: Points use FAKE, Nodes use
     POINTNET.  

  4.3. Inbound and Outbound Directories  

       Locally your messages are stored in single files in a number
     of different directories (Areas). This format is not very
     convenient for transmission via modem. Therefore different kind
     of packets and bundles exist for interchanging messages.  

       Translating from your local message base to outgoing mail
     bundles and vice versa is the main function of TrapToss. Packets
     you receive from other systems are stored in the Inbound
     directory (by TrapDoor or any other Mailer) until TrapToss
     processes them.  messages exported from your system will be
     packeted together in the Outbound directory, ready to be
     delivered by the Mailer.  

       Usually TrapToss assumes 'MAIL:Inbound' to be the Inbound
     directory and 'MAIL:Outbound' to be the Outbound directory. If
     you do not like this, you can change this using the 'INBOUND'
     and 'OUTBOUND' statements; for example: 

          INBOUND  "MAIL:MyInbound"
          OUTBOUND "MAIL:MyOutbound"



     Configuration                   Inbound and Outbound Directories


     Page 6             TrapToss' Fantastic Manual              Page 6


  4.4. Areas     

       In FidoNet two kinds of messages exist: private mail, which is
     only of interest for a single person, and public mail. Private
     mail is usually called Netmail (or Matrix Mail) and public mail
     is called EchoMail.  

       Netmail to and from your system is stored in a special
     sub-directory, the Netmail Area. In your configuration you have
     to specify the name of this sub-directory plus a name for the
     Area (this name is ignored by TrapToss, but may be used by some
     message editors); here is an example: 

          NETMAIL MAIL_DIR Mail:Matrix 

       This selects "Mail:Matrix" as the directory to be used for
     private Mail.  

       EchoMail (public mail) is grouped into several Areas. messages
     in certain Areas are usually restricted to certain topics and/or
     Nodes (information about this can usually be obtained from the
     rules posted by the moderator of an Area). Points should ask
     their Bosses for accessible Areas.  

       To configure Areas, both Points and Nodes have to specify AREA
     lines in their config files. The syntax is similar to the
     NETMAIL statement, but unlike NETMAIL you can specify multiple
     AREA lines.  Also unlike NETMAIL the name of the Area will be
     used by TrapToss.  You also have to specify which systems get
     messages written in the specified Area.  

       For Points this is your system and your Boss's. Here is an
     example (assuming your main Address is 2:310/6.4): 

          AREA TEST   MAIL:Echo/Test.Area   310/6.4 310/6
          AREA AMIGA  MAIL:Echo/Amiga.Area  310/6.4 310/6
          AREA CHAT   MAIL:Echo/Chat.Area   310/6.4 310/6
          etc.

       Please note that your Address has to be listed first, the
     Address of your Boss's system last. If your Boss tells you that
     certain Areas are read only, you should not attempt writing any
     messages there.  

       Nodes can specify several different kinds of Areas: 'normal'
     Areas, 'pass-through' Areas and 'read-only' Areas. 'Normal'
     Areas are simply Areas you receive from a certain Node (called
     the uplink Node for this Area) and pass on to zero or more other
     systems. 'Pass-through' Areas contain messages you pass on, but
     do not read yourself. Therefore you don't store these messages
     in your local message base (saving you time and harddisk space).
     Systems that have 'read-only' access will get messages from this
     Area, but are not allowed to write messages themselves. Here are
     a few examples (let's assume you're 2:310/6): 


     Configuration                                           Areas


     Page 7             TrapToss' Fantastic Manual              Page 7


          AREA TEST    MAIL:Echo/Test    310/6 310/6.1 310/6.3 310/6.4
          AREA AMIGA   MAIL:Echo/Amiga   310/6.1 310/6.3 310/6.4
          AREA INSIDER MAIL:Echo/Insider 310/6 310/7 310/6.1 310/6.2
          DISALLOW 310/7 310/6.1

       The first example shows a 'normal' Area which is received by
     your system, by 310/6.1, 310/6.3, and 310/6.4 (there is also a
     short form of specifying Addresses in an AREA statement, see the
     description of the Nodelist support features below for more
     information).  

       In the second example you can see a 'pass-through' Area that
     is exported to 310/6.1, 310/6.3, and 310/6.4, but not to your
     own system. The third example shows an Area that is marked
     'read-only' for 310/7 and 310/6.1: messages will be exported to
     these systems, but no incoming messages are allowed. Your system
     and 310/6.2, however, are allowed to write messages in the Area
     'INSIDER'.  

       Both Points and Nodes have to list at least one Area, the
     Bad-Message Area. This Area has to be listed as the first Area
     in the GCF (your config file). The name for this Area has to be
     'BAD' and you should list no Nodes for this Area (to prevent
     exporting messages from BAD). Here's an example: 

          AREA BAD Mail:Bad.Area

       Please note also, that you cannot specify AREA lines on the
     command line.  

  4.5. Reply Links    

       Usually messages in different Areas can be read in the order
     they arrive in. That means that you usually cannot stick to
     messages on a single subject first, and read messages about
     other subject afterwards.  

       Most editors, however, allow a 'threaded read mode', that is a
     mode where messages with the same subject can be read directly
     after each other (so you can complete a 'thread' before entering
     another). If your editor is capable of threaded messages, set
     LINKMSGS in your config file.  

  4.6. Compressed Mail    

       In order to reduce transfer time and telephone cost, mail
     packets can be compressed. The resulting bundles are called
     ARCMail bundles. Per default, TrapToss uses the ARC program for
     compressing (as the name ARCMail-bundle suggests), but you can
     also specify any Packer you like.  Here's a couple of examples: 

          PACKER "lha -x0 -X -f -u -m -P-1 -0 a" 310/30 310/70 310/90
          PACKER "MyPack a"                      310/9  310/19



     Configuration                                  Compressed Mail


     Page 8             TrapToss' Fantastic Manual              Page 8


       Please make sure you get in contact with the systems you set
     PACKER statements for (so they can correctly setup their
     software).  

       To unpack incoming bundles, you can specify default unpacker
     statements for various packer types. TrapToss currently knows
     Arc, Zoo, LHArc, Zip and Arj. You can also specify a 'general'
     unpacker for bundles TrapToss knows nothing about, for instance: 

          DEFAULTUNPACKERS "Pkax" "Zoo x:O" "Lha e" "UnZip -xnj" \
                           "UnArj e -y" "rx XArc e"

       Per default, TrapToss will use the ARC program to compress
     mail bundles, and automatically recognize and select the correct
     unpacker for decompressing mail bundles. (It knows about Arc,
     Zoo and LhArc.) You might want to use different archivers for
     some Nodes. Use the PACKER and UNPACKER statements for this
     purpose.  

  4.7. Adjusting Seen-By lines   

       Echomail messages contain special lines called the Seen-By
     lines. Seen-By lines are used by Tossers to determine which
     Nodes have already received a certain message and to prevent
     message looping. However due to fake Addresses Seen-By lines on
     systems may not be correct.  

       Points, for instance, if they do not exchange messages with
     their Bosses using 4D Addressing, have to strip their "real" 4D
     Address from their Seen-By lines. A simple 

          STRIPNODES 2:310/6.4

       will do, if your Address is 2:310/6.4. If your Boss uses
     TrapToss as well (or a 4D FroDo setup) you have to strip your
     fake Address instead. The 'STRIPNODES' keyword always affects
     *all* Areas.  

       Nodes, on the other hand, have to strip their Points'
     Addresses from the Seen-By lines (e.g. 'STRIPNODES 310/6.1
     310/6.2 310/6.3 310/6.4' if you feed the Points 1 to 4). For
     safety reasons you then should also strip your fake Address from
     the Seen-By lines by simply adding '3160/*' to the above
     command.  

  4.8. Wildcards     

       As you have seen, you also can specify so-called Wildcards or
     Jokers for 'STRIPNODES'. Basically Wildcards consist of an
     Address, where zero or more parts are replaced by '*' or '?'. A
     '?' simply means 'all of this item' (e.g.  2:310/? means 'all
     Nodes (Point=0) of Net #310 in Zone 2).  

       An asterisk not only means 'all of this item' but also 'and


     Configuration                                       Wildcards


     Page 9             TrapToss' Fantastic Manual              Page 9


     the rest'. So '*' simply means "everybody" (which is the same as
     ?:?/?.?). '2:*' means "everybody in Zone 2". So, for instance,
     2:310/* means "everybody in Net 310 of Zone 2, i.e. all Nodes
     *and* Points in Net #310). For a more detailed description of
     Wildcards see the corresponding chapter in the reference section
     of the manual.  

  4.9. Adjusting Seen-By lines Part 2 

       Nodes might consider it a good idea to simply say 'STRIPNODES
     310/6.* 3160/*'.  This has one negative side-effect: you strip
     yourself off the Seen-By lines! To prevent this from happening,
     you may add your Address to the Seen-By lines after stripping it
     using the 'ADDNODES' keyword. Its syntax is similar to
     'STRIPNODES', with the difference that no Wildcards are allowed
     there. For instance: 

          ADDNODES 2:310/6

       This will add the specified Addresses to the Seen-By lines
     *after* performing STRIPNODES.  

       So here is the full set of STRIPNODES and ADDNODES statements
     that a Boss Node supporting Points should use. In this example,
     the Boss is 2:310/6.  

          STRIPNODES 2:310/6.* 3160/*
          ADDNODES 2:310/6

  4.10. EchoMail ZoneGate    

       While we are at modifying the SEEN-BY lines... Suppose you are
     forwarding EchoMail to another Zone -- you have become a
     ZoneGate! 

       Unfortunately, this is a rather delicate topic and should be
     left to 'insiders' who know what they are doing. If at all
     possible, use the existing ZoneGates and let them forward the
     Areas for you.  

       Still, here is an example of how to use the ZONEGATE statement
     to work as a ZoneGate. Let us assume you are 2:253/140 and you
     are forwarding EchoMail to 1:140/90. You would need the
     following statement in your configuration file: 

          ZONEGATE 1:140/90 140/90 253/140 

     and he, 1:140/90, would need the statement 

          ZONEGATE 2:253/140 140/90 253/140 

       Then, close your eyes, hold your thumbs tight and wait for
     flames from all over the world. Good luck! :-) 



     Configuration                                EchoMail ZoneGate


     Page 10            TrapToss' Fantastic Manual             Page 10


  4.11. Duplicate Message Checking   

       TrapToss remembers some information about the last few
     thousand messages that it has seen. When such a message comes
     inadvertently back to your system (usually there is some error
     in the EchoMail topology that produces these duplicates),
     TrapToss will detect this and either discard the message or move
     it to your BAD message directory. It will also log this event in
     the logfile.  

       TrapToss uses a sophisticated duplicate detection scheme. When
     messages contain a MSGID control line (usually invisible in some
     message editors), TrapToss will use this MSGID for duplicate
     detection. When there is no MSGID line (some older systems do
     not generate MSGIDs), TrapToss will calculate a CRC of some of
     the header information of the message and use this CRC for
     duplicate detection.  

       TrapToss maintains two files for duplicate message detection,
     called Duplicate.Index and Duplicate.MsgID. These files are
     automatically generated in your MAIL: directory when you enable
     DupChecking with the 'DUPCHECK' keyword. You can influence the
     size of these files (and thus, the number of messages that
     TrapToss will remember back in time) using the 'DUPTABLESIZE'
     configuration keyword.  

       There is also a "small dupchecking" mode in TrapToss. When you
     enable 'SMALLDUPCHECK', TrapToss will search through your local
     message base to see if a message is already in there. It will
     not use the Duplicate.Index or Duplicate.MsgID files for
     dupchecking. This "small dupchecking" mode is slower than the
     full 'DUPCHECK' method, but it requires less disk and memory
     space.  























     Configuration                        Duplicate Message Checking


     Page 11            TrapToss' Fantastic Manual             Page 11


  4.12. Outbound Handling    

       To facilitate cooperation with a vast number of mailers,
     TrapToss supports a number of different outbound directory
     formats. You can choose between 2D and 4D handling of Netmail
     bundles, of EchoMail (arcmail) bundles, and of Flow files. The
     keywords (NO)FORCE4DMO, (NO)OLDSTYLEMO, (NO)OLDSTYLEFLO and
     (NO)OUT4D control this. Their defaults are set for perfect usage
     with the TrapDoor mailer.  

  4.13. Netmail Routing    

       If you are running as a Point system, this is easy. You route
     all your Netmail to your Boss. A simple 

          ROUTE NORMAL 2:310/6 * 

     does everything for you.  

       If you are preparing to run a Node, then good luck! This is
     probably one of the hardest things to explain, and apparently to
     understand, too.  

       You have to tell TrapToss where you want to route Netmail. You
     will also have to tell it what mail bundles should be sent out,
     and which should be kept "on hold" for other systems to call in
     and pick up.  

       The easiest way to get going is to find a system that will
     route Netmail for you. If you have someone splendid in your
     vicinity, and he agrees to do that, you simply send everything
     to him with a single 

          ROUTE NORMAL 2:310/11 * 

     statement. (In this example, 2:310/11 is the friendly site.)
     Then, as you slowly begin to get acquainted with the system, you
     can start adding other routing commands to your configuration
     file and see what happens to your mail.  

       There are four commands that deal with routing: POLL, CHANGE,
     SEND and ROUTE. You can have several of these commands in your
     configuration file.  First, all the POLL commands will be
     executed, then all the CHANGE commands. After that, the SEND and
     finally, the ROUTE commands will be processed. Within each group
     of commands, the statements will be executed in the order in
     which they appear in the configuration file.  

       What do these statements do and what can you achieve with
     them? 

       POLL: The idea of the POLL statement is to cause a certain
     Node to be called. It does this by creating an empty Flow file
     for that Node, unless there already exists one. Note that the


     Configuration                                  Netmail Routing


     Page 12            TrapToss' Fantastic Manual             Page 12


     flow file created will be of the 'Normal' type, so you might
     need an additional CHANGE statement to change the flavour of the
     Flow file to 'Crash'.  

       CHANGE: This statement changes the flavour of Flow files and
     Netmail bundles. Generally, all the files that TrapToss creates
     in the Outbound directory are of type 'Normal'. 'Normal' files
     indicate that no special method of sending out has been chosen
     for them, and they are usually sent out during ZMH
     automatically. Now there might be another Node that calls you
     regularly for his mail. So you won't want to send it to him, but
     rather keep his mail on 'Hold' for him. This is where the CHANGE
     statement comes in. With a simple 

          CHANGE NORMAL HOLD 2:310/42 

     all 'Normal' mail (and only 'Normal' mail) for 310/42 will be
     changed to status 'Hold'. Of course, you can change it back to
     'Normal' or even to 'Crash' later with another CHANGE statement.
     The CHANGE command also accepts wildcards. To keep mail for all
     your Points on 'Hold', use 

          CHANGE CRASH HOLD 2:310/6.* 2:3160/*
          CHANGE DIRECT HOLD 2:310/6.* 2:3160/*
          CHANGE NORMAL HOLD 2:310/6.* 2:3160/*

       SEND: is an abbreviation for often-used ROUTE statements.  

          SEND HOLD 2:310/42 2:242/25 2:281/100 

     is the same as 

          ROUTE HOLD 2:310/42  2:310/42.*
          ROUTE HOLD 2:242/25  2:242/25.*
          ROUTE HOLD 2:281/100 2:281/100.*

       Such statements are usually used to send mail for all Points
     of a Boss Node to the Boss Node, especially if you already have
     an EchoMail link with that Node.  

       ROUTE: This is the basic Netmail routing command. You pass it
     a list of "from"-Nodes, and a single "to"-Node where all the
     mail for the "from"-Nodes will be sent. The list of "from"-Nodes
     may even contain wildcards. Also, you tell it what flavour the
     resulting mail bundles should get. A simple example: 

          ROUTE CRASH 2:310/11 * 

     will route _all_ mail to 2:310/11, and will set the flavour to
     'Crash'.  






     Configuration                                  Netmail Routing


     Page 13            TrapToss' Fantastic Manual             Page 13


          ROUTE DIRECT 2:31/80 2:31/80.* 302/* 

       This means: route mail for all Points of 31/80 (and including
     mail for 31/80.0) plus all the mail for all Nodes and Points in
     Net 302 to the single Node 31/80. The mail will be of type
     'Direct', and thus, will be sent during ZMH.  

       Now we're getting tricky: What does 

          ROUTE DIRECT 2:?/0.0 2:* 

     do? Okay, it will take all mail to 2:* and route it to 2:?/0.0.
     Hm, but what does the wildcard '?' in the destination mean? This
     is a special feature of TrapToss: A wildcard in the destination
     of a route statement means that the wildcarded part of the
     destination Node number will be set to the corresponding part of
     the "from" Node number. I'll try to explain this example more
     properly: let's assume we have mail for 

          310/1 310/2 242/5 242/7 242/7.14 and 321/9 
          (all in Zone 2) 

     and I execute the above ROUTE statement. TrapToss takes the
     first mail (to 310/1) and goes through all the ROUTE statements,
     trying to find a matching "from"-Address field. It finds the
     2:*, and 2:310/1 matches. So it reads the destination of the
     route (2:?/0.0) and now replaces the wildcard '?' with the
     corresponding field of the current mail packet it is trying to
     route. Thus, the destination becomes 2:310/0.0. That is the
     Address where the mail packet will be routed. The same happens
     to the mail bundle to 310/2, it will be routed to 2:310/0.0 as
     well. Then, the three mail bundles to 242/5, 242/7 and 242/7.14
     will all be routed to 2:242/0.0. The final mail for 321/9 will
     be sent to 321/0. Guess what this was! We just performed a
     'HostRoute'-Statement, which other mail processors have as a
     separate routing command! We routed all mail bundles to their
     corresponding network Hosts! 

       Routing is really a complex topic. Don't try to get your
     routing straight at once. Start off with the simplest routing
     you can get along with, then slowly start adding more routing
     commands when you feel the system is performing as you wish.
     Take it easy. It sometimes even works.  

  4.14. Routing through a ZoneGate  

       Routing your Netmail through a ZoneGate is probably the
     fastest way to get messages through to other Zones. ZoneGates,
     however require a rather difficult to understand message
     addressing that is usually not available in your favourite
     message editor.  

       Using TrapToss' GATEROUTE statement this addressing can be
     done automatically for you. Just specify the Address of the


     Configuration                         Routing through a ZoneGate


     Page 14            TrapToss' Fantastic Manual             Page 14


     ZoneGate you want to route your messages through and the systems
     this routing should be performed for.  Here is an example
     (assuming you're part of Zone 2): 

          GATEROUTE 2/3 3:*
          GATEROUTE 2/5 5:100/* 5:200/*

       The first line is probably the form you will use: all Netmail
     messages to Zone 3 will be routed through the ZoneGate 2:2/3.
     The second form is an example of a more subtle selection: all
     messages to the Nets 100 and 200 in Zone 5 will be routed
     through the ZoneGate 2:2/5. All other Addresses in Zone 5 will
     be treated by your "normal" ROUTE statements.  

  5. Speeding up your System  

       In a FidoNet setup there are a lot of things that slow down
     the processing of mail. Here are a few hints that might help
     increasing the performance of your Point or Node. A major speed
     factor is the standard (FTS-1) message base used for FidoNet,
     which stores every message in a single file. This has always
     been a problem with Amiga FileSystems, because
     directory-scanning is rather slow.  

       However, if your system running is running Kickstart 3.0, like
     for instance on an Amiga 4000, you're lucky: the new
     FastFileSystem supports directory caching (DC-FFS), which very
     much speeds up TrapToss' directory scanning.  You will get this
     speed enhancement if you re-format your "Mail:" partition with
     the 'DIRCACHE' option.  

  5.1. Quick Import for Points  

       Usually TrapToss converts messages to an internal format in
     order to process them. While this is required for Nodes, it is
     just unneccessary overhead for Points. TrapToss automatically
     turns off these conversions whenever you use IMPORT for
     importing messages (that's what you usually do as a Point). This
     is an additional reason why as a Point you should never use
     TOSS! 

       If, for some strange reason, you are a Node and use IMPORT
     instead of TOSS, you have to make sure you specify NOQUICKIMPORT
     in your config file! Otherwise Seen-By and Path lines will not
     correctly be updated! 

  5.2. Buffered I/O    

       TrapToss now supports buffered I/O, that means data are first
     gathered in memory before they will be written to disk.
     Especially when you TOSS a lot of packets to other systems this
     can give you a dramatic speed increase.  

       Normally buffered I/O is turned off for sake of memory, but if


     Speeding up your System                                Buffered I


     Page 15            TrapToss' Fantastic Manual             Page 15


     your computer has about 3 MB of memory or more, you should
     specify: 

          IOBUFFERSIZE 8192

       which will cause TrapToss to allocate a buffer of 8 KB per
     file.  Large systems with even more RAM should increase this
     value to 16K or 32K in order to get optimal performance.  

  5.3. Dupe-Checking and Reply-Linking   

       DUPCHECK, SMALLDUPCHECK, and LINKMSGS cause TrapToss to seek
     through lookup-tables or through the message base. As a large
     system you will most definitely want to check for duplicate
     messages. In this case it is highly recommended to use DUPCHECK
     instead of SMALLDUPCHECK.  

       Most Points or smaller Nodes do not require dupe-checking. In
     this case just do not specify DUPCHECK or SMALLDUPCHECK in your
     config file.  

       Many editors allow using a 'threaded read mode' which lets you
     immediately read replies to a message; if your editor doesn't
     allow this or you usually do not use this feature, just make
     sure you don't specify LINKMSGS anywhere in your config file.
     This should again increase the speed of your system by some
     amount.  





























     Speeding up your System         Dupe-Checking and Reply-Linking


     Page 16            TrapToss' Fantastic Manual             Page 16


  6. Advanced Node Topics   

       Most Nodes and Points should find enough information in the
     last sections to setup their systems. More complex systems can
     find some additional features in this chapter and in the
     "Complex Configuration Keywords" reference section.  

       This chapter covers advanced topics, such as Regions, Hubs,
     and multi-net setups and is therefore intended for more
     experienced SysOps.  

  6.1. Using the Nodelist   

       Since Version 1.50 TrapToss supports using the Nodelist.
     Using the Nodelist is required for most of the features
     discussed in the sections below.  

       To tell TrapToss that a valid Nodelist exists and can be used
     you have to do two things: first, copy the 'traplist.library'
     you find in TrapToss' archive to your 'libs:' directory. Second,
     specify the directory the Nodelist can be found in (using the
     NODELISTPATH keyword).  Here is an example: 

          NODELISTPATH Mail:Nodelist

       This automatically enables the HOSTROUTING and BOSSROUTING
     switches discussed in the next section.  

  6.2. Hosts and Bosses   

       Usually TrapToss does not route messages that have the Crash
     or Direct flag set. Therefore a message addressed to a Point
     will create an outbound .DUT or .CUT file for this Point. E.g: A
     Crash message to 2:310/6.4 will create a '2.310.6.4.CUT'
     outbound file causing your mailer to try calling this Point
     directly.  

       While this may well be exactly what you intended, Points
     usually are not callable. Therefore, when the Nodelist is turned
     on, TrapToss defaults to BOSSROUTING, causing the message to
     automatically be redirected to the Boss of the addressed system.
     In the above example a '2.310.6.0.CUT' file is created instead
     of the original '2.310.6.4.CUT' file.  

       Similar rules can be applied to private Node systems.  Private
     Nodes do not have their telephone number listed in the Nodelist,
     i.e. you usually cannot call them. With the Nodelist support
     turned on, TrapToss defaults to HOSTROUTING causing Crash or
     Direct messages to undialable systems to be redirected to the
     Net's Host. A Crash message to 2:281/100 (which is an undialable
     system) will therefore get redirected to 2:281/0.  





     Advanced Node Topics                           Hosts and Bosses


     Page 17            TrapToss' Fantastic Manual             Page 17


       Also if the Boss of an undialable Point is undialable as well,
     messages to this Point will be Host-routed if HOSTROUTING is not
     explicitely turned off.  

       To turn off HOSTROUTING (or BOSSROUTING) you can specify
     NOHOSTROUTING (or NOBOSSROUTING respectively) in your config
     file. Alternatively you can omit the NODELISTPATH statement
     (i.e. turn off Nodelist support) causing HOST- and BOSSROUTING
     to be switched off automatically.  

  6.3. Regions and Hubs   

       When the Nodelist is used, wildcards are extended to Regions.
     That means that whenever a wildcard can be used as a source
     Address, a Region wildcard of the form 

          R<region>[%<wildcard>]

       can be used instead. <Region> specifies the region number
     (defaulting to your Zone) and an optional <wildcard> can be used
     to describe a Zone for this Region. Here are a few examples: 

          ROUTE HOLD   203/600 R20 R21
          ROUTE CRASH  281/100 R12%1:*
          ROUTE DIRECT 123/456 R60%*

       The first line tells TrapToss to put all Mail addressed to
     systems in Regions 20 and 21 on Hold for 203/600. The second
     example tells TrapToss to Crash all messages addressed to
     systems in Region 12 of Zone 1 to 281/100 (this is the version
     you need for Regions in other Zones than yours). The last
     example causes TrapToss to directly route all Mail addressed to
     systems in Region 60 in any Zone through 123/456.  

       In FidoNet Regions are currently unique throughout all Zones;
     it is therefore safe to use the form described in the last of
     the three examples. Be warned, however, that this does not
     necessarily apply to other FidoNet like networks! 

       While this wildcard extension can be used for source Addresses
     of routing statements, there is another extension that can be
     used for destinations: HUBs. Here is an example on how to use
     HUB wildcards: 

          ROUTE DIRECT HUB 2:253/* 2:203/*

       This causes all messages addressed to systems in the Nets 253
     and 203 to be routed to their corresponding Hub systems.  

       You can, of course, combine the Region and the HUB wildcards,
     as shown in the following example: 

          ROUTE DIRECT HUB R20
          ROUTE NORMAL HUB R21 R22 R28 R12%* R15%*


     Advanced Node Topics                           Regions and Hubs


     Page 18            TrapToss' Fantastic Manual             Page 18


       Whenever you use the HUB or Region wildcards, you must make
     sure you are using a Nodelist.  Otherwise routing may produce
     unexpected results! A good idea is to explicitely specify
     BOSSROUTING and/or HOSTROUTING in your config file. You will
     then get a warning if there are problems opening the Nodelist.  

  6.4. Bouncing     

       If you are using a Nodelist, TrapToss knows of legal and
     illegal (unknown) destination systems. To bounce messages
     addressed to unknown destinations you can use the BOUNCE
     keyword. When you are using a complete FidoNet Nodelist 

          BOUNCE 1:* 2:* 3:* 4:* 5:* 6:*

       will return all messages to unknown Addresses within FidoNet.
     OtherNet Addresses (i.e. Addresses of non-FidoNet systems) will
     not be bounced.  

  6.5. Multiple Networks    

       In the last couple of years a lot of FidoNet-like systems have
     evolved that are not actually part of FidoNet. Therefore many
     SysOps felt the need for being part of multiple networks.  

       TrapToss allows you to specify multiple Addresses for your
     system plus multiple sub-nets (Domains) your system resides in.
     In addition to the traditional AKA keyword you can now use the
     enhanced DOMAIN statement to specify OtherNet Addresses.  Here
     is an example: 

          NODE   3:622/401
          DOMAIN MaxNet    90:1003/1   90:*
          DOMAIN AmigaNet  41:200/401  39:* 40:* 41:*
          DOMAIN FidoNet

       This sets your default Address to 3:622/401. For all messages
     within Zone 90 an Address of 90:1003/1 will be used for your
     system (using a Domain name of "MaxNet"). 41:200/401 will be
     used as your main Address for all messages in Zones 39, 40, and
     41 (Domain "AmigaNet"). Finally, the default Domain "FidoNet"
     will be used for all other other Zones.  

       Areas can be specified as usual, just specify the main Address
     corresponding to the Domain a certain Area is in -- for example: 

          AREA AREXX  MAIL:FidoNet/Arexx     3:622/401  3:711/439
          AREA TREKKY MAIL:AmigaNet/TREKKIE 41:200/401 41:200/439

       To specify pass-through Areas in other networks there now is a
     new local keyword which lets you specify the OtherNet Address to
     use for the given Area. The example below shows you how to
     specify your AmigaNet main Address 41:200/401 for the
     pass-through Area PD_AMY: 


     Advanced Node Topics                         Multiple Networks


     Page 19            TrapToss' Fantastic Manual             Page 19


          AREA PD_AMY MAIL:AmigaNet/PD_AMY 41:200/439 41:200/401.7
          MAIN 41:200/401

       When you specify echoes in multiple networks you usually have
     to use different main Addresses in your Seen-By lines. While
     still possible, adjusting Seen-Bys using ADD and STRIP becomes a
     lot of work, and sometimes virtually impossible (when an AreaFix
     program is used, for instance).  

       To consistently adjust your Seen-By lines in a multinet
     environment use the FORDOMAIN keyword. Here is an example (using
     the same main Addresses as before): 

          FORDOMAIN FidoNet  STRIP 3:622/401.*
          FORDOMAIN FidoNet  ADD   3:622/401
          FORDOMAIN AmigaNet STRIP 41:200/401.* 41:2401/*
          FORDOMAIN AmigaNet ADD   41:200/401

       As you can see, just like with STRIPNODES, 'FORDOMAIN ...
     STRIP' lines may contain Wildcards.  




































     Advanced Node Topics                         Multiple Networks


     Page 20            TrapToss' Fantastic Manual             Page 20


  7. Common Configuration Keywords   

       This chapter describes the most commonly used config
     statements.  They should suffice for configuring simple Node or
     Point systems.  Once your system is up and running, you can
     refine your setup by using some of the more special
     configuration startements described in the next chapter.  

  7.1. ADDNODES     

       This keyword takes a list of Nodes to be added to Seen-By
     lines of all exported messages. This command takes a list of
     4-dimensional Fido-Nodes (where the 'Zone' and 'Point' parts may
     be omitted -- 'Zone' then defaults to the Zone specified in the
     'NODE' command, 'Point' defaults to zero). This list of Nodes
     will be added to the Seen-By lines of all processed EchoMail
     messages.  

       This statement can be overridden by the local 'ADD'and 'STRIP'
     commands (see the special keywords section for more
     information).  

       Example: 

          ADDNODES 310/6 310/3

       will add '310/6' and '310/3' to the Seen-By lines of all
     exported messages.  

  7.2. AKA     

       Allows you to add a list of FidoNet Addresses for your system
     (aliases).  TrapToss will then recognize any message addressed
     to one of those Addresses as addressed to you, which may be
     important for Netmail. Example: 

          AKA 2:3160/4 2:3160/4.1 39:2/3

       Defaults to no AKAs.  

  7.3. AREA     

       Define an EchoMail Area. AREA statements list the Area Tag,
     under which an EchoMail conference is known throughout the
     network, plus the directory in which you intend to store
     messages from that Area, plus a list of Nodes that receive this
     Area from you (or from which you receive the Area).  

       Syntax: 

          AREA tag directory {Nodes} 

       In order to receive messages in that Area yourself, you have
     to list your own Node number as the first Node in that Area. If


     Common Configuration Keywords                            AREA


     Page 21            TrapToss' Fantastic Manual             Page 21


     you do not list yourself among the participants of that echo,
     the Area will be pass-through, i. e.  messages in that Area will
     never be stored on your system, but immediately moved to the
     outgoing packets in your outbound directory, "on-the-fly".  

       Example: 

          AREA TRAPDOOR Mail:TrapDoor.Area    310/6 310/6.4

       Adds Area 'TRAPDOOR' in Directory 'Mail:TrapDoor.Area' for
     myself (2:310/6.0) and 2:310/6.4 

       Also, the AREA statement limits the scope of local keywords
     such as ADD, STRIP, GATE, DISALLOW, and ALLOW.  

  7.4. BADPACKETS     

       When TrapToss detects that a packet is somehow malformed, it
     will move the offending packet to the BADPACKETS directory.  

       Syntax: 

          BADPACKETS directory 

       The default is Mail:Bad.Pkts 

  7.5. (NO)BOSSROUTING     

       Causes TrapToss to automatically route Direct or Crash Mail
     addressed to undialable Points to the Point's Boss system. E.g.:
     a Crash Netmail message addressed to 2:310/6.4 will
     automatically be crashed to 2:310/6, if 2:310/6.4 does not
     appear in your Nodelist (or is undialable). This switch requires
     a valid Nodelist.  

       Default is BOSSROUTING when NODELISTPATH is set, NOBOSSROUTING
     otherwise.  

  7.6. BOUNCE     

       In conjunction with NODELISTPATH you can use BOUNCE to return
     Netmail to unknown destinations. Like STRIPNODES this command
     takes a list of (wildcarded) Fido Addresses to be taken into
     account when bouncing. Any message addressed to a system that
     cannot be found in the Nodelist, but matches this list, will be
     bounced. Example: 

          BOUNCE 1:* 2:* 3:* 4:* 5:* 6:* 

       bounces all mails addressed to unknown systems in Zones 1-6.
     Default is no bouncing at all.  





     Common Configuration Keywords                          BOUNCE


     Page 22            TrapToss' Fantastic Manual             Page 22


  7.7. CHANGE     

       Change the flavour of exported messages.  

       Syntax is: 

          CHANGE <from> <to> {<nodes>}

       where 'from' and 'to' are one of NORMAL, DIRECT, HOLD and
     CRASH and 'nodes' is a list of Fido-Nodes (wildcards allowed).  

  7.8. COLO(U)RS     

       This selects the colour of the TrapToss Screen. Its syntax is
     one of: 

          COLOURS <col1>/<col2>/<col3>/<col4>
          COLORS  <col1>/<col2>/<col3>/<col4>
          COLOURS <col1> <col2> <col3> <col4>
          COLORS  <col1> <col2> <col3> <col4>

       where <col1>..<col4> are the RGB4 values (in decimal or hex
     preceded by $) of TrapToss' screen colours. This command is
     ignored in 'SCREENMODE NONE'.  

  7.9. CONFIG     

       This keyword specifies a special path for the FCFG
     configuration file.  TrapToss usually searches the current
     directory and 'MAIL:' for a configuration file called
     'TrapToss.Cfg' or 'Fido.Cfg' (in exactly that order, i.e.
     'TrapToss.Cfg' then 'mail:TrapToss.Cfg' then 'Fido.Cfg' then
     'mail:Fido.Cfg').  If you want to use a special config file
     placed somewhere else you have to specify 

          CONFIG <filename>

       to describe the path and name of your file.  

       NOTE: This keyword can only be used from the CLI and has to be
     the first parameter on the command line.  

  7.10. DEFAULTUNPACKERS     

       Specifies the fall-back default unpackers to be used for
     specific bundle types. The syntax for this command is 

          DEFAULTUNPACKERS <arc> <zoo> <lharc> <zip> <arj> <unknown> 

       TrapToss will automatically fall back to these unpackers as
     soon as a bundle is not covered by an UNPACKER statement. In
     fact this statement obsoletes the UNPACKER statement if you do
     not want to specify certain unpackers for certain Nodes (since
     they will be chosen automatically, now).  


     Common Configuration Keywords                DEFAULTUNPACKERS


     Page 23            TrapToss' Fantastic Manual             Page 23


       Default is 

          DEFAULTUNPACKERS "Arc x" "Zoo x:O" "Lha -m -X e" "UnZip" \
                           "UnArj e -y" "rx XArc e"

  7.11. DOMAIN     

       This statement has been reworked for TrapToss 1.30 or higher.
     Its syntax and behavior, though, is backwards compatible with
     TrapToss 1.23.  DOMAIN tells TrapToss the domain your system is
     in, the main Address to use with this domain and the
     address-span this domain is valid in. The syntax used is: 

          DOMAIN <name> [<main> [{<addr>}]]

       where <name> is the name of the domain as used in ^aMSGID
     lines, etc.  <main> is the main Address to be used in this
     domain; it is automatically added to the list of AKAs, so
     there's no need to specify this Address in your AKA line as
     well. <addr> is a list (containing zero or more elements) of
     Addresses this domain is valid in. You can use wildcards as
     well. If no Addresses are given, the whole Zone of <main> will
     be taken as Address-span. If neither <main> nor <addr> is given,
     your system's NODE Address is used and all systems are covered
     (this is compatible with older versions of TrapToss). Here are
     some examples: 

          DOMAIN HyperNet 77:123/45 77:* 78:* 79:*
          DOMAIN OtherNet 56:78/90
          DOMAIN FidoNet

       The first example defines domain "HyperNet" for all messages
     in Zones 77, 78, and 79 with a main Address of 77:123/45 for
     your system. In the second line, "OtherNet" with a main Address
     of 56:78/90 is used for all mail in Zone 56, and finally, in the
     last line "FidoNet" (with a main Address as specified by your
     NODE statement) is used for the rest of the world.  

       Default is 'DOMAIN "FidoNet"'.  

  7.12. (NO)DUPCHECK     

       Switches on the Duplicate message checking of TrapToss. Causes
     TrapToss to save all MSGID's (or CRC's if none) of incoming
     messages to a dupe-database (two files called Duplicate.Index
     and Duplicate.MsgId in your MAIL: directory) and to check for
     duplicates. Per default all duplicate messages will be moved to
     the 'BAD' Area. Other options can be set through the 'DUPES' and
     'NETDUPES' commands.  

       Defaults to NODUPCHECK.  





     Common Configuration Keywords                    (NO)DUPCHECK


     Page 24            TrapToss' Fantastic Manual             Page 24


  7.13. FAKE     

       Specifies the FakeNet Address of your system. This should only
     be used by Points who have a special PointNet Address. For Nodes
     see the POINTNET keyword.  

       Syntax: 

          FAKE 3160/4

       The default setting for the fake Address (which is used for
     Path lines, packet and EchoMail message headers) is the Address
     specified by the 'NODE' keyword (see there).  

  7.14. (NO)FILEATTACH     

       This switch enables the file attach mode for TrapToss. If a
     Netmail message has its FileAttach bit set, TrapToss will attach
     the specified file to the message. The message will be treated
     according to the settings of the Crash and Hold bits. If neither
     is set, Direct is assumed (thus TrapToss will create .DUT files
     for FileAttach messages).  

       Currently TrapToss tries to locate the file as given in the
     subject.  The file name will then be copied to a ".DLO" file
     (".CLO" or ".HLO" if the Crash or Hold bit of the message is
     set). If the file cannot be found, TrapToss will attempt to
     locate the file in the Inbound directory (to allow the routing
     of file attaches) and - if found there - copy the file name
     prefixed by the Inbound directory name to the ".DLO" file.  

       Otherwise (if TrapToss could not locate the file) the subject
     will be copied to the ".DLO" file as-is, to enable locating the
     file at mailer run-time (TrapDoor, for instance, will attempt to
     locate the file in the outbound directory if no path is given).  

       Please note: routing file attaches is far from perfect, right
     now. We may give this topic additional thought in future
     releases. Currently there is no way to allow local file attaches
     and disallow file attach routing at the same time; Node systems
     should set FILEATTACH only for scanning (and NOFILEATTACH for
     tossing) to prevent TrapToss from routing file attaches.  

       Default setting is NOFILEATTACH.  

  7.15. (NO)FORCE4DMO     

       Causes TrapToss to use 4-dimensional .MOx files for ARCMail
     bundles. This will override 'OLDSTYLEMO' (see there).  

       The default setting is NOFORCE4DMO, which - if 'OLDSTYLEMO' is
     not set - causes TrapToss to work in "compatibility mode", i.e.
     bundles addressed to the same Zone which are not addressed to a
     Point Address other than 0 will have "old style" 2-dimensional


     Common Configuration Keywords                   (NO)FORCE4DMO


     Page 25            TrapToss' Fantastic Manual             Page 25


     filenames (like '1234abcd.TU1'). All other files will be "new
     style", e.g. '2.310.6.4.WE7'.  

       We recommend using FORCE4DMO for all systems running TrapDoor.
     Default, however, is NOFORCE4DMO.  

  7.16. (NO)HOSTROUTING     

       Like (NO)BOSSROUTING this statement allows automatic Host
     routing in conjunction with the Nodelist. If a valid
     NODELISTPATH is given, HOSTROUTING causes non-routed Netmail
     messages (i. e. Crashmail, Directmail or FileAttaches) to be
     routed through the Host if the specified system is undialable or
     unknown.  

       For instance: messages to 2:123/456 will be re-routed to
     2:123/0 if 2:123/456 is undialable. Messages to 1:987/654.3 will
     be routed through 1:987/0 if neither 1:987/654 nor 1:987/654.3
     are reachable.  

       Default is HOSTROUTING if a valid Nodelist is specified,
     NOHOSTROUTING otherwise.  

  7.17. (NO)IMPORT     

       Causes TrapToss to import inbound bundles/packets. Messages
     will be stored in the local message base but not automatically
     re-exported (you have to say EXPORT as well). This is useful for
     Points; Nodes, however, should use the more efficient 'TOSS'
     command which automatically tosses messages to the Outbound
     directory w/o having to export from the local message base.  

       Defaults to NOIMPORT.  

  7.18. INBOUND     

       Sets the Inbound directory path.  

       Syntax: 

          INBOUND <path>

       Default is 'INBOUND MAIL:Inbound'.  

  7.19. KEEP     

       Like ADD this switch is local to each Area; if specified for
     an Area this command tells TrapToss to keep a maximum of <n>
     messages in this Area's message base.  Whenever the number of
     messages in an Area becomes equal to or higher than the given
     number, TrapToss deletes one message per message imported to
     this Area. TrapToss will always delete the first message higher
     than 1 (i.e. the smallest message number above 1).  



     Common Configuration Keywords                            KEEP


     Page 26            TrapToss' Fantastic Manual             Page 26


       Example: 

          AREA TRAPDOOR ...
          KEEP 100

       deletes one message per incoming message if the number of
     messages in "TRAPDOOR" becomes higher than 99. This switch has
     been introduced in version 1.22 

  7.20. (NO)LINKMSGS     

       On importing this tells TrapToss to link messages with the
     same subject (Reply-Linking, Threading).  

       Default is NOLINKMSGS.  

  7.21. LOGFILE     

       Select the name of the Logfile.  

       Example: 

          LOGFILE Mail:TT.Log

       Defaults to 'Mail:TrapToss.Log' 

  7.22. LOGLEVEL     

       Select the amount of logging from 0 to 9. 9 is most logging.  

       If you select LOGLEVEL 0, no logfile will be created (and no
     logwindow will be opened, even if you had enabled it).  

       Example: 

          LOGLEVEL 3

       Defaults to, hmmm, let me have a look, 2 (but this definitely
     is subject to change according to enhancement requests).  

  7.23. LOGWINDOW     

       This keyword works in conjunction with 'SCREENMODE'. It
     defines the window position and size of the TrapToss log output
     window: 

          LOGWINDOW <left>/<top>/<width>/<height>
          or
          LOGWINDOW <left> <top> <width> <height>

       where the parameters follow the Amiga convention for Window
     sizes. Per default TrapToss will automatically center the log
     Window in the upper half of the screen. No log window will open
     if 'SCREENMODE NONE' is specified or LOGLEVEL is set to 0.  


     Common Configuration Keywords                       LOGWINDOW


     Page 27            TrapToss' Fantastic Manual             Page 27


  7.24. NODELISTPATH     

       When supplied with a string containing a valid Nodelist
     directory, this command tells TrapToss to open traplist.library
     and use the Nodelist. Using the Nodelist is required for special
     commands like BOSSROUTING, HOSTROUTING, or BOUNCE. The syntax is 

          NODELISTPATH <path> 

       For example: 

          NODELISTPATH Mail:Nodelist 

       The default is 'NODELISTPATH ""', meaning no Nodelist at all
     (this is compatible with earlier versions of TrapToss).  

  7.25. NETMAIL     

       Similar to 'AREA' this defines the Netmail directory, but
     unlike 'AREA' this keyword may only occur once.  

       Syntax: 

          NETMAIL MAIL_DIR Mail:Matrix

       For compatibility the name of the Area should be set to
     'MAIL_DIR'.  

  7.26. NODE     

       This keyword must not be omitted. It specifies the (main)
     Address of your system. Put your 4-dimensional FidoNet Address
     here. For compatibility you may omit the Zone entry, however you
     should specify 'ZONE' then.  

       Example: 

          NODE 2:310/6.4

       Points, who use a 'fake' PointNet have to specify their
     correct 4-dimensional Address here. The fake Address has to be
     specified using the 'FAKE' keyword.  

  7.27. ORIGIN     

       Local messages that do not contain an Origin line will be
     provided one by the Tosser. Use this keyword to specify your own
     particular Origin line (without the Node number which will be
     added by TrapToss).  

       Syntax: 

          ORIGIN orig_line



     Common Configuration Keywords                          ORIGIN


     Page 28            TrapToss' Fantastic Manual             Page 28


       <orig_line> is a string used by the tosser for your origin
     line.  

  7.28. OUTBOUND     

       Like 'INBOUND', but defines the Outbound directory path.  

       Syntax: see 'INBOUND' 

       Default is 'OUTBOUND Mail:Outbound' 

  7.29. PACKER     

       Tells TrapToss which packer to use for which Node.  

       Example: 

          PACKER "LHArc a" 310/* 313/*
          PACKER "Zoo a" *

       Defines 'LHArc' as Packer for all Nodes in Nets 310 and 313
     (of current Zone) and 'ZOO' as Packer for all other Nodes.  

       If a Node cannot be found in the list of PACKER statements,
     the command "Arc A" will be used to compress the mail bundle.  

  7.30. POINTNET     

       For Nodes only. Sets the fake PointNet for your system. All
     Addresses of template <pointnet>/<x> in Seen-By lines will be
     treated like <mynet>/<mynode>.<x>. Additionally, packets from
     PointNet Nodes will be interpreted as being from the correct
     4D-Address, so that security will work.  

       Example: 

          POINTNET 3160

       Point systems should not specify 'POINTNET', see 'FAKE' for
     specifying fake PointNet Addresses for Points. Nodes need only
     use this keyword if some of your Points are running older
     EchoMail software that uses fake PointNet addressing.  

  7.31. POLL     

       Causes TrapToss to create .FLO files for the Nodes specified
     if in route mode. If a .FLO file for a specified Node already
     exists, no action will be taken.  

       Example: 

          POLL 310/6 3:603/808




     Common Configuration Keywords                            POLL


     Page 29            TrapToss' Fantastic Manual             Page 29


  7.32. REMAP     

       This statement is very useful for Node systems. Any private
     mail addressed to one of your system's AKAs can be remapped to
     another system (usually one of your Points). The syntax of this
     statement is: 

          REMAP <name> <addr> 

       where <name> is the name of the addressee of the Netmail and
     Address is the Fido Address it should be remapped to. Under
     Kickstart 2.04 or higher, <name> may be any valid AmigaDOS
     pattern, otherwise only '?' and '#?' are allowed as patterns.  

       Please note that at the moment <addr> may be any valid FidoNet
     Address, but TrapToss will never add or remove kludge lines
     to/from the received Netmail.  Therefore please make sure your
     Points do not re-export their Netmail.  Remapping to systems in
     other Zones can only be done if mail to these systems is put on
     hold directly at your system. This behaviour may or may not
     change in the future, so don't rely on it; REMAP is intended for
     local Point-remapping, not for re-routing Netmail.  

       The default is no REMAP statement at all, which is compatible
     to older versions of TrapToss.  

  7.33. (NO)RENUMBER     

       Causes TrapToss to renumber its message base. This will
     automatically update the Hiwater-Mark (1.MSG) if it exists.  

       TrapToss tries to be as intelligent as possible here, i. e. an
     Area will only be re-scanned if it has not already been scanned
     by a SCAN or TOSS statement. Default is NORENUMBER.  

  7.34. ROUTE     

       Describes how to route Netmail (.OUT files).  

       Syntax: 

          ROUTE <flavour> <to> <from>

       Will re-direct all Netmail dedicated to <from> (a wildcarded
     list of Fido-Nodes containing at least one entry) to <to>
     (destination Address) using <flavour> (one of 'Crash', 'Direct',
     'Normal' or 'Hold').  

       Examples: 

          ROUTE Hold 2:253/140 1:140/* 2:253/*
          ROUTE Direct 2:2/3 3:*
          ROUTE Crash 2:310/6 *



     Common Configuration Keywords                           ROUTE


     Page 30            TrapToss' Fantastic Manual             Page 30


       Note: The destination Address for a ROUTE statement may
     contain wildcards, in which case the corresponding parts of the
     Address of the current mail packet being routed (the
     <from>-packet) will be used to replace the wildcards in the
     destination Address.  

  7.35. (NO)ROUTING     

       Switches on (off) the routing mode of the Tosser.  

       Default is ROUTING, if export/scan/toss mode is set, otherwise
     NOROUTING.  

  7.36. (NO)SCAN     

       Sets the Scan mode for the Tosser. This exports messages from
     the message base, but unlike 'EXPORT' causes TrapToss to export
     only local messages. This mode should be used by Points for
     exporting and by Nodes in conjunction with 'TOSS' (read: most
     systems should use SCAN instead of EXPORT).  

       Default is NOSCAN.  

  7.37. (NO)SCANOUTBOUND     

       Tells TrapToss to Scan the Outbound directory for .PKT files
     to be ARCed. If NOSCANOUTBOUND is set on Export mode, .PKT files
     will be created but not yet ARCed and routed. See also:
     (NO)ROUTING.  

       Default mode is SCANOUTBOUND in export/scan/toss mode,
     NOSCANOUTBOUND otherwise.  

  7.38. SCREENMODE     

       As you may have noticed TrapToss supports Screens. Currently
     this is far from perfect and we have not yet decided on whether
     we will make this a little more smart in the future or not.
     Anyway, here is the Syntax: 

          SCREENMODE <mode>

       where <mode> is one of 'CUSTOM' (simply open a custom screen),
     'WORKBENCH' (open windows on the default public screen),
     'ACTIVE' (currently active screen), 'TRAPTOSS' (open a shared
     TrapToss screen, for instance causes TrapToss to open on an
     already-opened TrapDoor screen) and 'NONE' (no screen at all).  

       The default mode is SCREENMODE TRAPTOSS, but this will most
     probably change...  






     Common Configuration Keywords                      SCREENMODE


     Page 31            TrapToss' Fantastic Manual             Page 31


  7.39. SEND     

       Causes TrapToss to send Netmail addressed to the Nodes given
     and their Points directly to these Nodes as compressed mail
     bundles. Actually, SEND is just an abbreviation for a set of
     route statements.  

       For example: 

          SEND Crash 310/6 310/3
          SEND Direct 310/* 313/* 1:123/456
     could also be written as: 

          ROUTE Crash  310/6     310/6.*
          ROUTE Crash  310/3     310/3.*
          ROUTE Direct 310/*.0   310/*.*
          ROUTE Direct 313/*.0   313/*.*
          ROUTE Direct 1:123/456 1:123/456.*

       As you can see, the SEND statements are much shorter and more
     concise.  

  7.40. STATWINDOW     

       This works in conjunction with 'SCREENMODE'. It defines the
     window position and size of the TrapToss status output window: 

          STATWINDOW <left>/<top>/<width>/<height>
          or
          STATWINDOW <left> <top> <width> <height>

       where the parameters are equal to the Amiga convention for
     Window sizing. Per default TrapToss will automatically center
     the Status Window in the lower half of the screen. No Status
     window will open if 'SCREENMODE NONE' is specified.  

  7.41. STRIPNODES     

       This is the opposite of 'ADDNODES'. You can specify a list of
     Nodes that will be stripped off the Seen-By lines of your
     EchoMail messages. This is especially useful for Node systems to
     get rid of their Points' Seen-By Addresses. Wildcards are also
     allowed here.  

       If you are running a Node system with Points, you will
     probably want to strip all occurrences of your Points from the
     Seen-By lines (don't forget to add yourself again!), like in: 

          STRIPNODES 2:310/6.* 2:3160/*
          ADDNODES 2:310/6

       There is also a local keyword, 'STRIP' which does basically
     the same as 'STRIPNODES', but local for each Area. For multiple
     Net setups you probably want to use 'STRIP' as well (see the


     Common Configuration Keywords                      STRIPNODES


     Page 32            TrapToss' Fantastic Manual             Page 32


     special keywords section for a description of 'STRIP').  

  7.42. (NO)TOSS     

       Selects Toss mode for TrapToss; causes Inbound packets/bundles
     to be imported to the local message base as well as being tossed
     to the Outbound directory (exporting on-the-fly). This will not
     re-export messages nor export Local messages.  

       Nodes should use this mode for importing messages in
     conjunction with 'SCAN' for exporting, although it is also
     possible, but a lot less efficient, to use 'IMPORT' for
     importing and 'EXPORT' for exporting.  

       Points should use IMPORT instead of TOSS for importing
     messages.  

       Defaults to NOTOSS.  

  7.43. (NO)UNATTENDED     

       Switches on the 'unattended' mode for TrapToss. This is
     especially useful if your system works without supervision: No
     Requesters, like "please insert disk" will appear, and smaller
     errors will be ignored by the Tosser. Thus you do not have to
     sit by while importing and/or exporting.  

       Defaults to NOUNATTENDED.  




























     Common Configuration Keywords                  (NO)UNATTENDED


     Page 33            TrapToss' Fantastic Manual             Page 33


  8. Special Configuration Keywords   

       This chapter describes TrapToss' less commonly used
     configuration statements. Most simple systems should be able to
     run without specifying any of them. Use these commands with
     care, they allow running setups incompatible to other systems;
     only experienced sysops should use the commands described
     below.  

  8.1. (NO)4DMSGHEADER     

       This keyword determines whether to use the old date-stamped
     message header or the new FTS-0001 style 4D message header for
     stored messages.  Default is NO4DMSGHEADER, which is compatible
     with most available Amiga message-editors.  

        Please note that if you turn on 4DMSGHEADER you must make
     sure that all software writing to your messagebase uses 4D
     headers. Otherwise TrapToss will interpret the old style date
     fields as Zone/Point-Addresses giving you the most odd effects! 

  8.2. ADD     

       This is a local keyword, i.e. it may only stand after an AREA
     line (see below). This command takes a list (i.e. one or more)
     of 4 dimensional Fido-Nodes (where 'Zone' and 'Point' may be
     omitted - 'Zone' defaults to the Zone given in the 'NODE'
     keyword and 'Point' defaults to zero) which shall be added to
     the Seen-By lines of messages exported from the Area defined by
     the 'AREA' keyword above it.  

       Example: 

          AREA TRAPDOOR Mail:TrapDoor.Area 310/6 310/6.4
          ADD 3160/4

       This will add '3160/4' to the Seen-By lines of each exported
     message of Area 'TRAPDOOR' (for 'AREA' Keyword see below).  

  8.3. (NO)ADDMSGID     

       This keyword causes TrapToss to create a ^aMSGID line for
     every local message which does not already contain one. Useful
     for editors like CE 0.10 which do not already create MSGID's.  

       Defaults to ADDMSGID.  

  8.4. (NO)ADDOUTBOUND     

       Tells TrapToss to put the outbound directory path in front of
     each exported filename (useful for mailers which do not
     automatically search the outbound directory).  

       Defaults to ADDOUTBOUND.  


     Special Configuration Keywords                (NO)ADDOUTBOUND


     Page 34            TrapToss' Fantastic Manual             Page 34


  8.5. (NO)ADDPID     

       Similar to ADDMSGID, but for ^aPID lines. If set to 'ADDPID'
     local messages which do not yet contain a ^aPID line will be
     provided with one.  

       Defaults to ADDPID.  

  8.6. ALLOW     

       Normally, TrapToss will refuse to accept EchoMail from a Node
     that is not listed in your AREA statement for that Area.
     Instead, it will move the messages to the BAD message directory.
     Sometimes, however, it is desirable to receive messages in an
     Area without having the Node listed in the export list. An
     example might be a read-only Area. You can allow certain Nodes
     to send you EchoMail in that Area, using the ALLOW statement.
     ALLOW is a local keyword, and may only be used after an AREA
     line, just like the ADD or STRIP commands. ALLOW accepts
     wildcards.  

       Here is an example: 

          AREA TEST MAIL:Test.area 310/6 310/3 310/42
          ALLOW 310/99 3160/*

  8.7. (NO)AREAPACKET     

       In EXPORT or SCAN mode this switch will force TrapToss to
     create a new packet for each Area. It may be useful if your
     Boss/Host uses an Area-oriented system to increase performance
     on that system.  Generally not recommended, especially since
     this switch currently does nothing in TOSS or IMPORT mode! 

       Defaults to NOAREAPACKET.  

  8.8. (NO)AUTORENUMBER     

       When set to AUTORENUMBER, this switch causes TrapToss to
     automatically renumber all Message-Areas that have been SCANned
     or EXPORTed. Only Areas that have been changed are touched. This
     takes away some overhead a lonely RENUMBER statement would have
     and is especially useful if you are not using KEEP, but some
     external messagebase-cleanup utility you only run once in a
     while. Default is NOAUTORENUMBER.  

  8.9. BUFFERSIZE     

       On IMPORT/TOSS TrapToss will buffer incoming .PKT files. Use
     this keyword to specify the buffer size for all packets. Set
     according to your memory needs.  





     Special Configuration Keywords                     BUFFERSIZE


     Page 35            TrapToss' Fantastic Manual             Page 35


       Syntax: 

          BUFFERSIZE <number> 

       The default is to use half the size of the largest free block
     of memory. If a smaller buffer is sufficient to read the whole
     .PKT into memory, TrapToss will only allocate that smaller
     amount of memory.  

  8.10. COPYMSG     

       This statement allows local sysop copies of Netmail messages
     to be created. Messages addressed to other systems (and
     therefore not put to the local message base) are checked for an
     addressee matching an AmigaDOS compatible pattern: 

          COPYMSG <pat> 

       <pat> may contain '?' or '#?' wildcards in Kickstart 1.3 or
     below -- it can be a full featured AmigaDOS pattern in Kickstart
     2.04 or higher.  

       Default is no COPYMSG at all.  

  8.11. (NO)CRASHMAIL     

       Use this keyword to tell TrapToss to allow Crashmail messages
     in transit, i.e. incoming messages with the Crash bit set will
     be routed as Crashmail. This is useful to allow 'emergency
     messages' to be passed on.  

       Default is NOCRASHMAIL.  

  8.12. (NO)CRC     

       NOCRC causes TrapToss to ignore messages without MSGID kludge
     line for dupe checking. This is the opposite of CRCONLY
     (described below). Using NOCRC in conjunction with CRCONLY
     therefore does not make much sense.  

       Default is CRC.  

  8.13. (NO)CRCONLY     

       If you select CRCONLY, TrapToss will ignore the MSGID for
     dupchecking.  Instead, it will use an internally calculated CRC
     to find duplicated messages. This is generally not recommended.  

       Defaults to NOCRCONLY.  







     Special Configuration Keywords                    (NO)CRCONLY


     Page 36            TrapToss' Fantastic Manual             Page 36


  8.14. (NO)DELETEEMPTYMSGS     

       Causes TrapToss to automatically delete empty Netmail messages
     on import. This might save you from a lot of undesired status
     messages some utilities produce. Please note that messages
     matching a MSGFILTER pattern are not affected by this command,
     no matter if they are empty or not! This may or may not change
     in the future, so don't rely on this behaviour.  

       Defaults to NODELETEEMPTYMSGS.  

  8.15. (NO)DELROUTEATTACHES     

       This switch causes TrapToss to turn on (off) deleting of
     routed file attaches. If FILEATTACH is set, DELROUTEATTACHES
     causes TrapToss to add a '-' sign before the name of the routed
     attached file, which will in turn be deleted by TrapDoor when
     sent.  

       Default is NODELROUTEATTACHES.  

  8.16. DESTINIZEPACKET     

       This sets the compatibility mode for some programs that do not
     fully comply FTS-0001 (like GEcho with "Check Destination
     packet" set).  This keyword takes a list of (wildcarded) Fido
     Addresses and causes TrapToss to change the packet header of
     packets routed through these systems. For example: 

          DESTINIZEPACKET 2:310/90 2:123/* 

       This will re-address all packets routed through 2:310/90 or
     Nodes in Net 123.  

  8.17. (NO)DISABLEDIRCACHE     

       Tells TrapToss to ignore the directory dates and always scan
     all Areas. Only use this if your file system doesn't correctly
     support date stamps. Default is NODISABLEDIRCACHE.  

  8.18. (NO)DISABLEMATRIXPID     

       Since version 1.22 TrapToss creates PID lines for local matrix
     mail as well (default: NODISABLEMATRIXPID). To restore version
     1.20 compatible behaviour please specify 

          DISABLEMATRIXPID

  8.19. DISALLOW     

       Like ALLOW, ADD and STRIP this is an Area-local keyword. This
     causes messages to be rejected from systems even though they're
     listed in the specified export list (read-only Areas). Its
     syntax is: 


     Special Configuration Keywords                       DISALLOW


     Page 37            TrapToss' Fantastic Manual             Page 37


          DISALLOW {wfnodes} 

       Like with STRIP, <wfnodes> is a list of (wildcarded) FidoNet
     Nodes to be excluded from the current Area. Messages from
     systems matching these Addresses will not be accepted in the
     Area. Example: 

          AREA TEST Mail:Echo/Test.Area 2:310/6 .1 .3 .4
          DISALLOW 2:310/6.1 2:310/6.3

       This specifies the Area 'TEST' as read-only for 2:310/6.1 and
     2:310/6.3, 2:310/6 and 2:310/6.4 are allowed to write messages
     in this Area.  

  8.20. DUPES     

       Using this command you can specify what to do with duplicate
     messages.  There are three possibilities at the moment: 

          DUPES BAD
          DUPES DELETE
          DUPES IGNORE

       'BAD' causes duplicates to be tossed to the BADMSGS directory.
     'DELETE' causes them to simply be deleted (and not passed on).
     'IGNORE' just does nothing, dupes will be tossed through like
     normal messages (the difference to NODUPCHECK however is, that
     the dupe base is kept updated). Default is 'DUPES ->BAD', which
     is compatible to earlier versions of TrapToss.  

  8.21. DUPTABLESIZE     

       Allows you to select the size of the Duplicate message files
     that TrapToss uses to remember important information about the
     past few thousand messages. Note: You cannot select a specific
     number of messages that TrapToss will remember, nor can you
     select a specific size of the files.  You can rather change an
     internal value that will influence the size of the duplicate
     message table. Also, the number of messages "remembered" will
     always be smaller than the number you specify with DUPTABLESIZE.
     (The actual number will be about 80% of the value of
     DUPTABLESIZE.) 

       Syntax: 

          DUPTABLESIZE 5000

       Defaults to 8192.  








     Special Configuration Keywords                   DUPTABLESIZE


     Page 38            TrapToss' Fantastic Manual             Page 38


  8.22. (NO)ECHOCRASH     

       Normally EchoMail messages should not have their Crash bit
     set. However you can use this keyword to tell TrapToss not to
     clear Crash bits of EM messages in transit.  

       Defaults to NOECHOCRASH.  

  8.23. (NO)EXPORT     

       This keyword tells the Tosser to export Mail (Local and
     InTransit) from all Areas (see AREA). Usually this keyword will
     be used via CLI although it may be added to the config file.
     Most systems should not use this switch, but (NO)SCAN instead
     (see there). Only Nodes (not Points) importing all mail with
     'IMPORT' have to use 'EXPORT'.  

       Example: 

          TrapToss EXPORT

       Default is NOEXPORT.  

       Caveat: Points should use 'SCAN' (see there) which only
     exports local messages as an additional security feature to
     prevent re-exporting of incoming messages. Nodes using 'TOSS'
     for importing also should use SCAN for exporting local
     messages.  

  8.24. FORDOMAIN     

       This statement is primarily intended for use with multi-net
     setups.  Its syntaxes are: 

          FORDOMAIN <name> ADD {nodes}
          FORDOMAIN <name> STRIP {wnodes}

       where <name> is the name of the selected domain. This must
     already have been specified with a DOMAIN statement (see there).
     There are two sub-commands, 'ADD' and 'STRIP'; they act like the
     ADD(NODES) or STRIP(NODES) command, but will only affect Areas
     which are part of the specified domain. Adding/stripping of
     systems from the Seen-By lines will be performed between the
     corresponding ADDNODES/STRIPNODES and ADD/STRIP commands, in
     other words: FORDOMAIN takes precedence over
     ADDNODES/STRIPNODES, but is superceded by ADD/STRIP.  

       Please note that you cannot use both ADD and STRIP within the
     same FORDOMAIN line; you have to specify two lines instead.  

       See also: ADD, ADDNODES, STRIP, STRIPNODES, DOMAIN, AREA.  





     Special Configuration Keywords                      FORDOMAIN


     Page 39            TrapToss' Fantastic Manual             Page 39


  8.25. (NO)FSC39     

       Enables (disables) the creation of FSC-0039 compatible packet
     headers.  Normally, these new packet headers should be
     transparently read by older packages without problems.  

       Basically FSC39 is the same as FSC48 apart from a few minor
     differences.  This switch was added in Version 1.15 of TrapToss
     in order to avoid minor problems some Points may have with
     FrontDoor Bosses. This switch is now default, so if you have a
     Boss which does not accept FSC-39 compatible packets, you might
     try "FSC48" instead (see description of FSC48).  

       Defaults to FSC39 (unless FSC48 is set).  

  8.26. (NO)FSC48     

       Enables (disables) the creation of FSC-0048 compatible packet
     headers.  Normally, these new packet headers should be
     transparently read by older packages without problems. Please
     note that FSC-0048 packets become the default method of TrapToss
     when FSC-0039 packet creation is disabled.  

       Defaults to NOFSC48 (unless NOFSC39 is specified).  

  8.27. GATE     

       This is a magic keyword. It is the local variant of the
     ZONEGATE statement and will act only on the current Area, just
     like ADD, ALLOW and STRIP. See the ZONEGATE statement for a
     description of what GATE does, and don't dare to use it unless
     you know _exactly_ what you are doing. Basically, you can make
     up individual 'custom' SEEN-BY lines for every single Node, and
     different ones in every single Area! Trust me, and better don't
     touch it.  

  8.28. GATEROUTE     

       This statement is similar to ROUTE. It causes mail to certain
     systems to be routed through another system (preferably a
     ZoneGate). Like with Host or Boss routing, Gate routing is done
     during the TOSS and SCAN phases, not during ROUTING.  

       The difference to the normal ROUTE statements is that it
     changes the message destination Address to the Address given in
     this statement.  In other words the original message destination
     can only be retrieved if the message contains a ^aINTL kludge
     line (therefore this statement is only meant for ZoneGate
     routing). The syntax is: 

          GATEROUTE <zonegate> {<dest>} 

       '<Zonegate>' is the Node where mail to any System matching
     <dest> shall be routed through.  


     Special Configuration Keywords                      GATEROUTE


     Page 40            TrapToss' Fantastic Manual             Page 40


  8.29. (NO)IGNORESENT     

       Tells TrapToss (if in export/scan mode) to export all Mail
     above the HiWater mark regardless of the state of their Sent
     bit. Useful for re-scanning the message base: 1) delete the
     HiWater mark ('1.MSG'), 2) call 'TrapToss EXPORT IGNORESENT' and
     all messages will - depending on the contents of their Seen-By
     lines - be exported again.  

       Defaults To NOIGNORESENT.  

  8.30. IOBUFFERSIZE     

       Sets the buffer size for buffered I/O. For example: 

          IOBUFFERSIZE 8192 

       this sets 8K buffers per file. Please note that this switch is
     only available when running under Kickstart 2.0 or higher!
     Default is 'IOBUFFERSIZE 0', meaning unbuffered I/O.  

  8.31. (NO)KILLSENT     

       Normally TrapToss kills every Netmail message with the
     KillSent-Bit set when exporting. To disable this mode, you can
     set TrapToss to NOKILLSENT.  

       Default is KILLSENT.  

  8.32. MAIN     

       This keyword specifies the main Address to be used in
     pass-through Areas.  It is intended for multi-networking. Like
     'ALLOW' or 'STRIP' this keyword is meant to sit below an AREA
     line, it locally changes the Address for the given Area: 

          AREA FOURTYNINE MAIL:Echo/FourtyNine 49:23/5 6 7 .1 .2
          MAIN 49:15/7

       sets your main Address to 49:15/7 in the pass-through Area
     FOURTYNINE.  

       Default is the global main Address defined NODE.  

  8.33. (NO)MATRIX     

       In export/scan mode this causes TrapToss to export Matrix-Mail
     (Netmail) as well as EchoMail. If you are using another Netmail
     exporter (oMMM, for instance) you should set NOMATRIX.  

       Defaults to MATRIX.  





     Special Configuration Keywords                     (NO)MATRIX


     Page 41            TrapToss' Fantastic Manual             Page 41


  8.34. (NO)MATRIXONLY     

       In SCAN, EXPORT and RENUMBER mode this key tells TrapToss to
     process only Matrix-Mail (Netmail) and skip echomail. Although
     this works in conjunction with (NO)MATRIX, it doesn't make much
     sense to specify NOMATRIX and MATRIXONLY... :-) 

       The default mode is NOMATRIXONLY 

  8.35. MSGFILTER     

       This Keyword causes TrapToss to filter certain Netmail
     messages addressed to your system. Its syntax is 

          MSGFILTER FROM|TO|SUBJ|DATE <pattern> [<file> [<cmd>]] 

       The first option selects the part of the message that should
     match the given AmigaDOS <pattern> (this is only true for
     Kickstart 2.04 or higher; if you're running Kickstart 1.3,
     pattern can only contain '?' or '#?' as wildcard characters). If
     no other option is set, messages with a matching pattern will
     simply be filtered out (deleted) during import.  

       The <file> argument allows you to specify a file name. In this
     case the message will be converted to RFC-822 and appended to
     the given file. This is useful if you want the message to be
     processed by some programs (an AreaFix program, for instance)
     later on.  

       If <cmd> is specified, the given program will be called for
     each message matching the pattern. TrapToss will then either
     delete the message (if the return code was 0), post it to the
     local message base (for a return code of 5), retry for other
     matches (if the returncode was 10), or set the given secondary
     return code and exit processing messages (for returncodes
     greater or equal to 20).  

       Please note that there is an interaction between this keyword
     and DELETEEMPTYMSGS: messages that are detected by MSGFILTER
     will never be deleted by DELETEEMPTYMSGS, you have to take care
     of that yourself, i.e. specify correct return values. Please
     note also that in IMPORT mode messages will currently not be
     deleted, even if the called program returned 0. This behaviour
     may change in future versions of TrapToss, so don't rely on it! 

  8.36. (NO)NEEDORIGIN     

       Since version 1.22 TrapToss does not require echomail
     containing an origin line.  To enable tossing of echomail
     without a valid origin line, please specify 

          NONEEDORIGIN

       in your config file, 


     Special Configuration Keywords                 (NO)NEEDORIGIN


     Page 42            TrapToss' Fantastic Manual             Page 42


          NEEDORIGIN

       if you insist on a valid origin line. Please note that the
     current default value is "NONEEDORIGIN", but this may be subject
     to change. To be save, specify explicitly what you want. See
     also (NO)NEEDTEAR.  

  8.37. (NO)NEEDTEAR     

       TrapToss (version 1.22 and above) no longer needs echomail
     containing tearlines; per default (NONEEDTEAR) TrapToss
     tosses/imports echomail w/o a tear line as well.  To require
     tear lines for echo mail, please specify 

          NEEDTEAR

       See also (NO)NEEDORIGIN.  

  8.38. NETDUPES     

       Like DUPES this keyword specifies what to do with Netmail
     duplicates. It has all modes introduced with DUPES, plus an
     additional 'RETURN' mode. The possible modes are 

          NETDUPES BAD
          NETDUPES DELETE
          NETDUPES IGNORE
          NETDUPES RETURN

       'BAD' causes duplicate Netmail messages to be moved to
     Bad.Msgs, 'DELETE' will simply erase Netmail dupes, 'IGNORE'
     causes them to be passed on and 'RETURN' causes them to be
     bounced with a short notice.  

       It is recommended to use 'IGNORE' or 'RETURN' for Policy4
     compliant behaviour. Default is 'NETDUPES BAD'.  

  8.39. NEWMODAYS     

       Since Version 1.30 TrapToss creates new compressed mail
     bundles (also called .MOx files) every day. Using this keyword
     you can specify the number of days files should be added to an
     existing bundle before creating a new one. The syntax is: 

          NEWMODAYS <n> 

       where <n> is the number of days between new .MOx bundles. If
     <n> is 0, TrapToss will always create new bundles, if <n> is -1,
     no new bundle will be created before the current bundle has been
     sent (this behaviour is compatible to TrapToss 1.23 and
     before).  

       Please note that the method used to create bundles has
     changed.  TrapToss 1.23 (and lower) used to start with an '.MO0'


     Special Configuration Keywords                      NEWMODAYS


     Page 43            TrapToss' Fantastic Manual             Page 43


     file extension regardless of the current day of week. This has
     caused some misunderstandings, we therefore decided to change
     this behaviour.  If possible TrapToss now only creates files
     with extensions named after the current day of week.  

       Default is NEWMODAYS 1.  

  8.40. (NO)OLDSTYLEFLO     

       Sets the .FLO file compatibility mode, i.e. .FLO files will be
     named 'hhhhhhhh.xLO', where <hhhhhhhh> is an 8-digit hex number
     and <x> is one of 'F', 'D', 'H' or 'C'. If NOOLDSTYLEFLO is set
     TrapToss will create files named 'z.n.f.p.xLO', where 'z' is the
     Zone number, 'n' is the Net number, 'f' is the Node number, 'p'
     is the Point number (all decimal) and 'x' is one of 'F', 'D',
     'H', or 'C'.  

       Default is NOOLDSTYLEFLO.  

  8.41. (NO)OLDSTYLEMO     

       Causes TrapToss to switch to 'compatibility mode' for .MOx
     files.  All filenames will contain eight hex digits containing
     the difference of destination and origin Nets and Nodes. This
     2-dimensional format cannot tell the difference between
     '2:310/6' and '1:310/6' and will create the same filename for
     both. Therefore this option should only be used if you are not
     using a modern Mailer (like TrapDoor versions higher than 1.70)
     which can use 4-dimensional file names.  

       Defaults to NOOLDSTYLEMO. This switch will be overridden if
     'FORCE4DMO' is set.  

  8.42. ONLY     

       Using this option in conjunction with SCAN, EXPORT or RENUMBER
     you can specify a sub-set of Areas to be processed by TrapToss.
     The syntax used is: 

          ONLY <pat> 

       Where <pat> is an AmigaDOS compatible pattern containing the
     name(s) of the echomail Area(s) to be scanned. For full featured
     AmigaDOS patterns you need Kickstart Release 2.04 or higher,
     otherwise only '?' and '#?' are supported. Here is an example of
     a full featured pattern: 

          ONLY (TRAPDOOR|AMIGA) 

       This will cause TrapToss only to scan the 'TRAPDOOR' and
     'AMIGA' Areas.  Please note that ONLY does not affect the
     scanning of your private mail directory (use (NO)MATRIX to
     scan/skip Netmail).  



     Special Configuration Keywords                           ONLY


     Page 44            TrapToss' Fantastic Manual             Page 44


       Default is 'ONLY #?' 

  8.43. (NO)OUT4D     

       Tells TrapToss to create 4-dimensional (new style) .OUT files.
     Use this option if you are using a modern Mailer (like TrapDoor)
     which recognizes these new style files.  

       Default is OUT4D.  

  8.44. (NO)PATH4D     

       Switches TrapToss to 4-dimensional Path mode, i.e. all Zones
     will be added to the Path lines. You can only use this option if
     all systems you export your Mail to are able to process
     4-dimensional Path lines.  

       Default is NOPATH4D which produces backwards-compatible Path
     lines.  

  8.45. (NO)QUICKIMPORT     

       Causes TrapToss to import messages without processing the
     kludge lines.  This is especially useful for Points or Nodes
     that use IMPORT, because it skips most of the re-exporting
     overhead. This switch only has effect during IMPORTing, TOSSing
     is not covered. For compatibility with older versions of
     TrapToss you can set NOQUICKIMPORT.  

       Default is QUICKIMPORT.  

  8.46. (NO)RTD     

       Adds a little bit of security to Seen-By checking: also the
     Nodes in the Path line of each message is checked on
     exporting/scanning/tossing; exporting is suppressed for Nodes
     found in the Path line.  

       Default setting is NORTD.  

  8.47. (NO)SEEN4D     

       Like 'PATH4D', causes TrapToss to add the Zone number to all
     Seen-By lines. Default is NOSEEN4D, which creates 2-dimensional
     Seen-By lines.  

  8.48. (NO)SETHIWATER     

       Causes TrapToss to set the hiwater mark after importing or
     exporting.  

       The default setting for this Switch is SETHIWATER on
     export/scan mode, otherwise NOSETHIWATER.  



     Special Configuration Keywords                 (NO)SETHIWATER


     Page 45            TrapToss' Fantastic Manual             Page 45


  8.49. (NO)SETSENT     

       Tells TrapToss whether to set the Sent bit in messages
     exported or not.  

       Default is SETSENT for TOSS, SCAN and EXPORT, NOSETSENT for
     IMPORT.  

  8.50. (NO)SMALLDUPCHECK     

       If 'SMALLDUPCHECK' is set this tells TrapToss to check the
     message Base (in this case: all messages of the same Area) for
     duplicates while importing.  Unlike 'DUPCHECK' the incoming
     message is compared only to stored messages of the same Area.
     This is useful for Points on small systems (Floppy based
     systems), who don't want to keep large 'Duplicate' files.  

       In case you have many messages stored in an Area this may well
     turn out to be less efficient than DUPCHECK.  

       Default setting is NOSMALLDUPCHECK.  

  8.51. STRIP     

       Like 'ADD' this is a 'local' keyword, i.e. it has to occur
     after an 'AREA' line and defines a number of (wildcarded) Nodes
     to be stripped from Seen-By lines of messages in this Area.  

       Example: 

          AREA TRAPDOOR Mail:TrapDoor.Area 310/6 310/3 310/6.4 310/6.5
          STRIP 3160/*

  8.52. TEARLINE     

       Defines the Tearline handling of TrapToss. You can select
     'Replace', which replaces existing TearLines with '---
     TrapToss...', 'Leave', which just leaves the Tearline as is or
     'None' which simply creates '---' as a Tearline (recommended if
     ^aPID lines are being created).  

       This only has effect on Local EchoMail messages.  

       Default mode is 'TEARLINE Replace'.  

  8.53. TIMEZONE     

       Use this to tell TrapToss what timezone you are in. TrapToss
     will put this information in "Via" lines when it passes Netmail
     to other systems.  

       Example: 

          TIMEZONE "CET"


     Special Configuration Keywords                       TIMEZONE


     Page 46            TrapToss' Fantastic Manual             Page 46


       The default is no timezone at all, meaning local time...  

  8.54. UNPACKER     

       This keyword takes an Unpacker command (a CLI command) and a
     (wildcarded) list of Nodes to use the unpacker for.  

       It is almost obsolete, though still there for compatibility
     with older versions of TrapToss and for special setups using
     unsupported packer types. It lets you select special unpackers
     for special Nodes. Usually 'DEFAULTUNPACKERS' should suit your
     needs and be given preference over 'UNPACKER'.  

       Example: 

          UNPACKER "LHArc x" 310/6 310/11
          UNPACKER "Zoo x" 310/*

       If no specific unpacker has been specified for a Node,
     TrapToss will look inside the mail bundle to find out what
     compression program had been used to create the file. TrapToss
     knows about Arc, Zoo and LhArc bundles, and will use 

          "Arc x"       for ARCMail
          "Lha -m -X e" for LHArcMail
          "Zoo x:O"     for ZOOMail
          "UnZip"       for ZIPMail
          "UnArj e -y"  for ARJMail
          "rx XArc e"   for unknown packers

       In case you prefer your own super-duper versatile
     de-compressor command for all bundles (e.g. "RX XArc X") you may
     as well say 

          UNPACKER "RX XArc x" *

  8.55. (NO)V22HEADER     

       Creates V2.2 packet types. Otherwise TrapToss will create V2.0
     packets.  Please note that V2.2 packets are not compatible with
     most other FidoNet mail processors (see FSC39 and FSC48 for a
     compatible version of 4D packets)! 

       Defaults to NOV22HEADER.  

  8.56. (NO)WRITEBACK     

       Causes TrapToss to write-back the entire message after
     exporting. If NOWRITEBACK is set, only the message header will
     be written back (thus changes of Seen-By, Path, MsgID, etc.
     lines cannot be viewed in the message Editor).  

       Default is WRITEBACK.  



     Special Configuration Keywords                  (NO)WRITEBACK


     Page 47            TrapToss' Fantastic Manual             Page 47


  8.57. ZONE     

       Compatibility only: you may omit a default Zone entry in your
     'NODE' line. You then have to specify 'ZONE z' to define the
     Zone you are in (default Zone).  

  8.58. ZONEGATE     

       This is the global variation of the GATE statement. It allows
     you to act as an EchoMail ZoneGate, plus a lot of other
     unpleasant things.  

       Syntax: 

          ZONEGATE <wild> {seenby-list} 

       What it does is: For each Node that matches <wild>, it will
     remove all the Nodes in the SEEN-BY: lines and replace them with
     the Nodes on the {seenby-list} instead.  

  9. Reserved Keywords    

       The following keywords are considered private and are reserved
     for future use; please do not specify any of these in your
     Config files: 

          NOPKTDATE
          NOPKTFORWARD
          PATHPROTOCOL
          PATHPROTOCOLFILE
          PKTDATE
          PKTFORWARD

  10. Wildcards     

       Some keywords accept wildcards as parameters. For those who
     like splitting hairs, here is the exact definition of a
     wildcard: 

     Syntax:
     ­­­­­­­

     Wildcard = <V, T, P, S>

     V = {<WFIDO>, <FQFA>, <WCARD>, <W1>, <NW>, <ZW>, <WC>, <ZF>, <Z>, <ZIF>}

     T = {0, ..., 9, ?, *, :, /, .}
          ¯       ¯  ¯  ¯  ¯  ¯  ¯
     P:

     <WFIDO> -> <FQFA> | <WCARD>

     <FQFA>  -> <ZONE><Z>/<Z><POINT>
                         ¯


     Wildcards


     Page 48            TrapToss' Fantastic Manual             Page 48


     <ZONE>  -> # | <Z>:
                       ¯
     <POINT> -> # | .<Z>
                    ¯
     <WCARD> -> <ZW><W1> | *
                           ¯
     <W1>    -> <WC>/<NW> | *
                    ¯       ¯
     <NW>    -> <WC> | <WC>.<WC>
                           ¯
     <ZW>    -> # | <ZF>: | *:
                        ¯   ¯¯
     <WC>    -> * | <ZF>
                ¯
     <ZF>    -> <Z> | ?
                      ¯
     <Z>     -> <Z><ZIF> | <ZIF>

     <ZIF>   -> 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
                ¯   ¯   ¯   ¯   ¯   ¯   ¯   ¯   ¯   ¯

     S = <WFIDO>

      -------------------------------------------------------------------------------

     Semantics:
     ­­­­­­­­­­

     ? ... all of this type, e.g: "x:y/z.?" = all Points (including .0) of Node x:y/z
     ¯                              ¯ ¯ ¯¯
     * ... all of this type and all types to the right which are not specified,
     ¯     eg.: "x:*" = "x:?/?.?"; a single asterisk "*" means "?:?/?.?"
                  ¯¯      ¯¯¯¯¯¯                      ¯         ¯¯¯¯¯¯¯

     Rules for information not specified:
     ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
     * (<ZONE> or <ZW>) == # (not given) means 'this Zone'

     * <POINT> == # means .0 (i.e. the Node w/o its Points)

      -------------------------------------------------------------------------------

     Limits:
     ­­­­­­­

     Zone:  1 <= <Z> <= 65535
     Net:   0 <= <Z> <= 65535
     Node:  0 <= <Z> <= 65535
     Point: 0 <= <Z> <= 65535







     Wildcards


     Page 49            TrapToss' Fantastic Manual             Page 49


  11. Example Setup    

  11.1. Point Setup    

       Here is a sample TrapToss configuration file for Points
     (should be named MAIL:TrapToss.Cfg or MAIL:Fido.Cfg): 

     ; ************************************************************************
     ; ***                                                                  ***
     ; ***                Sample TrapToss.Cfg file for Points               ***
     ; ***                       ¯¯¯¯¯¯¯¯¯¯¯¯                               ***
     ; *** ---------------------------------------------------------------- ***
     ; ***  This file is a tiny setup for TrapToss to import and export     ***
     ; ***  EchoMail. Please modify to suit your personal needs.            ***
     ; *** ---------------------------------------------------------------- ***
     ; ***  TrapToss.Cfg is compatible to the GCF (Global Configuration     ***
     ; ***  File) Standard. If you want to use it in conjunction with other ***
     ; ***  programs using the GCF, TrapList, for instance, simply rename   ***
     ; ***  this file as "FIDO.CFG"                                         ***
     ; ************************************************************************

     ; ************************************************************************
     ; ***  PUBLIC SECTION -- accessible by other programs, insert global   ***
     ; ***  ­­­­­­­­­­­­­­    information here...                           ***
     ; ************************************************************************

     ; Here comes my full 4-dimensional fido Address as well as my fake Address
     NODE 2:310/6.4
     FAKE 3160/4

     ; ************************************************************************
     ; ***  TRAPTOSS PRIVATE SECTION -- Here goes information exclusively   ***
     ; ***  ­­­­­­­­­­­­­­­­­­­­­­­­    accessible by TrapToss...           ***
     ; ************************************************************************

     ;Section Identifier
     [TRAPTOSS]

     ; All the Netmail goes via my Boss
     ROUTE Normal 2:310/6 *

     ; Add your favourite Cruncher, Muncher or Packer command(s) here, e.g.
     ; (an empty list stands for *:*/*.*, meaning "the rest of the world")
     ; PACKER "LHArc a" 2:310/6 2:310/3 1:*/*
     ; PACKER "Arc a" *

     PACKER "LHArc a" *

     ; Packertypes:    ARC    ZOO       LHARC    ZIP         ARJ          Others
     ;------------------------------------------------------------------------------
     DEFAULTUNPACKERS "Pkax" "Zoo x:O" "Lha e" "UnZip -xnj" "UnArj e -y" "rx XArc e"

     ; This for threaded messages
     LINKMSGS


     Example Setup                                      Point Setup


     Page 50            TrapToss' Fantastic Manual             Page 50


     ; Most Bosses do not like 4-dimensional entries in Seen-By lists,
     ; so just strip them (if your Boss uses a 4-dimensional FrontDoor
     ; setup, strip your fake Address instead)
     STRIPNODES 310/6.4

     ; Here we go: Those are the Message-Areas I currently get. The format
     ; is basically the same as in good old AREAS.BBS, except that the Area
     ; name comes first, and you have to list *your* Address as well if you
     ; want that Area (this is due to Node compatibility)
     ;
     ;Key Areaname           Directory Name          Nodes (Point: myself + Boss)
     ;¯¯¯ ¯¯¯¯¯¯¯¯           ¯¯¯¯¯¯¯¯¯¯¯¯¯¯          ¯¯¯¯¯
     NETMAIL MAIL_DIR        MAIL:Matrix
     AREA BAD                MAIL:Bad.Msgs

     AREA A3000              MAIL:A3000.Area         310/6.4 310/6
     AREA MAD                MAIL:Mad.Area           310/6.4 310/6
     AREA TECHNICS           MAIL:Technics.Area      310/6.4 310/6
     AREA TRAPDOOR           MAIL:TrapDoor.Area      310/6.4 310/6
     AREA INTERCOOK          MAIL:InterCook.Area     310/6.4 310/6
     AREA AUSTROCHAT.AUS     MAIL:ViennaChat.Area    310/6.4 310/6
     AREA NEWSOFT.AUS        MAIL:Software.Area      310/6.4 310/6
     AREA TRAPDOOR.BETA      MAIL:TrapDoorBeta.Area  310/6.4 310/6

































     Example Setup                                      Point Setup


     Page 51            TrapToss' Fantastic Manual             Page 51


  11.2. Node Setup    

       Here is a sample TrapToss configuration file for Nodes (should
     be named MAIL:TrapToss.Cfg or MAIL:Fido.Cfg): 

     ; ************************************************************************
     ; ***                                                                  ***
     ; ***                Sample TrapToss.Cfg file for Nodes                ***
     ; ***                       ¯¯¯¯¯¯¯¯¯¯¯¯                               ***
     ; *** ---------------------------------------------------------------- ***
     ; ***  This file is a tiny setup for TrapToss to import and export     ***
     ; ***  EchoMail. Please modify to suit your personal needs.            ***
     ; *** ---------------------------------------------------------------- ***
     ; ***  TrapToss.Cfg is compatible to the GCF (Global Configuration     ***
     ; ***  File) Standard. If you want to use it in conjunction with other ***
     ; ***  programs using the GCF, TrapList, for instance, simply rename   ***
     ; ***  this file as "FIDO.CFG"                                         ***
     ; ************************************************************************

     ; ************************************************************************
     ; ***  PUBLIC SECTION -- accessible by other programs, insert global   ***
     ; ***  ­­­­­­­­­­­­­­    information here...                           ***
     ; ************************************************************************

     ; Here comes my full 4-dimensional fido Address as well as my fake Address
     NODE     2:310/6.0
     AKA      2:3160/0 2:3164/0
     POINTNET 3160

     DOMAIN   "FidoNet"
     ORIGIN   "The Mad House, Vienna, Austria [ZYX]"
     TIMEZONE "CET"

     INBOUND  "Mail:Inbound"
     OUTBOUND "Mail:Outbound"

     ; ************************************************************************
     ; ***  TRAPTOSS PRIVATE SECTION -- Here goes information exclusively   ***
     ; ***  ­­­­­­­­­­­­­­­­­­­­­­­­    accessible by TrapToss...           ***
     ; ************************************************************************

     ;Section Identifier
     [TrapToss]

     UNATTENDED      ; this is an unattended system

     LOGLEVEL 4      ; some logging
     LOGFILE Mail:TrapToss.Log

     SCREENMODE None

     FORCE4DMO       ; I run the new TrapDoor

     LINKMSGS        ; replylink messages


     Example Setup                                       Node Setup


     Page 52            TrapToss' Fantastic Manual             Page 52


     DUPCHECK        ; and check for duplicates

     ; put mail on Hold for Points
     CHANGE Crash  Hold 2:310/6.* 2:3160/*
     CHANGE Direct Hold 2:310/6.* 2:3160/*
     CHANGE Normal Hold 2:310/6.* 2:3160/*

     ; select EchoMail flavour for other Nodes
     CHANGE Normal Hold   2:310/15  2:242/25 2:281/100 2:302/810
     CHANGE Normal Crash  2:310/3   2:310/11 2:310/30
     CHANGE Normal Direct 2:253/140

     ; what to do with Netmail for these Nodes
     SEND Crash  2:310/12 2:310/19 2:310/30 2:310/42  2:310/90  2:2/527
     SEND Direct 2:310/2  2:310/5  2:310/8  2:310/10  2:310/13  2:313/11 2:241/7504
     SEND Hold   2:310/15 2:310/42 2:242/25 2:281/100 2:302/810

     ; route the rest of the Netmail
     ROUTE Direct 2:253/140   253/140.* 253/*.*
     ROUTE Crash  2:310/30    341/23.*
     ROUTE Crash  2:310/1     310/1.*  31/0.*
     ROUTE Crash  2:310/0     310/0.*  310/7.*
     ROUTE Hold   2:313/1     313/1.*  313/0.*
     ROUTE Crash  2:310/11    310/11.* 1:*   3:*   4:*   5:* 6:* \
                              2/3.*    2/4.* 2/5.* 2/6.*
     ROUTE Crash  2:310/3     310/3.* *

     ; these Nodes want LHArc compressed mail
     PACKER "LhArc -x0 -f -u -m a" 310/19 310/42 310/6.3 310/6.4 310/6.7

     ; Packertypes:    ARC    ZOO       LHARC    ZIP         ARJ          Others
     ;------------------------------------------------------------------------------
     DEFAULTUNPACKERS "Pkax" "Zoo x:O" "Lha e" "UnZip -xnj" "UnArj e -y" "rx XArc e"

     ; remove my Points from the seen-bys, but
     ; don't forget to add myself again!
     STRIPNODES 2:3160/* 2:310/6.*
     ADDNODES   2:310/6.0

     ; Finally, here are my Areas:
     ;
     ;key areaname           directory               Nodes who get it (I must be first!)
     ;¯¯¯ ¯¯¯¯¯¯¯¯           ¯¯¯¯¯¯¯¯¯               ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
     NETMAIL MAIL_DIR       MAIL:matrix              310/6

     Area BAD               MAIL:BAD

     Area AMIGA.GER         MAIL:Echo/AMIGA.GER      310/6 310/11 310/42
     Area AMIPROG.GER       MAIL:Echo/AMIPROG.GER    310/6 310/11 310/6.2 310/6.6
     Area AUSTROCHAT.AUS    MAIL:Echo/AUSTROCHAT     310/6 310/3  310/6.4 310/6.6 310/6.7 310/42
     Area DLG_BETA          MAIL:Echo/DialogBeta     310/6 253/140
     Area DLG_INFO          MAIL:Echo/DialogInfo     310/6 253/140 281/100 310/42 302/810

     ; here is a read-only echo I get from 69:1134/300


     Example Setup                                       Node Setup


     Page 53            TrapToss' Fantastic Manual             Page 53


     Area KINKNET           MAIL:Echo/KINKNET        310/6
     Allow 69:1134/300

     ; the following three echoes are being passed-through
     ; to one of my Points -- I don't care to read MSDos echoes.
     Area LAN               MAIL:                    310/11 310/6.7
     Area OS2               MAIL:                    310/11 310/6.7
     Area PS_2              MAIL:                    310/11 310/6.7
















































     Example Setup                                       Node Setup


     Page 54            TrapToss' Fantastic Manual             Page 54


  11.3. MultiNet Setup    

       Here is a sample TrapToss configuration file for MultiNet
     Nodes (should be named MAIL:TrapToss.Cfg or MAIL:Fido.Cfg): 

     ; ************************************************************************
     ; ***                                                                  ***
     ; ***           Sample MultiNet TrapToss.Cfg file for Nodes            ***
     ; ***                  ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯                           ***
     ; *** ---------------------------------------------------------------- ***
     ; ***  This file is a tiny setup for TrapToss to import and export     ***
     ; ***  EchoMail. Please modify to suit your personal needs.            ***
     ; *** ---------------------------------------------------------------- ***
     ; ***  TrapToss.Cfg is compatible to the GCF (Global Configuration     ***
     ; ***  File) Standard. If you want to use it in conjunction with other ***
     ; ***  programs using the GCF, TrapList, for instance, simply rename   ***
     ; ***  this file as "FIDO.CFG"                                         ***
     ; ************************************************************************

     ; ************************************************************************
     ; ***  PUBLIC SECTION -- accessible by other programs, insert global   ***
     ; ***  ­­­­­­­­­­­­­­    information here...                           ***
     ; ************************************************************************

     ; Here comes my full 4-dimensional fido Address as well as my fake Address
     NODE     2:310/6.0
     AKA      2:3160/0 2:3164/0
     POINTNET 3160

     DOMAIN "AmigaNet"  39:200/6  39:* 40:* 41:*
     DOMAIN "GlobalNet" 54:6101/6 51:* 52:* 53:* 54:*
     DOMAIN "FidoNet"

     ORIGIN   "The Mad House, Vienna, Austria [Zyxel 16K8]"
     TIMEZONE "CET"

     INBOUND      "Mail:Inbound"
     OUTBOUND     "Mail:Outbound"
     NODELISTPATH "Nodelist:"

     ; ************************************************************************
     ; ***  TRAPTOSS PRIVATE SECTION -- Here goes information exclusively   ***
     ; ***  ­­­­­­­­­­­­­­­­­­­­­­­­    accessible by TrapToss...           ***
     ; ************************************************************************

     ;Section Identifier
     [TrapToss]

     UNATTENDED      ; this is an unattended system

     LOGLEVEL 4      ; some logging
     LOGFILE Mail:TrapToss.Log

     SCREENMODE None ; no screen desired


     Example Setup                                   MultiNet Setup


     Page 55            TrapToss' Fantastic Manual             Page 55


     FORCE4DMO       ; I run the new TrapDoor

     LINKMSGS        ; replylink messages
     DUPCHECK        ; and check for duplicates

     ; I have a Nodelist for these Zones, so allow bouncing there
     BOUNCE 1:* 2:* 4:* 5:* 6:* 9:* 41:* 40:*

     ; put mail on Hold for Points
     CHANGE Crash  Hold 2:310/6.* *:3160/* 39:200/6.* 54:6101/6.*
     CHANGE Direct Hold 2:310/6.* *:3160/* 39:200/6.* 54:6101/6.*
     CHANGE Normal Hold 2:310/6.* *:3160/* 39:200/6.* 54:6101/6.*

     ; select EchoMail flavour for other Nodes
     CHANGE Normal Hold   2:310/15  2:242/25   2:281/100 2:302/810
     CHANGE Normal Crash  2:310/3   2:310/11   2:310/30
     CHANGE Normal Direct 2:253/140 41:200/401 41:243/12

     ; what to do with Netmail for these Nodes
     SEND Crash  2:310/12 2:310/19 2:310/30 2:310/42  2:310/90  2:2/527
     SEND Direct 2:310/2  2:310/5  2:310/8  2:310/10  2:310/13  2:313/11 2:241/7504
     SEND Hold   2:310/15 2:310/42 2:242/25 2:281/100 2:302/810

     ; route the rest of the Netmail
     ROUTE Direct 2:253/140   253/140.* 253/*.*
     ROUTE Crash  2:310/30    341/23.*
     ROUTE Crash  2:310/1     310/1.*  31/0.*
     ROUTE Crash  2:310/0     310/0.*  310/7.*
     ROUTE Hold   2:313/1     313/1.*  313/0.*
     ROUTE Crash  2:310/11    310/11.* 1:*   3:*   4:*   5:* 6:* \
                              2/3.*    2/4.* 2/5.* 2/6.*
     ROUTE Crash  2:310/3     310/3.* *

     ; these Nodes want LHArc compressed mail
     PACKER "LhArc -x0 -f -u -m a" 310/19 310/42 310/6.3 310/6.4 310/6.7

     ; Packertypes:    ARC    ZOO       LHARC    ZIP         ARJ          Others
     ;------------------------------------------------------------------------------
     DEFAULTUNPACKERS "Pkax" "Zoo x:O" "Lha e" "UnZip -xnj" "UnArj e -y" "rx XArc e"

     ; remove my Points from the seen-bys, but
     ; don't forget to add myself again!

     FORDOMAIN FidoNet   STRIP 2:310/6.* 2:3160/*
     FORDOMAIN FidoNet   ADD   2:310/6

     FORDOMAIN AmigaNet  STRIP 39:200/6.* 39:3160/*
     FORDOMAIN AmigaNet  ADD   39:200/6

     FORDOMAIN GlobalNet STRIP 54:6101/6.* 54:3160/*
     FORDOMAIN GlobalNet ADD   54:6101/6


     ; Finally, here are my Areas:


     Example Setup                                   MultiNet Setup


     Page 56            TrapToss' Fantastic Manual             Page 56


     ;
     ;key areaname           directory               Nodes who get it (I must be first!)
     ;¯¯¯ ¯¯¯¯¯¯¯¯           ¯¯¯¯¯¯¯¯¯               ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
     NETMAIL MAIL_DIR       MAIL:matrix              310/6

     Area BAD               MAIL:BAD

     Area AMIGA.GER         MAIL:Fido/AMIGA.GER      310/6 310/11 310/42
     Area AMIPROG.GER       MAIL:Fido/AMIPROG.GER    310/6 310/11 310/6.2 310/6.6
     Area AUSTROCHAT.AUS    MAIL:Fido/AUSTROCHAT     310/6 310/3  310/6.4 310/6.6 310/6.7 310/42

     ; the following three echoes are being passed-through
     ; to one of my Points -- I don't care to read MSDos echoes.
     Area LAN               MAIL:                    310/11 310/6.7
     Area OS2               MAIL:                    310/11 310/6.7
     Area PS_2              MAIL:                    310/11 310/6.7

     ; These are my AmigaNet echoes
     Area AMI_MAIL          MAIL:ANet/AMI-MAIL       39:200/6 41:200/439.0
     Area ANOTHERONE        MAIL:ANet/OneMore        39:200/6 41:200/439.0







  12. Caveats     

       Some Points may encounter problems sending packets to their
     Bosses. This is sometimes caused by Programs incompatible to the
     FSC39 proposal. In this case try NOFSC39 or even NOFSC48 (for
     old-style packets).  

       TrapToss uses the filenotes of .MSG files to speed up some of
     its operations. If programs modify the filenotes, TrapToss will
     operate more slowly.  

       TrapToss has many switches that can cause it to produce
     duplicate messages. Be careful when using the GATE, STRIP,
     STRIPNODES and ZONEGATE statements.  

       TrapToss can be made FidoNet-incompatible. The SEEN4D and
     PATH4D options should not be used in a FidoNet environment. They
     are reserved for TrapToss-exclusive (private) networks.  

       When you are running a 4D multi-boss Point (with more than one
     Point Address) you should make certain that you are creating 4D
     packets (i.e. that you have not turned off FSC39, or that you
     have explicitely turned on FSC48 or V22HEADER).  Otherwise the
     Point part of your Address might get lost, causing your Boss to
     throw away your packets.  

       The MSGFILTER command currently only supports one of FROM, TO,


     Caveats


     Page 57            TrapToss' Fantastic Manual             Page 57


     SUBJ, or DATE. Statements in the form of 

          MSGFILTER FROM foo TO bar

       are currently not allowed. This might change in the future. If
     you use multiple MSGFILTER statements please note also that you
     have to take care of the order these statements appear in: 

          MSGFILTER FROM #?
          MSGFILTER TO AreaFix t:areafix.msg "AreaFix t:areafix.msg"

       This will never call AreaFix, because all messages are alread
     matched by the first pattern.  






  13. Future     

       The optimist sees the doughnut.  
       The pessimist sees the hole.  
       I see TrapToss everywhere.  
































     Future


     Page 58            TrapToss' Fantastic Manual             Page 58


  14. Registration     

       TrapToss is a copyrighted product that has been made available
     to you under the concept of "Shareware". It has never been, nor
     will it ever be in the "Public Domain". You are granted a
     limited license in order to evaluate the program. If, after a 3
     or 4 week period of evaluation, you find that TrapToss suits
     your mail tossing needs, please register. By cooperating with
     this concept you help to ensure continued development of this
     product.  

       Registered users will be shipped a disk with the latest
     release version of TrapToss together with a keyfile. This
     keyfile, once copied to your system, will disable the ShareWare
     reminders that always open when you start or quit TrapToss.  

       Site license information for commercial and government use as
     well as source code licenses can be obtained directly from the
     authors.  

       No person(s) or businesses other than the authors are
     authorized to accept any registration or distribution fees in
     any form whatsoever, except the official registration and
     support centers as specified by the authors. The only people who
     will be acknowledged as registered users are those who have sent
     ATS 350,- (plus another ATS 150,- if you send foreign cheques or
     money orders) to: 

                           TrapDoor Development
                            Maximilian Hantsch
                      Matzleinsdorfer Platz 3-4/3/10
                                A-1050 Wien
                             Austria / Europe

     or registered at one of the registration and support centers as
     specified by the authors. A list of these can be found in the
     file "SupportCenters.txt".  

       As one of the safest and possibly easiest ways to send in your
     registration fee from other countries, we would suggest an
     international postal money order -- your local post office will
     happily provide you with more information about this. It also
     has the advantage that the exchange of currencies is handled
     automatically and the surcharge is negligible.  

       Alternatively, you can either send us a Eurocheque payable to
     Maximilian Hantsch in Austrian Schillings or have your bank
     transfer the registration fee to the "Österreichische
     Postsparkasse (PSK)" (BLZ 60000), account 6.777.234, "Maximilian
     Hantsch". Beware: International transfers via banks are rather
     expensive.  





     Registration


     Page 59            TrapToss' Fantastic Manual             Page 59


       Note: IF YOU SEND CHEQUES, PLEASE SEND ONLY EUROCHEQUES MADE
     OUT IN AUSTRIAN SCHILLINGS! We have to impose a surcharge of ATS
     150,- on all other cheques or money orders.  

       Until now, we have accepted other foreign cheques and money
     orders as well, but our bank has raised the charge for these by
     more than 50% over the past two years to more than ATS 100,- per
     cheque. We can no longer afford this and are thus forced to pass
     on this charge. Sorry.  

       In any case, be sure to provide us with your name, Address,
     Fido Node number and international phone number for our files.
     You can send this information via electronic mail, if you wish.
     If you don't mind, this data will be stored and processed in
     electronic form. There is also a sample registration form you
     can fill out in the file "Registration.txt".  

       Please allow up to eight weeks for delivery.  











  15. Politics     

  15.1. Distribution     

       In a nutshell, TrapToss may be distributed freely as long as
     the following restrictions are met: 

       The distributor may only charge a fee up to the costs of
     obtaining a public domain diskette from Fred Fish. The
     distributor agrees to cease distributing the programs and data
     involved if requested to do so by the authors. The distributor
     may only distribute an unmodified copy of the original program,
     with all the supplied documentation and copyright notices
     intact.  

       For more details, see the chapter called "License".  











     Politics                                         Distribution


     Page 60            TrapToss' Fantastic Manual             Page 60


  15.2. Support     

       The latest version of TrapToss (with all its associated tools)
     is always available for filerequest from FidoNet Node 2:310/6,
     "The Mad House" under the magic filename "TRAPTOSS".  

       If you have any suggestions, bug reports etc., feel free to
     contact the authors of TrapToss at the Address given in the
     chapter "Registration". Additionally, you can reach us at: 

          René Hexel                    Maximilian Hantsch
          Fido: 2:310/6                 Fido: 2:310/6
          Uucp: rh%powidl@cbmvie.co.at  Uucp: max%madvie@cbmvie.co.at

       Also, there is a FidoNet Echomail conference called TRAPDOOR,
     which should be available at major backbones. This conference is
     in English and intended for the users of TrapDoor and TrapToss.
     There, you can freely exchange your experience with TrapToss,
     discuss future enhancements you would like to see etc. The
     authors will participate in the conference and try to assist
     you. The availability of new versions of TrapToss will be
     announced there, too.  











  15.3. License     

       1. This license applies to the product called "TrapToss", a
     set of programs for the Amiga computer, published by René Hexel
     under the concepts of ShareWare, and the accompanying
     documentation, example files and anything else that comes with
     the original distribution. The terms "Programs" and "TrapToss"
     below, refer to this product. The licensee is addressed as
     "you".  

       2. You may copy and distribute verbatim copies of the
     programs' executable code and documentation as you receive it,
     in any medium, provided that you conspicuously and appropriately
     publish only the original, unmodified programs, with all
     copyright notices and disclaimers of warranty intact and
     including all the accompanying documentation, example files and
     anything else that came with the original.  






     Politics                                              License


     Page 61            TrapToss' Fantastic Manual             Page 61


       3. You may not copy and/or distribute these programs without
     the accompanying documentation and other additional files that
     came with the original. You may not copy and/or distribute
     modified versions of these programs.  

       4. You may not copy, modify, sublicense, distribute or
     transfer the programs except as expressly provided under this
     license. Any attempt otherwise to copy, modify, sublicense,
     distribute or transfer the programs is void, and will
     automatically terminate your rights to use the programs under
     this license. However, parties who have received copies, or
     rights to use copies, from you under this license will not have
     their licenses terminated so long as such parties remain in full
     compliance.  

       5. By copying, distributing and/or using the programs you
     indicate your acceptance of this license to do so, and all its
     terms and conditions.  

       6. Each time you redistribute the programs, the recipient
     automatically receives a license from the original licensor to
     copy, distribute and/or use the programs subject to these terms
     and conditions. You may not impose any further restrictions on
     the recipients' exercise of the rights granted herein.  

       7. You may not disassemble, decompile, re-source or otherwise
     reverse engineer the programs.  

       8. You may use the programs for a period of up to 30 days for
     evaluation.  After that, you have to register.  

       9. If you wish to incorporate parts of the programs into other
     programs, write to the author to ask for permission.  

       10. You agree to cease distributing the programs and data
     involved if requested to do so by the author.  

       11. You may charge a fee to recover distribution costs. The
     fee for diskette distribution may not be more than the cost to
     obtain a public domain diskette from Fred Fish.  
















     Politics                                              License


     Page 62            TrapToss' Fantastic Manual             Page 62


  15.4. No Warranty    

       THERE IS NO WARRANTY FOR THE PROGRAMS, TO THE EXTENT PERMITTED
     BY APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE
     COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAMS "AS
     IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
     INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
     MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE
     ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAMS IS
     WITH YOU.  SHOULD THE PROGRAMS PROVE DEFECTIVE, YOU ASSUME THE
     COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.  

       IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
     WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY
     REDISTRIBUTE THE PROGRAMS AS PERMITTED ABOVE, BE LIABLE TO YOU
     FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
     CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
     THE PROGRAMS (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA
     BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
     PARTIES OR A FAILURE OF THE PROGRAMS TO OPERATE WITH ANY OTHER
     PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED
     OF THE POSSIBILITY OF SUCH DAMAGES.  




  15.5. Disclaimer     

       No warranty, either express or implied, is made with respect
     to the fitness or merchantability of TrapToss.  

       René Hexel (referred to as "the author") reserves the right to
     not develop any future versions of TrapToss.  

       The author will try to make a good faith attempt at correcting
     any problems if any are discovered, but is in no way required,
     nor bound to correct them.  

       The author neither assumes or accepts any responsibility for
     the use or misuse of these programs. He also will not be held
     liable for damages or any compensation beyond the original
     registration fee due to loss of profit or any other damages
     arising out of the use, or inability to use these programs.  

       Neither Maximilian Hantsch nor René Hexel nor Martin Laubach
     will be liable for any damage arising from the failure of these
     programs to perform as described, or any destruction of other
     programs or data residing on a system attempting to run the
     programs. While we know of no damaging errors, the user of these
     programs uses it at his or her own risk.  






     Politics                                           Disclaimer


     Page 63            TrapToss' Fantastic Manual             Page 63


  16. Acknowledgements     

       The following names are either trademarks or the efforts of
     the person and/or company listed: 

          Amiga, Kickstart, Workbench and AmigaDOS
                         are trademarks of Commodore-Amiga, Inc.
          ARexx by William S. Hawes.
          ARQ by Martin J. Laubach and René Hexel,
                         graphics by Peter Wlcek.
          BinkleyTerm Amiga by Jürgen Hermann.
          BinkleyTerm by Alan D. Applegate, Robert Hartman
                         and Vincent Perriello.
          Bloom County by Berke Breathed.
          Boring by Arnout Grootveld.
          CancelReq/RestoreReq by René Hexel.
          Chameleon Editor and CList by Jürgen Hermann.
          ConfMail by Bob Hartman, Spark Software Inc.
          DLG Professional by TelePro Technologies.
          EchoMail by Jeff Rush.
          EMSI by the EMSC.
          FCfg by René Hexel and Martin Laubach.
          Fido and FidoNet are trademarks of Tom Jennings, Fido Software.
          FFRS by Martin Kuhne
          FFSA by Carl-Christian Kanne.
          License Agreement inspired by Jack Radigan
                         and the GNU General Public License.
          Many Thanks to Tony Miller, Arnout Grootveld, Alexander Holy,
                         Café Heine, Felix Kasza, Johannes Mistelbauer,
                         Manfred Schädler, Mike Oliphant, Many Others,
                         and Werner Schlagnitweit.
          Moral Support by Snooker.
          MS-DOS is a trademark of Microsoft Corporation.
          Special Thanks to all our Registered Users.
          TOPDec by René Hexel.
          TrapDoor, TrapList, TrapPoll and traplist.library
                         by Maximilian Hantsch and Martin Laubach.
          TrapFax by René Hexel, Martin Laubach, and Maximilian Hantsch.
          TrapToss, TrapEdit by René Hexel.
          UNIX is a registered trademark of AT&T.
          Windows is a registered trademark of Microsoft Corp.
          YooHoo by Wynn Wagner III.
          ZModem by Chuck Forsberg.

          Special Xtra-Thanx to Arnout Grootveld for proof-reading
          the manual more than 6 times by now.










     Acknowledgements


     Page I             TrapToss' Fantastic Manual              Page I


  Road Map


        1. Introduction    .....................................    2
        2. Basics    ...........................................    2
        3. Installation    .....................................    3
        4. Configuration    ....................................    4
           4.1. Specifying your Address  .......................    4
           4.2. Fake and PointNet Addresses ....................    4
           4.3. Inbound and Outbound Directories ...............    5
           4.4. Areas    .......................................    5
           4.5. Reply Links   ..................................    7
           4.6. Compressed Mail   ..............................    7
           4.7. Adjusting Seen-By lines  .......................    8
           4.8. Wildcards    ...................................    8
           4.9. Adjusting Seen-By lines Part 2..................    9
           4.10. EchoMail ZoneGate   ...........................    9
           4.11. Duplicate Message Checking  ...................    9
           4.12. Outbound Handling   ...........................   11
           4.13. Netmail Routing   .............................   11
           4.14. Routing through a ZoneGate ....................   13
        5. Speeding up your System .............................   14
           5.1. Quick Import for Points ........................   14
           5.2. Buffered I/O   .................................   14
           5.3. Dupe-Checking and Reply-Linking  ...............   15
        6. Advanced Node Topics  ...............................   16
           6.1. Using the Nodelist  ............................   16
           6.2. Hosts and Bosses  ..............................   16
           6.3. Regions and Hubs  ..............................   17
           6.4. Bouncing    ....................................   18
           6.5. Multiple Networks   ............................   18
        7. Common Configuration Keywords  ......................   20
           7.1. ADDNODES    ....................................   20
           7.2. AKA    .........................................   20
           7.3. AREA    ........................................   20
           7.4. BADPACKETS    ..................................   21
           7.5. (NO)BOSSROUTING    .............................   21
           7.6. BOUNCE    ......................................   21
           7.7. CHANGE    ......................................   21
           7.8. COLO(U)RS    ...................................   22
           7.9. CONFIG    ......................................   22
           7.10. DEFAULTUNPACKERS    ...........................   22
           7.11. DOMAIN    .....................................   23
           7.12. (NO)DUPCHECK    ...............................   23
           7.13. FAKE    .......................................   23
           7.14. (NO)FILEATTACH    .............................   24
           7.15. (NO)FORCE4DMO    ..............................   24
           7.16. (NO)HOSTROUTING    ............................   25
           7.17. (NO)IMPORT    .................................   25
           7.18. INBOUND    ....................................   25
           7.19. KEEP    .......................................   25
           7.20. (NO)LINKMSGS    ...............................   26
           7.21. LOGFILE    ....................................   26
           7.22. LOGLEVEL    ...................................   26


     Road Map


     Page II            TrapToss' Fantastic Manual             Page II


           7.23. LOGWINDOW    ..................................   26
           7.24. NODELISTPATH    ...............................   26
           7.25. NETMAIL    ....................................   27
           7.26. NODE    .......................................   27
           7.27. ORIGIN    .....................................   27
           7.28. OUTBOUND    ...................................   28
           7.29. PACKER    .....................................   28
           7.30. POINTNET    ...................................   28
           7.31. POLL    .......................................   28
           7.32. REMAP    ......................................   28
           7.33. (NO)RENUMBER    ...............................   29
           7.34. ROUTE    ......................................   29
           7.35. (NO)ROUTING    ................................   30
           7.36. (NO)SCAN    ...................................   30
           7.37. (NO)SCANOUTBOUND    ...........................   30
           7.38. SCREENMODE    .................................   30
           7.39. SEND    .......................................   30
           7.40. STATWINDOW    .................................   31
           7.41. STRIPNODES    .................................   31
           7.42. (NO)TOSS    ...................................   32
           7.43. (NO)UNATTENDED    .............................   32
        8. Special Configuration Keywords  .....................   33
           8.1. (NO)4DMSGHEADER    .............................   33
           8.2. ADD    .........................................   33
           8.3. (NO)ADDMSGID    ................................   33
           8.4. (NO)ADDOUTBOUND    .............................   33
           8.5. (NO)ADDPID    ..................................   33
           8.6. ALLOW    .......................................   34
           8.7. (NO)AREAPACKET    ..............................   34
           8.8. (NO)AUTORENUMBER    ............................   34
           8.9. BUFFERSIZE    ..................................   34
           8.10. COPYMSG    ....................................   35
           8.11. (NO)CRASHMAIL    ..............................   35
           8.12. (NO)CRC    ....................................   35
           8.13. (NO)CRCONLY    ................................   35
           8.14. (NO)DELETEEMPTYMSGS    ........................   35
           8.15. (NO)DELROUTEATTACHES    .......................   36
           8.16. DESTINIZEPACKET    ............................   36
           8.17. (NO)DISABLEDIRCACHE    ........................   36
           8.18. (NO)DISABLEMATRIXPID    .......................   36
           8.19. DISALLOW    ...................................   36
           8.20. DUPES    ......................................   37
           8.21. DUPTABLESIZE    ...............................   37
           8.22. (NO)ECHOCRASH    ..............................   37
           8.23. (NO)EXPORT    .................................   38
           8.24. FORDOMAIN    ..................................   38
           8.25. (NO)FSC39    ..................................   38
           8.26. (NO)FSC48    ..................................   39
           8.27. GATE    .......................................   39
           8.28. GATEROUTE    ..................................   39
           8.29. (NO)IGNORESENT    .............................   39
           8.30. IOBUFFERSIZE    ...............................   40
           8.31. (NO)KILLSENT    ...............................   40
           8.32. MAIN    .......................................   40


     Road Map


     Page III           TrapToss' Fantastic Manual            Page III


           8.33. (NO)MATRIX    .................................   40
           8.34. (NO)MATRIXONLY    .............................   40
           8.35. MSGFILTER    ..................................   41
           8.36. (NO)NEEDORIGIN    .............................   41
           8.37. (NO)NEEDTEAR    ...............................   42
           8.38. NETDUPES    ...................................   42
           8.39. NEWMODAYS    ..................................   42
           8.40. (NO)OLDSTYLEFLO    ............................   43
           8.41. (NO)OLDSTYLEMO    .............................   43
           8.42. ONLY    .......................................   43
           8.43. (NO)OUT4D    ..................................   44
           8.44. (NO)PATH4D    .................................   44
           8.45. (NO)QUICKIMPORT    ............................   44
           8.46. (NO)RTD    ....................................   44
           8.47. (NO)SEEN4D    .................................   44
           8.48. (NO)SETHIWATER    .............................   44
           8.49. (NO)SETSENT    ................................   44
           8.50. (NO)SMALLDUPCHECK    ..........................   45
           8.51. STRIP    ......................................   45
           8.52. TEARLINE    ...................................   45
           8.53. TIMEZONE    ...................................   45
           8.54. UNPACKER    ...................................   46
           8.55. (NO)V22HEADER    ..............................   46
           8.56. (NO)WRITEBACK    ..............................   46
           8.57. ZONE    .......................................   46
           8.58. ZONEGATE    ...................................   47
        9. Reserved Keywords   .................................   47
        10. Wildcards    .......................................   47
        11. Example Setup   ....................................   49
           11.1. Point Setup   .................................   49
           11.2. Node Setup   ..................................   51
           11.3. MultiNet Setup   ..............................   54
        12. Caveats    .........................................   56
        13. Future    ..........................................   57
        14. Registration    ....................................   58
        15. Politics    ........................................   59
           15.1. Distribution    ...............................   59
           15.2. Support    ....................................   60
           15.3. License    ....................................   60
           15.4. No Warranty   .................................   62
           15.5. Disclaimer    .................................   62
        16. Acknowledgements    ................................   63














     Road Map


     Page IV            TrapToss' Fantastic Manual             Page IV


                         Time flies like an arrow.
                        Fruit flies like a banana.






















































     Road Map