Page 1 TrapToss' Fantastic Manual Page 1 TrapToss The Real Amiga Packet Tosser Version 1.20 Copyright (c) 1989-1991 René Hexel All rights reserved TrapToss' Fantastic Manual Monday 30-Sep-91 13:33:40 Copyright (c) 1990, 1991 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 toss EchoMail and matrix mail bundles. Please refer to the documentations of TrapDoor and Chameleon for additional information on Area bases, packet transfer, modems and other topics you are missing in here. Please read the entire manual before using TrapToss. TrapToss is a FidoNet-compatible Area tosser for Amiga systems. It has been designed to combine high performance as well as compatibility to existing software. You can use TrapToss for a tiny, simple Point system as well as in a complex, tricky Node setup. It will import and export Areas from and to other systems using FTS-0001 Area Packets and ARCMail bundles (with configurable Packer/Unpacker calls). It handles both, EchoMail Areas and NetMail (private mail, frequently called Matrix mail). In a typical point setup, TrapToss will merely replace older products like ConfMail and oMMM for the Amiga. However in a node environment, things will 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 and soon TrapDoor), thus enabling easy single-file configuration for a variety of applications. Please note that the keywords are neither case sensitive nor 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 executing TrapToss). Then copy the supplied 'TrapToss.Cfg' file to 'mail:'. 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 ' as described below 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. For instructions on 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 FidoNet features two major network entities: 'Nodes' and 'Points' (see a description of FidoNet for more detailed information). While Nodes are connected together and can either call other Nodes or wait for incoming calls, Points are 'DeadEnds', meaning they have only one Node they usually call (their BossNode). Points also have to call (poll) their Bossnode to send/receive mail to/from the Net instead of being called. Since Points are usually only known to their Boss, they cannot call other Nodes on the Net. The main criterion of a Node or Point is its network Address. FidoNet Addresses consist of four numbers, called the Zone, the Net, the Node and the Point. The Zone determines the part of the world your system is located in, like - for example - Europe or Asia. The Net Address specifies the region your system is in (for example, a country or a city) and the Node part of the Address is your system specific identifier. If the Point number is zero, your system is a Node, otherwise it is a Point connected to the BossNode with the same Address (and the Point part being zero), e.g. '2:310/6.4' is a Point of Node '2:310/6.0'. Nodes mostly do not declare a zero Point Address, thus '2:310/6.0' will be addressed as '2:310/6'. The Zone part of the Address is optional as well, meaning "the current zone" if left blank. For instance: my system Address is '2:310/6.4', thus '310/30' means '2:310/30.0' to me. 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). The keyword for this is 'NODE ', where is a fully 4-dimensional FidoNet Address (as a Node you may omit the Point part of the Address, meaning '.0', but you should not omit the Zone part [however if you have to, see the description of the 'ZONE' keyword in the Reference Section]). 4.2. Fake and PointNet Addresses For historical reasons many systems even now 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). To implement Points anyway, 'PointNet' Addresses have been established. A PointNet Address is a virtual Node Address for a Point (a Point fakes to be a Node). This Address, however, is only known to the Point's Boss, enabling him (the Boss) to send mail to his Point's Fake Address (this works with 2-dimensional mail processors since only Net and Node numbers are used). Configuration Fake and PointNet Addresses Page 5 TrapToss' Fantastic Manual Page 5 So, if you are a Point and your Boss has a 2- or 3-dimensional Mailer/Tosser setup (most Nodes do, currently only TrapToss and sometimes FrontDoor systems are exceptions to this) you have to specify your fake PointNet Address as well to enable TrapToss to switch back to 'compatibility mode' for certain features. The keyword for Fake Addresses is 'FAKE ' where is the (2..4 dimensional) PointNet Address of your system. For instance: I am 2:310/6.4 and my PointNet (sometimes called FakeNet) is 3160. So my Fake Address is 2:3160/4.0 and I can tell TrapToss: 'FAKE 3160/4'. If you are running a Node system and you have 'fake' points using a PointNet, you should use the POINTNET keyword to enable an automatic internal 2D->4D conversion in TrapToss. 4.3. Inbound and Outbound Directories Messages you Export to a certain system will be packed together in mail bundles. These packets will be transferred to the other system by a Mailer, like TrapDoor. Before being transmitted the Packets are stored in a certain directory on your system, called the Outbound Directory. For TrapToss the Outbound directory name defaults to 'MAIL:Outbound', but you can use your own Path for the outbound directory, specifying 'OUTBOUND ' in the GCF or on the command line. is the name of the directory where outgoing files will be stored. Similar to this is the Inbound directory. Incoming Packets/Bundles will be stored there by the Mailer for further processing by TrapToss. The default Inbound directory path for TrapToss is 'MAIL:Inbound', but you can change this using 'INBOUND ' (in the GCF or on the command line). 4.4. Private and EchoMail Areas In FidoNet, Mail can be EchoMail or NetMail. NetMail is 'private' Mail which can only be read by the addressee. In the '.MSG' Messagebase, which is used by TrapToss, private mail will be stored in its own directory. To specify the name (path) of this directory, TrapToss uses the 'NETMAIL' keyword. For compatibility reasons this keyword not only requires a directory path, but also an Area name (see below). This Area name should be set to "MAILDIR". For instance, if you want to receive private mail in 'MAIL:Matrix', type NETMAIL MAILDIR Mail:Matrix For EchoMail (public mail) handling, TrapToss supports Areas. An Area is a Directory containing Mail concerning a specific topic (e.g. 'AMIGA' is an Area for Amiga specific Messages). No private Mail may be sent in an EchoMail Area. Unlike NETMAIL, using the AREA keyword you can specify multiple Areas. The Configuration Private and EchoMail Areas Page 6 TrapToss' Fantastic Manual Page 6 syntax is 'AREA ', where is the name of the Area (like 'TRAPDOOR'), is the path as used by the editor (like 'mail:TrapDoor.Area') and is a list of Nodes (their Addresses, actually) who get this Area. For a Point system this must contain your own Address (you have to be the first entry) as well as the Address of your Boss Node. In a Node system you have to list every Node that gets the Area *directly* from you. If you want the Area yourself, you have to list your Address as the first one. For pass-through Areas, i.e. Areas you route but actually do not want to read yourself, simply do not list yourself. In this case, however, you still have to specify a (dummy) directory for this Area ("MAIL:" recommended). You have to list at least one Area, the Bad-Message Area. This Area has to be listed as the first Area in the GCF. The name for this Area has to be 'BAD' and you should list no Nodes for this Area (to prevent exporting Messages from BAD). For example AREA BAD Mail:Bad.Area Please note also, that AREA lines may not be specified on the command line. 4.5. 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 Point's 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. Configuration Adjusting Seen-By lines Page 7 TrapToss' Fantastic Manual Page 7 4.6. 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 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.7. 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.8. 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. Configuration EchoMail ZoneGate Page 8 TrapToss' Fantastic Manual Page 8 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. Noone guarantees that this will work. It is untested so far. 4.9. 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 9 TrapToss' Fantastic Manual Page 9 4.10. 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.11. 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 10 TrapToss' Fantastic Manual Page 10 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 choosen for them, and they are usually sent out during ZMH automatically. Now there might be another node that calls you regularily 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 11 TrapToss' Fantastic Manual Page 11 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 nodenumber will be set to the corresponding part of the "from"-nodenumber. 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. Configuration NetMail Routing Page 12 TrapToss' Fantastic Manual Page 12 4.12. Compressed Mail 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. Here is another trick: The UNPACKER statement will select the decompressor depending on the node number from which a mail bundle was received. If one of these nodes suddenly decides to change the packer type, this must be reflected in your UNPACKER statements. Otherwise TrapToss will call the wrong decompressor. Now there are a few programs (and even ARexx-scripts) that can find out the type of compressor that a particular file was compressed with, and call the appropriate decompressor. If you wish to use such a program, use something like UNPACKER "AutoXtract" * or UNPACKER "rx XArc x" * Configuration Compressed Mail Page 13 TrapToss' Fantastic Manual Page 13 5. Configuration Keywords 5.1. 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). 5.2. (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. 5.3. ADDNODES This keyword takes a list of nodes to be added to Seen-By lines of all exported Messages. In principle this does the same as 'ADD' (see above), but unlike 'ADD' this is a global keyword, i.e. does the adding for all Areas. Example: ADDNODES 310/6 310/3 will add '310/6' and '310/3' to the Seen-By lines of all exported Messages. 5.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. Configuration Keywords (NO)ADDOUTBOUND Page 14 TrapToss' Fantastic Manual Page 14 5.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. 5.6. AKA Allows the 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. 5.7. 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/* 5.8. (NO)AREAPACKET This switch will force TrapToss to create a new packet (.PKT file) 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. Defaults to NOAREAPACKET. 5.9. 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). Configuration Keywords AREA Page 15 TrapToss' Fantastic Manual Page 15 Syntax: AREA tag directory {nodes} In order to receive Messages in that Area yourself, you have to list your own nodenumber as the first node in that Area. If 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 and ALLOW. 5.10. 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 5.11. 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. Defaults to half the size of the largest free block of memory. Note: If a smaller buffer is sufficient to read the whole .PKT into memory, TrapToss will only allocate that much memory. 5.12. 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). Configuration Keywords CHANGE Page 16 TrapToss' Fantastic Manual Page 16 5.13. COLO(U)RS This selects the colour of the TrapToss Screen. Its syntax is one of: COLOURS /// COLORS /// COLOURS COLORS where .. are the RGB4 values (in decimal or hex preceded by ) of TrapToss' screen colours. This command is ignored in 'SCREENMODE NONE'. 5.14. 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 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. 5.15. (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. 5.16. (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. 5.17. DOMAIN Tells TrapToss the domain your system is in. Currently this is only used for ^aMSGID lines created by the Tosser. The syntax of this command is: Configuration Keywords DOMAIN Page 17 TrapToss' Fantastic Manual Page 17 DOMAIN Default is DOMAIN "Fidonet". 5.18. (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 dup-database (two files called Duplicate.Index and Duplicate.MsgId in your MAIL: directory) and to check for duplicates. Currently all duplicate Messages will be moved to the 'BAD' Area. Some more options to this will probably be added. Defaults to NODUPCHECK. 5.19. 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 Message "remembered" will always be smaller (about 80%) of the number you specify with DUPTABLESIZE. Syntax: DUPTABLESIZE 5000 Defaults to 8192. 5.20. (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. 5.21. (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. Example: TrapToss EXPORT Default is NOEXPORT. Configuration Keywords (NO)EXPORT Page 18 TrapToss' Fantastic Manual Page 18 Caveat: Points should use 'SCAN' (see there) which only exports local Messages as an additional security feature to prevent re-exporting of incoming Messages. 5.22. 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). 5.23. (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 thoughts 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. 5.24. (NO)FORCE4DMO Causes TrapToss to use 4-dimensional .MOx files for ARCMail bundles. This will override 'OLDSTYLEMO' (see there). Configuration Keywords (NO)FORCE4DMO Page 19 TrapToss' Fantastic Manual Page 19 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 filenames (like '1234abcd.TU1'). All other files will be "new style", e.g. '2.310.6.4.WE7'. Default is NOFORCE4DMO. 5.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). 5.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). 5.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. 5.28. (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. Configuration Keywords (NO)IGNORESENT Page 20 TrapToss' Fantastic Manual Page 20 Defaults To NOIGNORESENT. 5.29. (NO)IMPORT Causes TrapToss to import inbound bundles/packets. Messages will be stored in 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 MessageBase. Defaults to NOIMPORT. 5.30. INBOUND Sets the Inbound directory path. Syntax: INBOUND Default is 'INBOUND MAIL:Inbound'. 5.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. 5.32. (NO)LINKMSGS On importing this tells TrapToss to link Messages with the same subject (Reply-Linking, Threading). Default is NOLINKMSGS. 5.33. LOGFILE Select the name of the Logfile. Example: LOGFILE Mail:TT.Log Defaults to 'Mail:TrapToss.Log' 5.34. 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). Configuration Keywords LOGLEVEL Page 21 TrapToss' Fantastic Manual Page 21 Example: LOGLEVEL 3 Defaults to, hmmm, let me have a look, 2 (but this definitely is subject to change according to enhancement requests). 5.35. LOGWINDOW This keyword works in conjunction with 'SCREENMODE'. It defines the window position and size of the TrapToss log output window: LOGWINDOW /// or LOGWINDOW 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. 5.36. (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. 5.37. (NO)MATRIXONLY On export (scan) this key tells TrapToss to export Matrix-Mail (NetMail) only, i.e. skipping 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 5.38. NETMAIL Similar to 'AREA' this defines the NetMail directory, but unlike 'AREA' this keyword may only occur once. Syntax: NETMAIL MAILDIR Mail:Matrix For compatibility the name of the Area should be set to 'MAILDIR'. Configuration Keywords NETMAIL Page 22 TrapToss' Fantastic Manual Page 22 5.39. 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. 5.40. (NO)OLDSTYLEFLO Sets the .FLO file compatibility mode, i.e. .FLO files will be named 'hhhhhhhh.xLO', where is an 8-digit hex number and 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. 5.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. 5.42. 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 origline is a string used by the tosser for your origin line. Configuration Keywords ORIGIN Page 23 TrapToss' Fantastic Manual Page 23 5.43. (NO)OUT4D Tells TrapToss to create 4-dimensional (new style) .OUT files. Use this option if you are using a modern Mailer which recognizes these new style files. Default is OUT4D. 5.44. OUTBOUND Like 'INBOUND', but defines the Outbound directory path. Syntax: see 'INBOUND' Default is 'OUTBOUND Mail:Outbound' 5.45. 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. 5.46. (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. 5.47. POINTNET For Nodes only. Sets the fake pointnet for your system. All Addresses of template / in Seen-By lines will be treated like /.. Additionally, packets from PointNet nodes will be interpreted as being from the correct 4D-Address, so that security will work. Example: POINTNET 3160 You need only use this keyword if some of your points are Configuration Keywords POINTNET Page 24 TrapToss' Fantastic Manual Page 24 running older EchoMail software that uses fake pointnet addressing. 5.48. 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 5.49. ROUTE Describes how to route NetMail (.OUT files). Syntax: ROUTE Will re-direct all NetMail dedicated to (a Wildcarded list of Fido-Nodes containing at least one entry) to (destination Address) using (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 * 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 -packet) will be used to replace the wildcards in the destination Address. 5.50. (NO)ROUTING Switches on (off) the routing mode of the Tosser. Default is ROUTING, if export/scan/toss mode is set, otherwise NOROUTING. 5.51. (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. Configuration Keywords (NO)RTD Page 25 TrapToss' Fantastic Manual Page 25 5.52. (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'. Default is NOSCAN. 5.53. (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. 5.54. 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 where 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... 5.55. (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. 5.56. 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 Configuration Keywords SEND Page 26 TrapToss' Fantastic Manual Page 26 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. 5.57. (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. 5.58. (NO)SETSENT Tells TrapToss whether to set the Sent bit in Messages exported or not. Default is SETSENT. 5.59. (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 seting is NOSMALLDUPCHECK. 5.60. STATWINDOW This works in conjunction with 'SCREENMODE'. It defines the window position and size of the TrapToss status output window: STATWINDOW /// or STATWINDOW 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. Configuration Keywords STATWINDOW Page 27 TrapToss' Fantastic Manual Page 27 5.61. 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/* 5.62. STRIPNODES This is the same as 'STRIP', but has global scoping, i.e. all Nodes specified there will be removed from Seen-By lines of Messages of all Areas. 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 5.63. TEARLINE Defines the Tearline handling of TrapToss. You can select 'Replace', which replaces existing TearLines by '--- TrapToss...', 'Leave', which just leaves the Tearline as is or 'None' which simply creates '---' as a Tearline (useful if ^aPID lines are being created). This only has effect on Local EchoMail Messages. Default mode is 'TEARLINE Replace'. 5.64. 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" The default is no timezone at all, meaning local time... 5.65. (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 Configuration Keywords (NO)TOSS Page 28 TrapToss' Fantastic Manual Page 28 this mode for importing Messages in conjunction with 'SCAN' for exporting, although it is also possible, but nevertheless a lot less efficient, to use 'IMPORT' for importing and 'EXPORT' for exporting. Defaults to NOTOSS. 5.66. (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. 5.67. UNPACKER Selects special unpackers for special Nodes. Takes an Unpacker command (a CLI command) and a (wildcarded) list of Nodes to use the unpacker for. 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 "LhArc x" for LHArcMail "Zoo x" for ZOOMail 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" * 5.68. (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. Configuration Keywords (NO)V22HEADER Page 29 TrapToss' Fantastic Manual Page 29 5.69. (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. 5.70. 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). 5.71. 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 {seenby-list} What it does is: For each node that matches , it will remove all the nodes in the SEEN-BY: lines and replace them with the nodes on the {seenby-list} instead. 6. 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 PKTDATE PKTFORWARD Reserved Keywords Page 30 TrapToss' Fantastic Manual Page 30 7. 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 = {0, ..., 9, ?, *, :, /, .} Ż Ż Ż Ż Ż Ż Ż P: -> | -> / Ż -> # | : Ż -> # | . Ż -> | * Ż -> / | * Ż Ż -> | . Ż -> # | : | *: Ż ŻŻ -> * | Ż -> | ? Ż -> | -> 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 Ż Ż Ż Ż Ż Ż Ż Ż Ż Ż S = ------------------------------------------------------------------------------- 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 "?:?/?.?" ŻŻ ŻŻŻŻŻŻ Ż ŻŻŻŻŻŻŻ Wildcards Page 31 TrapToss' Fantastic Manual Page 31 Rules for information not specified: ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ * ( or ) == # (not given) means 'this zone' * == # means .0 (i.e. the Node w/o its points) ------------------------------------------------------------------------------- Limits: Zone: 1 <= <= 65535 Net: 0 <= <= 65535 Node: 0 <= <= 65535 Point: 0 <= <= 65535 Wildcards Page 32 TrapToss' Fantastic Manual Page 32 8. Example Setup 8.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" * ; This for threaded Messages LINKMSGS ; 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) Example Setup Point Setup Page 33 TrapToss' Fantastic Manual Page 33 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 MAILDIR 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 34 TrapToss' Fantastic Manual Page 34 8.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 PointNet 3160 Domain "FidoNet" Origin "The Mad House, Vienna, Austria [HST]" 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 35 TrapToss' Fantastic Manual Page 35 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 ; I have a general unpacker that takes care of everything UnPacker "rx XArc x" * ; 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 ;ŻŻŻ ŻŻŻŻŻŻŻŻ ŻŻŻŻŻŻŻŻŻ ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ NetMail MAILDIR MAIL:matrix 310/6 Area BAD MAIL:BAD Area AMIGA.GER MAIL:AMIGA.GER.AREA 310/6 310/11 310/42 Area AMIPROG.GER MAIL:AMIPROG.GER.AREA 310/6 310/11 310/6.2 310/6.6 Area AUSTROCHAT.AUS MAIL:AUSTROCHAT.AREA 310/6 310/3 310/6.4 310/6.6 310/6.7 310/42 Area DLGBETA MAIL:DialogBeta.Area 310/6 253/140 Area DLGINFO MAIL:DialogInfo.Area 310/6 253/140 281/100 310/42 302/810 ; here is a read-only echo I get from 69:1134/300 Area KINKNET MAIL:KINKNET.AREA 310/6 Example Setup Node Setup Page 36 TrapToss' Fantastic Manual Page 36 Allow 69:1134/300 ; the following three echos are being passed-through ; to one of my points -- I don't care to read MSDos echos. Area LAN MAIL:LAN.AREA 310/11 310/6.7 Area OS2 MAIL:OS2.AREA 310/11 310/6.7 Area PS2 MAIL:PS2.AREA 310/11 310/6.7 9. 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. 10. Future The optimist sees the doughnut. The pessimist sees the hole. I see TrapToss everywhere. Future Page 37 TrapToss' Fantastic Manual Page 37 11. 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 these programs. 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 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 300,- for Austrian addresses (ATS 350,- for Germany and other European countries, ATS 400,- for overseas addresses) to: TrapDoor Development c/o Maximilian Hantsch Matzleinsdorfer Platz 3-4/3/10 A-1050 Wien Austria / Europe or one of the other 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. Should the above not work out satisfyingly, you can either send a cheque (Eurocheques gladly accepted) or money order 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". (The account number given in previous manuals is still valid, but we prefer to receive registrations to the new account.) Beware: International transfers via banks are rather expensive. Registration Page 38 TrapToss' Fantastic Manual Page 38 In any case, be sure to provide us with your name, address, fido-nodenumber 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 six to eight weeks for delivery. 12. Politics 12.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 author. 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". 12.2. Support If you have any suggestions, bug reports etc., feel free to contact the authors of TrapToss at the above address. Additionally, you can reach us at: René Hexel Maximilian Hantsch Fido: 2:310/6.4 Fido: 2:310/6 Uucp: rh%powidl@cbmvie.at Uucp: max%madvie@cbmvie.at 12.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". Politics License Page 39 TrapToss' Fantastic Manual Page 39 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. 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 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 40 TrapToss' Fantastic Manual Page 40 12.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. 12.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 41 TrapToss' Fantastic Manual Page 41 13. 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. CancelReq 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. 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 Snoopy. MS-DOS is a trademark of Microsoft Corporation. Special Thanks to all our Registered Users. TrapDoor, TrapList, TrapPoll, TrapTell and traplist.library by Maximilian Hantsch and Martin Laubach. TrapToss, TrapEdit by René Hexel. UNIX is a registered trademark of AT&T. YooHoo by Wynn Wagner III. ZModem by Chuck Forsberg. Special Mega-Thanx to Arnout Grootveld for proof-reading the manual twice. Acknowledgements Page 42 TrapToss' Fantastic Manual Page 42 14. 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. Private and EchoMail Areas ..................... 5 4.5. Adjusting Seen-By lines ....................... 6 4.6. Wildcards ................................... 6 4.7. Adjusting Seen-By lines Part 2.................. 7 4.8. EchoMail ZoneGate ............................ 7 4.9. Duplicate Message Checking .................... 8 4.10. Outbound Handling ........................... 9 4.11. NetMail Routing ............................. 9 4.12. Compressed Mail ............................. 12 5. Configuration Keywords ............................ 13 5.1. ADD ......................................... 13 5.2. (NO)ADDMSGID ................................ 13 5.3. ADDNODES .................................... 13 5.4. (NO)ADDOUTBOUND ............................. 13 5.5. (NO)ADDPID .................................. 13 5.6. AKA ......................................... 14 5.7. ALLOW ....................................... 14 5.8. (NO)AREAPACKET .............................. 14 5.9. AREA ........................................ 14 5.10. BADPACKETS ................................. 15 5.11. BUFFERSIZE ................................. 15 5.12. CHANGE ..................................... 15 5.13. COLO(U)RS .................................. 16 5.14. CONFIG ..................................... 16 5.15. (NO)CRASHMAIL .............................. 16 5.16. (NO)CRCONLY ................................ 16 5.17. DOMAIN ..................................... 16 5.18. (NO)DUPCHECK ............................... 17 5.19. DUPTABLESIZE ............................... 17 5.20. (NO)ECHOCRASH .............................. 17 5.21. (NO)EXPORT ................................. 17 5.22. FAKE ....................................... 18 5.23. (NO)FILEATTACH ............................. 18 5.24. (NO)FORCE4DMO .............................. 18 5.25. (NO)FSC39 .................................. 19 5.26. (NO)FSC48 .................................. 19 5.27. GATE ....................................... 19 5.28. (NO)IGNORESENT ............................. 19 5.29. (NO)IMPORT ................................. 20 5.30. INBOUND .................................... 20 5.31. (NO)KILLSENT ............................... 20 5.32. (NO)LINKMSGS ............................... 20 5.33. LOGFILE .................................... 20 Road Map Page 43 TrapToss' Fantastic Manual Page 43 5.34. LOGLEVEL ................................... 20 5.35. LOGWINDOW .................................. 21 5.36. (NO)MATRIX ................................. 21 5.37. (NO)MATRIXONLY ............................. 21 5.38. NETMAIL .................................... 21 5.39. NODE ....................................... 21 5.40. (NO)OLDSTYLEFLO ............................ 22 5.41. (NO)OLDSTYLEMO ............................. 22 5.42. ORIGIN ..................................... 22 5.43. (NO)OUT4D .................................. 23 5.44. OUTBOUND ................................... 23 5.45. PACKER ..................................... 23 5.46. (NO)PATH4D ................................. 23 5.47. POINTNET ................................... 23 5.48. POLL ....................................... 24 5.49. ROUTE ...................................... 24 5.50. (NO)ROUTING ................................ 24 5.51. (NO)RTD .................................... 24 5.52. (NO)SCAN ................................... 24 5.53. (NO)SCANOUTBOUND ........................... 25 5.54. SCREENMODE ................................. 25 5.55. (NO)SEEN4D ................................. 25 5.56. SEND ....................................... 25 5.57. (NO)SETHIWATER ............................. 26 5.58. (NO)SETSENT ................................ 26 5.59. (NO)SMALLDUPCHECK .......................... 26 5.60. STATWINDOW ................................. 26 5.61. STRIP ...................................... 26 5.62. STRIPNODES ................................. 27 5.63. TEARLINE ................................... 27 5.64. TIMEZONE ................................... 27 5.65. (NO)TOSS ................................... 27 5.66. (NO)UNATTENDED ............................. 28 5.67. UNPACKER ................................... 28 5.68. (NO)V22HEADER .............................. 28 5.69. (NO)WRITEBACK .............................. 28 5.70. ZONE ....................................... 29 5.71. ZONEGATE ................................... 29 6. Reserved Keywords ................................. 29 7. Wildcards ........................................ 30 8. Example Setup ..................................... 32 8.1. Point Setup .................................. 32 8.2. Node Setup ................................... 34 9. Caveats .......................................... 36 10. Future .......................................... 36 11. Registration .................................... 37 12. Politics ........................................ 38 12.1. Distribution ............................... 38 12.2. Support .................................... 38 12.3. License .................................... 38 12.4. No Warranty ................................. 40 12.5. Disclaimer ................................. 40 13. Acknowledgements ................................ 41 14. Road Map ......................................... 42 Road Map