The FFFFFFFFF OOOOOOO OOOOOOO ZZZZZZZZZZZ LLL EEEEEEEEE FFF OOO OOO OOO OOO ZZZ LLL EEE FFF OOO OOO OOO OOO ZZZ LLL EEE FFF OOO OOO OOO OOO ZZZ LLL EEE FFFFFFF OOO OOO OOO OOO ZZZ LLL EEEEEEE FFF OOO OOO OOO OOO ZZZ LLL EEE FFF OOO OOO OOO OOO ZZZ LLL EEE FFF OOO OOO OOO OOO ZZZ LLL EEE FFF OOOOOOO OOOOOOO ZZZZZZZZZZZ LLLLLLLLL EEEEEEEEE Mail Manipulation System Manual Written and copyright 1991, 1992 by Peer Hasselmeyer All rights reserved. Foozle's Manual CONTENTS -------- 0. General Survey . . . . . . . . . . . . . . . . . . . . . 5 1. Installation . . . . . . . . . . . . . . . . . . . . . . 6 1. Preparations . . . . . . . . . . . . . . . . . . . . . 6 2. Starting FzI . . . . . . . . . . . . . . . . . . . . . 6 3. General 1 . . . . . . . . . . . . . . . . . . . . . . 7 1. Your Name . . . . . . . . . . . . . . . . . . . . . 7 2. Fidonet Address . . . . . . . . . . . . . . . . . . 7 3. Pointnet . . . . . . . . . . . . . . . . . . . . . . 7 4. AKAs . . . . . . . . . . . . . . . . . . . . . . . . 7 5. Inbound . . . . . . . . . . . . . . . . . . . . . . 8 6. Outbound . . . . . . . . . . . . . . . . . . . . . . 8 7. Unpack directory . . . . . . . . . . . . . . . . . . 8 8. Logfile . . . . . . . . . . . . . . . . . . . . . . 8 9. Editor Command . . . . . . . . . . . . . . . . . . . 9 10. Edit File . . . . . . . . . . . . . . . . . . . . . 9 11. Nodelist Directory . . . . . . . . . . . . . . . . 9 12. Userlist File . . . . . . . . . . . . . . . . . . . 9 13. AreaFix Logfile . . . . . . . . . . . . . . . . . . 9 14. Font name . . . . . . . . . . . . . . . . . . . . . 10 15. Colours . . . . . . . . . . . . . . . . . . . . . . 10 4. General 2 . . . . . . . . . . . . . . . . . . . . . . 10 1. Interlace . . . . . . . . . . . . . . . . . . . . . 10 2. Unpack Security . . . . . . . . . . . . . . . . . . 10 3. Check Area Access . . . . . . . . . . . . . . . . . 11 4. Software Used . . . . . . . . . . . . . . . . . . . 11 5. Fast/Secure Saves . . . . . . . . . . . . . . . . . 11 6. Delete Dupes . . . . . . . . . . . . . . . . . . . . 11 7. Route Incoming Netmail . . . . . . . . . . . . . . . 11 8. Auto HiMark . . . . . . . . . . . . . . . . . . . . 12 9. Auto Renumber . . . . . . . . . . . . . . . . . . . 12 10. Reflow Messages . . . . . . . . . . . . . . . . . . 12 11. Show Kludges . . . . . . . . . . . . . . . . . . . 12 12. Hide SEEN-BY . . . . . . . . . . . . . . . . . . . 12 13. Use CM-Style . . . . . . . . . . . . . . . . . . . 13 14. Paragon-Boss . . . . . . . . . . . . . . . . . . . 14 15. Remap MS-DOS Characters . . . . . . . . . . . . . . 13 5. Systems . . . . . . . . . . . . . . . . . . . . . . . 13 1. The Packers/Unpackers . . . . . . . . . . . . . . . 13 2. The Main Systems Screen . . . . . . . . . . . . . . 14 6. Areas . . . . . . . . . . . . . . . . . . . . . . . . 14 1. Default Origins . . . . . . . . . . . . . . . . . . 14 2. Reply Headers . . . . . . . . . . . . . . . . . . . 15 3. Signatures . . . . . . . . . . . . . . . . . . . . . 15 4. Forward Header . . . . . . . . . . . . . . . . . . . 15 5. Dupe Table Size . . . . . . . . . . . . . . . . . . 16 6. The Main Area Screens . . . . . . . . . . . . . . . 16 7. Routing . . . . . . . . . . . . . . . . . . . . . . . 18 8. External . . . . . . . . . . . . . . . . . . . . . . . 18 2 Foozle's Manual 1. After Export Command . . . . . . . . . . . . . . . . 18 2. After Renumber Command . . . . . . . . . . . . . . . 18 3. Special Names . . . . . . . . . . . . . . . . . . . 18 2. The Editor . . . . . . . . . . . . . . . . . . . . . . . 19 1. The Editor Screen . . . . . . . . . . . . . . . . . . 19 1. The Status Line . . . . . . . . . . . . . . . . . . 19 2. The Message Header . . . . . . . . . . . . . . . . . 19 3. The Message Text . . . . . . . . . . . . . . . . . . 20 2. The Menus . . . . . . . . . . . . . . . . . . . . . . 20 1. The "Action" Menu . . . . . . . . . . . . . . . . . 20 2. The "Areas" Menu . . . . . . . . . . . . . . . . . . 22 3. The "Movement" Menu . . . . . . . . . . . . . . . . 23 4. The "Messages" Menu . . . . . . . . . . . . . . . . 24 3. The Keys . . . . . . . . . . . . . . . . . . . . . . . 26 3. The Commandline Functions . . . . . . . . . . . . . . . 28 1. Import . . . . . . . . . . . . . . . . . . . . . . . . 28 2. Export . . . . . . . . . . . . . . . . . . . . . . . . 28 3. Himark . . . . . . . . . . . . . . . . . . . . . . . . 29 4. Renum . . . . . . . . . . . . . . . . . . . . . . . . 29 5. Rescan . . . . . . . . . . . . . . . . . . . . . . . . 29 6. FRescan . . . . . . . . . . . . . . . . . . . . . . . 30 7. Maint . . . . . . . . . . . . . . . . . . . . . . . . 30 8. Editor . . . . . . . . . . . . . . . . . . . . . . . . 30 9. Background/BG . . . . . . . . . . . . . . . . . . . . 30 10. Config . . . . . . . . . . . . . . . . . . . . . . . 30 11. Quit . . . . . . . . . . . . . . . . . . . . . . . . 31 12. Prio . . . . . . . . . . . . . . . . . . . . . . . . 31 4. External Programmes . . . . . . . . . . . . . . . . . . 32 1. External Functions . . . . . . . . . . . . . . . . . . 32 2. The UserList . . . . . . . . . . . . . . . . . . . . . 33 3. The Remap-File . . . . . . . . . . . . . . . . . . . . 33 5. Routing . . . . . . . . . . . . . . . . . . . . . . . . 34 1. Remapping . . . . . . . . . . . . . . . . . . . . . . 35 6. Installing Points . . . . . . . . . . . . . . . . . . . 36 7. AreaFix . . . . . . . . . . . . . . . . . . . . . . . . 37 1. About AreaFix . . . . . . . . . . . . . . . . . . . . 37 2. Installing AreaFix . . . . . . . . . . . . . . . . . . 37 3. Using AreaFix . . . . . . . . . . . . . . . . . . . . 37 4. Hints . . . . . . . . . . . . . . . . . . . . . . . . 37 8. Multiple Net Support . . . . . . . . . . . . . . . . . . 38 9. Inbound/Outbound . . . . . . . . . . . . . . . . . . . . 39 1. The Inbound . . . . . . . . . . . . . . . . . . . . . 39 2. The Outbound . . . . . . . . . . . . . . . . . . . . . 39 3 Foozle's Manual 10. The Logfile . . . . . . . . . . . . . . . . . . . . . . 41 11. Limitations . . . . . . . . . . . . . . . . . . . . . . 42 12. Registration . . . . . . . . . . . . . . . . . . . . . 43 1. Why Register . . . . . . . . . . . . . . . . . . . . . 43 2. How To Register . . . . . . . . . . . . . . . . . . . 43 13. License . . . . . . . . . . . . . . . . . . . . . . . . 44 1. Notice . . . . . . . . . . . . . . . . . . . . . . . . 44 2. You May . . . . . . . . . . . . . . . . . . . . . . . 44 3. You May Not . . . . . . . . . . . . . . . . . . . . . 44 4. No Warranty . . . . . . . . . . . . . . . . . . . . . 45 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . 46 4 Foozle's Manual 0. General Survey ----------------- The Foozle Mail Manipulation System ("Foozle") is a fast FidoNet-compatible message-editor/tosser/scanner/packer. In simpler terms it is a program to import messages from other FidoNet-systems into your local database, to export messages to other FidoNet-locations, to read and write messages and to do some other nice things. If you previously worked with some fidonet-compatible software on your Amiga, Foozle will merely replace CE / CM / FastPoint / GCC(host) / Juliet / oMMM / PointManager / RMB / TrapToss or whatever you have used in one single program. Only a mailer is lacking, so you have to use one of the existant mailers like BinkleyTerm, TrapDoor or WelMat. Actually, this program is designed to be run with TrapDoor version 1.74 or higher, but it also works with other mailers and other versions of TrapDoor. All parts of the program are written in assembly language for the reason of speed and comfort. Foozle is designed to work with a HardDisk and at least 1MB of RAM. If you want to keep a message base with typically more than 20-30 areas - depending on the other utilities you run in the background - it is recommended to have even more free store. Foozle needs about 200KB for the program, its buffers and the screen. Each area uses at least 2KB (if you do not have a dupe- table and less than 100 messages). But remember: if you want to im- or export, you also need memory for the archive-utility (about 150KB) and for fast exports you should store all temporary files in the ram-disk which can also absorbe quite a bit of memory. Foozle can be started from either the CLI or the WorkBench. It accepts some commands which can be entered at the command-line, stored in the default tool of an icon or issued via the built-in ARexx port. This manual is not intended to be a complete description of FidoNet, thus containig no explanation of echomail etc. For further information about net- and echomail consult FTS-0003 or the documentation of ConfMail as well as the documentation of oMMM. For an explanation of the organisation of FidoNet try to get ahold of the Policy which should be available at every FidoNet node. Before installing Foozle you should read the whole manual carefully. Everything you need to set up a working FidoNet compatible mail processing system should be described somewhere in it. If you miss some information, feel free to contact the author via NetMail at 2:247/4@FidoNet or use one of the echomail conferences FOOZLE or AMY_POINT. 5 Foozle's Manual 1. Installation --------------- The installation of Foozle is mostly done by a program called "FzI" which should be included in the archive/disc you got this manual from. "FzI" is also needed for all changes you want to do to your setup. If you have finished setting up Foozle you must create all necessary directories. Foozle's editor will create a mail directory for you when you try to access an area with a nonexistant directory so that you should quickly pass through all areas to create the necessary directories. But don't forget to make sure that the parent directory (the directory to which mail directories are added to) as well as the inbound, outbound and nodelist directories already exist. 1.1. Preparations ----------------- To run Foozle properly you need to set up at least a logical device named "t:" which will keep all temporary packets during the export. Usually you would assign this device to your RAM:-disk, as only temporary files are stored in it. But if you export large amounts of mail it depends on your memory-constitution if you perhaps better assign t: to a directory on your HardDisk. In the normal setup you would also assign a directory to "MAIL:" in which you store all of your messages. Foozle does not rely on this assignment, so you may have all your messages in "FOOZLE:" or anywhere across your harddisk. Foozle needs some third party shareware. There is at least the "arp.library". This library is a part of the AmigaDOS Resource Project which is widely available. If you don't have it, contact your local BBSes, the next shareware dealer or the author of Foozle. 1.2. Starting FzI ----------------- The Foozle installation program "FzI" must be placed in the same directory you keep the main Foozle program in. Start FzI by simply typing "FzI". If this is the first time you install Foozle, you must go through all steps described below. If you only do some changes to your setup, the main FzI-screen will be displayed asking you to select one of the six topics. On the bottom of FzI's window you will always see three gadgets. By pressing the "OKAY" gadget your information is stored and FzI advances to the next question. "SAVE" lets you store your setup to disk anytime you want to. "CANCEL" aborts the queue of questions on the selected topic and places you back into the main menu. NEVER press "CANCEL" while you are installing Foozle for the 6 Foozle's Manual first time or recover from some file loss / damage. You may abort FzI at any time by simply clicking on the close gadget in the upper left corner of its window. Don't forget to save your setup before quitting FzI ! After changing some things of your setup, be sure that you hit the "OKAY" gadget before saving ! 1.3. General 1 -------------- There shouldn't be any questions left because of the texts explaining what to do. But, however, here is the description once again. 1.3.1. Your Name ---------------- Not very difficult - just enter your name. It will be displayed as a default for the from-field for every message you are entering. 1.3.2. FidoNet Address ---------------------- A bit more difficult as you don't need this information in the "normal" life. But you don't have to think about this question: if you operate a point - ask your boss, if you operate a node - ask your netcoordinator/hub. You MUST specify the fully qualified 4 dimensional address here ! This includes zone, net, node and point information (well, if you are a node, you can leave out the point - the default is 0). Your address, therefore, should look like 2:247/4 or 1:23/456 for a node and 2:247/4.9040 or 3:210/987.6 for a point. 1.3.3. Pointnet --------------- This information is needed as you can't do everything in FidoNet four dimensionally due to the historical development of FidoNet. If you operate a point, you must again ask your boss for this. In node operation you must create the pointnet by yourself. Just use a number between 1 and 32767 that has something to do with your node address, e.g. 22474 if you are 2:247/4 or 16000 if you are 5:352/16. Please use a large, very specific number so that it can't get in conflict with existing nets. A point must sometimes be accessed via its "fake" address. This address is a node address built of the pointnet and the point number (e.g. boss 2:247/4, pointnet 22474, point 6: normal address: 2:247/4.6, fake address: 22474/6). 7 Foozle's Manual 1.3.4. AKAs ----------- You can enter up to eight alternative system addresses (AKA=also known as). Those are needed when you work in different networks with different zone numbers or if you operate a multiple boss point. Just leave these lines blank if you don't have any AKAs. The pointnet must always be given after your full four dimensional address divided off by a comma. Examples: 2:247/4.99, 24704 222:104/1, 10401 1:247/102.4, 24102 1.3.5. Inbound -------------- The directory where everything you receive is stored is your inbound directory. Please set this according to your mailer's settings, e.g. "mail:inbound", "dh0:foozle/in". 1.3.6. Outbound --------------- The directory where all your outgoing mail will be placed by Foozle is the outbound directory. You must also set this according to what your mailer uses. Examples: "mail:outbound" "fido:mail/outgoing" 1.3.7. Unpack Directory ----------------------- Select now where Foozle is going to unpack bundles to. If you have enough memory you can choose the RAM:-disk. If you want the bundles to be unpacked to the inbound directory, leave this line blank. Examples: "ram:packets" "t:" "mail:unpackdir/" 1.3.8. Logfile -------------- Every time Foozle performs some action, it will write this into the logfile. You can specify now, where you want this information to be put. If you operate a node it is a good idea to store this information on (hard)disk as you may want to see what happened while you left the system unattended. If you operate a point and always sit next to your computer while Foozle works, you can use a logfile on the RAM:-disk, a CON:-window or even the NIL:-device. 8 Foozle's Manual Examples: "logs:Foozle.log" "mail:fz.log" 1.3.9. Editor Command --------------------- Enter your preferred editor here. It will be called by Foozle every time you write, edit or reply to a message. The place where the filename of the edited file will be put can be specified by entering a "%". If you leave this out, the filename will be added to the end of the command line. Examples: "Ed" "CEd % -keepio". 1.3.10. Edit File ----------------- You can select the file that is passed to the editor (see above) with this command. It is recommended to use the RAM-disk for this file, e.g. "ram:Foozle.tmp", "t:x". 1.3.11. Nodelist Directory -------------------------- If you want to have the luxury of using the nodelist, you must now specify the directory where you keep all nodelist related files in. The nodelist(s) must have already been compiled by TrapList (or an equivalent) so that the index file can be accessed. Foozle uses the "traplist.library" which is included in the archive of TrapDoor 1.80. Examples: "nodelist:" "sys:fido/nodelist" 1.3.12. UserList File --------------------- If you want to use a so called "UserList" file which contains all the names and addresses of persons you often write messages to, enter the name and the path of that file now. For the format of this file see chapter 4.2. Examples: "mail:UserList" "dh0:text/FidoUsers" 9 Foozle's Manual 1.3.13. AreaFix Logfile ----------------------- Foozle has a built in AreaFix. AreaFix is a fake user at your system who maintains the topology of echomail flow. Another system can now add and remove itself from receiving echomail areas without your intervention. To enable AreaFix at your system simply specify the logfile to be used for storing all changes done to echomail topology. For more information read chapter 7 - AreaFix. Examples: "logs:AreaFix.log" "t:af.log" 1.3.14. Font Name ----------------- Foozle may use any font, that has the fixed size of 8x8 (if you use another size, the screen will look weired). You can specify the name of that font now (including ".font"). If you don't enter any name, the default topaz.font is used. An even better solution of using other fonts is to set the desired font with "FastFonts" as the default system font. This will dramatically improve the speed of the display. 1.3.15. Colours --------------- Foozle can use the colours that you like most. Select the colour you want to change (click on one of the four square boxes) and adjust it with the (R)ed, (G)reen and (B)lue sliders. To check whether the colours are okay, select the "TEST" gadget on the right. To return to the default colour set, just click on the "DEFAULT" gadget. 1.4. General 2 -------------- 1.4.1. Interlace ----------------- Foozle can operate on an interlaced screen if you wish. This is only recommended if you have a flicker fixer. 1.4.2. Unpack Security ---------------------- This switch may be used to run a secure system. To avoid your node being the entry-point of echomail from unauthorised systems, 10 Foozle's Manual you can instruct Foozle to ignore packed mail bundles from systems that were not installed in the "Systems"-setup. Incoming uncompressed packets are not checked by Foozle. To run a fully secure system, you should run the program "CheckPackets" before those packets are processed by Foozle. 1.4.3. Check Area Access ------------------------ If you enable this feature, Foozle verifies that the originating system of a packet containing echomail messages has access (is listed in the export_to-list) to an area it wants to send messages to. If the system has no access to that area, the offending message is moved to the BAD_MSGS area. 1.4.4. Software Used -------------------- The original FidoNet naming system does not support zone and point information. But TrapDoor 1.50 introduced a new zone and point aware naming scheme for outgoing packets and "flow files". TrapDoor 1.74 and higher also features 4 dimensional names for outgoing packed mail bundles. If you use one of the mentioned versions of TrapDoor, it's best to tell this now. 1.4.5. Fast/Secure saves ------------------------ Safe saves store all changes made to your message base immediately on disk. Fast saves only store this information if it is necessary. If you do an import and an export afterwards, the changes will only be saved after the export if you use fast saves; otherwise the changes will also be saved after the import. 1.4.6. Delete Dupes ------------------- Messages that come in twice can be completely ignored by Foozle or put into the BAD_MSGS area. The dupe detection is almost 100% reliable - but it will only be 100% safe if all incoming messages contain a MSGID-kludge. 1.4.7. Route Incoming Netmails ------------------------------ Foozle can route incoming netmails directly on an import. As a node, you should always route these netmails as it doesn't make 11 Foozle's Manual sense to first import the netmails and then export them again; they will only enlarge your netmail area. In a point environment it is useful to let Foozle import all netmails, as some brain-damaged software (e.g. MS-DOS Tick) may create messages with a wrong destination (which would be routed by Foozle). 1.4.8. Auto HiMark ------------------- This option is only recommended for points. It adjusts the HiWater mark after each import to the highest available message, thus no mails that weren't written locally are touched by the next export. 1.4.9. Auto Renumber -------------------- If you enable this, the messages of those areas, the maintenance function deleted messages in, will be renumbered. 1.4.10. Reflow Messages ----------------------- Reflowing is a nice feature if you have a text editor terminating all lines with a line feed (no word wrap). Foozle now removes these line feeds so that every mail reader can adjust the length of each line to its own needs. 1.4.11. Show Kludges -------------------- Some fidonet messages contain control-lines which are only useful for message tossers/scanners. These are called IFNA-kludges and "hidden" behind a control-A character (01hex). If you decide to see them, they will be displayed in black (with the default colour set) otherwise they won't appear. 1.4.12. Hide SEEN-BY -------------------- The SEEN-BY: lines can also be "hidden" as a kludge which is useful in conjunction with "Hide Kludges" as only the plain message text will be displayed. This option affects messages only locally - you won't see any effect unless you exported the message to other systems. 12 Foozle's Manual 1.4.13. Use CM-Style -------------------- You can now select whether Foozle should create messages in its own style or stick to the old ConfMail-style (true FTS-1 which is compatible with other FidoNet software). If you're using old style messages (e.g. in conjunction with a BBS) you don't have any reply linking. 1.4.14. Paragon-Boss -------------------- Paragon's mail processor generates netmail packets (at least for its points) that do not comply with the FidoNet specifications. These packets would normally be considered damaged by Foozle. If you set this switch to "Paragon", a check within Foozle is disabled and Paragon's packets (as well as some really damaged ones) are processed normally. 1.4.15. Remap MS-DOS Characters ------------------------------- Foozle's editor can remap a few of the MS-DOS characters to their equivalents on the Amiga. Don't enable this feature if you're using an IBM character set. 1.5. Systems ------------ 1.5.1. The Packers/Unpackers ---------------------------- To reduce the time needed for transferring echomail to other systems, the messages are packed into one file. Then this file usually gets compressed. With Foozle you can have four different sets of commands to be used for compressing/decompressing the mail. The first command of each pair will be used for compressing, the second for decompressing. Don't forget to enter the full absolute path for each command as it is unknown what the current directory will be during import/export. And don't forget to specify all parameters for the commands. Examples: "dh1:zoo a" "c:lharc -m -n x" "ram:bin/pkxarc" 13 Foozle's Manual 1.5.2. The Main Systems Screen ------------------------------ On the left side you see a list of nodes that have access to some/all of your message bases. On the right hand side you see a list of your areas. All areas that get exported to the currently selected system (the one that is framed) are highlighted. To scroll through one of these lists use the arrows next to that list. The single arrows scroll one line up/down, the double arrows are used for fast scrolling. Inbetween those two lists you can choose the packer/unpacker that is used for that system and you can edit the access level as well as the access flags of the system (refer to chapter 1.6. for a short description of the flags field). Systems that have a lower access level than that of a specific area or not the right flags set can't use the AreaFix to get access to that area. It can only be switched on manually. If you want to hold the mail for a system (so that the system has to call you to receive its mail) you must select the "Hold"-switch. If you want the mail for a specific system leave your system immediately, you should select "Crash" for that system. If neither the Hold nor the Crash switch is enabled, the mail is created with the normal status. You can also switch between 2 and 4 dimensional packets. This option has no effect on links between nodes, but from a node to a point and the other way round. You should always have a try with 4 dimensional packets. If it causes too many problems on the remote system, switch back to 2D. (Hint: 4D has successfully been tested with Foozle and D'Bridge and should work with ScanToss, TosScan and TrapToss). To add nodes to your list either press the "Insert"-button or scroll to the end of the list and enter the system's FidoNet address when the line for the selected system is blank. To remove a system, scroll through the list until that system is selected and click on the "Delete"-button. To change the address of a system, just select that system and change the address as desired. To add/remove an area for the selected system just click on the desired area. Please note that you can't switch on the netmail- and the BAD_MSGS-areas. 1.6. Areas ---------- 1.6.1. Default Origins ---------------------- The origin is a string near the end of each echomail message preceded by the string " * Origin: " and followed by the FidoNet address of the originating system. It should contain information about where your system is located. You can have different origins for each area, but the first of these two will be used as default 14 Foozle's Manual for every area until you change it. Your origin string should not exceed the size of about 50 characters as this may cause the whole line to be longer than 80 characters which can confuse some mail processors. The idea behind having default origins is quite simple: let's say you use the same origin in five areas. Instead of changing the origin five times you must only modify the default origin. 1.6.2. Reply Headers -------------------- When replying to a message the actual text is "quoted" and preceded by an optional reply header. You can have four different reply headers. The text of the headers may contain some templates which will be replaced by an appropriate string. The following templates are known (case sensitive !): %n : name of writer %N : first name %o : origin address %a : addressee %d : date %t : time All vertical bars ("|") are translated into line feeds. Examples: "In a message of <%d %t> %n (%o) wrote to %a:||" "Hi %N !||In one of your articles I saw the following:|" 1.6.3. Signatures ----------------- All messages you write may be appended by a signature. You can again have four different which you can enter now. If a signature is larger than 120 characters you must put it into a file and write the name of the file preceded by a "<" into the corresponding gadget. Vertical bars are again translated into line feeds (this does not apply to signature files). Examples: |Bye ... Peer|| The following is a short description of all actions available to you in the editor. This includes the menu-description as well as the functions of the keys. 2.1. The Editor Screen ---------------------- The screen of the editor is divided into three parts: the status line, the message header and the message text. 2.1.1. The Status Line ---------------------- On the left side of the status line you see the name of the current area. In the middle you can find the number of the message that is currently displayed. If there are any replies to this message or if this message is a reply to a previous message, arrows and the number of that message will precede and/or follow the message number. Just behind you can find the flags of the message (if any are set). The abbreviations are: PV - Private KS - Kill/Sent FL - File attached MK - Marked CR - Crash On the right side of the screen you can find the number of messages in this area as well as the numbers of the first and the last messages. 2.1.2. The Message Header ------------------------- This section of the screen consists of three lines. The first line tells you the name of the message writer, his FidoNet address and the date he wrote this message. The second line shows the name of the addressee and the date you received that message. If you wrote a message locally, the second date represents the time you exported this message for the first time. In the NetMail area, the FidoNet address of the addressee will also be shown. The third line just gives you the subject of the message. 19 Foozle's Manual 2.1.3. The Message Text ----------------------- In this area the text of the message is displayed. With the default colours the text is white and control information (the so called "kludge lines") is displayed in black (unless you decided to hide all kludges). The slider on the right side shows how large the message is and where in the message you are located. It is also used for quick jumps in the text. With the two arrows you can scroll through the text line by line. 2.2. The Menus -------------- Foozle has four or five menus. The first four are always the same and include all functions of Foozle. The fifth menu can be defined by the user by creating a "Foozle.ext" file. This is described in chapter 4.1. 2.2.1. The "Actions" Menu ------------------------ IMPORT: This option starts the import-facility of Foozle. An info-window will be displayed in which you can see how the process of importing mail into your database is going on. In fact, all the information going into your logfile will be displayed in this window plus some more. EXPORT: This is the opposite of import. Now mail will be exported from your message-base to other nodes/points. You can supervise the execution in the same info-window as described above under "IMPORT". MAINTENANCE: Maintenance deletes messages in the areas according to your specifications made with FzI. In the status window you will see how many messages were deleted and in which area. TRANSFER FILES: This option enables you to specify some files which will be transferred to another FidoNet-node/point. First you must enter the full 4d address of the destination. If you leave out the zone, net or node information, your zone, net or node will be used as default. If you do not specify a point-number, 0 will be used. Then you can enter up to 32 files to be transferred. You should always specify the full path of the file (e.g. "dh1:fido/mail/bin/Foozle") to be sure that your mailer sends the right files. If you enter a blank line or click on the "OK"-gadget, your file-selection is stored onto disk. You can 20 Foozle's Manual scroll through the list by using the arrows on the right side. If "Hold" is switched on, the files will only be sent if the destination node/point calls your system. Otherwise the files will be sent on your phone-bill. REQUEST FILES: With file-requests you can obtain files from other FidoNet-systems. Just procede as stated above in "Transfer Files" and enter all files you want to receive from the remote system. For receiving a list of available files from a system, you only have to enter the keyword "FILES" - this works on most systems. Please never request files during the zone mail hour (e.g. zone 2: 2:30 - 3:30 UTC) and always remember your phone-bill ! CREATE AREA LIST: Creates a list of all available areas. Please enter the desired filename of the list. CREATE AREA REPORT: Creates a list of areas that are active for a system. You must enter the system's address as well as the filename of the report. SET ADDRESS: If you want to write some messages with another address than the default one, you may now choose it. Please note, that this is only a temporary change: the next time you switch to this area, the default address will be active again. REFLOW TEXT: This switch has the same meaning as the corresponding switch within FzI, but it is only effective temporary (until you restart Foozle). REMAP CHARS: Again, a temporary correspondance to the switch within FzI. HIDE KLUDGE: And yet again a temporary switch. LEAVE: Leaves the editor. In opposition to exit, this function only assures, that the editor is terminated. If there were any additional commands queued or has the editor been invoked from the background, Foozle will execute these commands/go back into the background. BACKGROUND: The editor is left, but Foozle will not be terminated. It still resides in the background waiting for some command being issued via the ARexx-port. This is useful, if you don't like/need an additional screen, but need Foozle though. If you have enough memory it is a good idea to leave Foozle in the background, as all following commands are executed faster than by restarting Foozle. 21 Foozle's Manual EXIT: Foozle will be terminated completely and all allocated resources will be freed. Any queued commands are ignored. (Instead of selecting this function from the menu, you may as well press Shift-Right_Amiga-Q). TOGGLE BAR: Shows/hides the screen's title-bar. ABOUT: Just a short information about the program. 2.2.2. The "Areas" menu ----------------------- CHANGE AREA: Allows you jump directly into a specific mail-area. The colour of each area tells you, if there are new messages in it. This only works if you didn't quit Foozle after the last import. Using the default colours, the areas will normally be displayed black. If there are new messages available, the colour will change to white. And if Foozle detected any mails for you, the area is displayed blue. NEXT AREA: Activates the next mail-area. If you reached the last one, the first area (the NetMail area) will be chosen. PREVIOUS AREA: Just like NEXT AREA, but the other way round. AREA WITH NEW MAIL: Activates the next area that contains unread messages. Note that this function, as well as "Change Area" and "Area/Mail For You", only applies to messages received during the last import and does not work, when you left Foozle after the last import. AREA/MAIL FOR YOU: Activates the next area that contains unread messages of which at least one is addressed to you. RENUMBER AREA: When you work extensively with a message-area, it will soon be splattered. To "reorganize" the numbers of the messages, select this option. The numbers of the messages will be from 1 to the number of messages in this area. RENUMBER ALL: Does the same as "Renumber Area" to all of your message-areas. 22 Foozle's Manual RESCAN AREA: Sometimes even YOUR computer can crash. And sometimes this even happens while Foozle is doing some work on your message-base. If this ever happens, you should do a rescan. You should also do a rescan if a program other than Foozle performed some work on a message-area, e.g. deleted or created some messages. Rescan brings the .map-file up to date. To work efficiently, rescan first searches the mail-directory for all *.MSG-files. If these are already stored in the .map-file nothing else will happen. If a "new" *.MSG-file is encountered, this message will be opened and all appropriate data will be included in the .map-file. Missing *.MSG-files will be removed from the .map-file. RESCAN ALL AREAS: Well, have a guess ... or just try it ! FULL RESCAN: See the description in chapter 3.6 - FRescan. FULL RESCAN ALL: The above for all areas. HIMARK: The HiWater mark is used by the export function to find the first message that was not yet exported. If you himark an area, the HiWater mark is set to the highest message in this area so that none of the current messages will be exported from this area during the next export. HIMARK ALL: Sets the HiWater marks of all areas. SET MARK: Move the HiWater mark to another message. During the next export all messages that have a higher number will be exported unless the destination is already listed in the SEEN-BY's. 2.2.3. The "Movement" Menu -------------------------- NEXT MESSAGE: Just what it says: jumps to the next available message. PREVIOUS MESSAGE: Jumps into the other direction. LAST MESSAGE: Jumps to the last available message. FIRST MESSAGE: Jumps to the first available message. 23 Foozle's Manual NEXT MARKED MESSAGE: Jumps to the next message in this area, which has been marked before. This is very useful if you want to reply to or re-read specific messages. PREVIOUS MARKED MSG: See above, just jumps into the other direction. NEXT REPLY: Jumps to the message that is a reply to the current one - if one exists. PREVIOUS REPLY: Jumps to the original message - if available. JUMP TO MESSAGE: Do you really need an explanation for this ? 2.2.4. The "Messages" Menu -------------------------- WRITE MESSAGE: This is a very, very useful function: you can write a message into the current message-area! You're favourite editor will be invoked and now it's up to you to pack your thoughts into nice words (always remember: FidoNet is for fun - so: no flames !). After leaving the editor, a requester will pop up asking for some details about the message. The first field is for the name of the author of this message. Your name is displayed by default and should never be changed as pseudonyms are not allowed in FidoNet. By pressing return you get into the "To:"-field. Enter the name of the addressee of this message or something like "All" if the message is not destined to a specific person. But remember: all messages in echomail-areas (= all areas except the first one - the NetMail-area) can be read by many people around the world, so don't write any personal stuff in echomails - use NetMail ! If you have enabled the UserList support, you may enter the name of a person or his nickname. If the person was found, his/her full name will appear in the To:-field and the FidoNet address will be put into the Dest:-field if you are in the netmail area. You can search for parts of the name by adding a question mark to the search string (e.g. "mey?"). When you write a netmail you can also enter the FidoNet address of the addressee instead of his name. If you enabled the nodelist support, Foozle will now try to find this system in the nodelist. If the system is present, the name of its SysOp will be displayed in the "To" field and the system's address as well as its name are shown in the "Dest" gadget. After another touch of the return-key, you can specify the subject of your message. At last there is either the Origin- or the Destination-field left. In all echomail-areas you will be asked for the origin-string. Your origin for the area will already be filled in, but you can change it if you want. In the 24 Foozle's Manual netmail-area you will be prompted for the destination. Specify any valid address in here (e.g. 2:247/4.9041, 1:1/20, ...). If you leave out the zone (and net and node), your zone (and net and node) will be used as default. Now you can change the attributes of your message. The following gadgets are available (in echomail you can only access the "Private" and the "Kill/Sent"-buttons): Normal: just a normal message - the flags of the message are set in accordance with the node-infos/routing. Crash : a very important mail - this flag means, that the message should be sent directly to the addressee. Hold : this message will be held by your system until the receiver of it calls you. Private: the message is marked private - not that useful as netmail is always private and echomail is always public. Kill/Sent: the message will be killed during the next export - normally not very useful (or do you want to loose everything you wrote?) except for writing to AreaFix as somebody could read your password in this message. File Attach: a file will be sent with this message. If you switch this flag on, a requester will pop up in which you can select the file to be transferred. Please note that an attached file is NEVER routed - you can only put it on hold. If you neither flag the message as "Crash" nor as "Hold", the message will be routed - but not the file. File Request: this netmail is a matrix file request - all files specified in the subject line should be sent by the remote system (this flag is not supported by all mailers). Receipt Request: the addressee of this messsage should return a message to you saying that he received yours. Audit Request: all systems your message passes through, should send you a message back. Please note, that the last two flags are only supported by a very small number of systems. Attention: you can select all flags via the keyboard by pressing the first letter of the flag. However, there are the following exceptions: A - File Attach U - Audit Request REPLY: With this function you can answer to the currently visible message. The message will be quoted and your editor is then invoked. Please delete unnecessary lines from the quoted text so that transmission costs are kept at a minimum. 25 Foozle's Manual MATRIX REPLY: The same as "Reply To Message" - but your answer is stored in the netmail-area and thus private. FORWARD MESSAGE: is used for transferring messages from one area to another and to resend messages in the same area. You can first choose the area to which you want the message to be transferred and then edit the message-header as described above. EDIT MESSAGE: Maybe you discover that you wrote something wrong in a message. Then this option is just the right thing for you. It allows you to edit everything of any message except its destination and origin. READDRESS MESSAGE: This is used for changing the destination address of a netmail. It may be useful if you made a mistake in the address or if a message arrives that just isn't destined to your system. MARK MESSAGE: Toogle the mark of the current message. DELETE MARKED MSGS: Kills all messages that have the mark set. PRINT MESSAGE: Prints the message on the PRT:-device. SAVE MESSAGE: Stores a message on disk - you only have to specify a filename for it. VIEW MAIL LIST: A very useful function to get an overview of your message base. Enter the first and the last number of the messages you want to see and a short header of each message containing its number, the writer, the addressee, the subject and the date the message was written will be displayed. Marked messages are being highlighted. You can scroll through the list by using the slider and the arrows on the right side of the screen or the cursor keys. If you want to see only special messages you can enter patterns for the writer, the addressee and the subject (e.g. "Peer*", "*fo?zle*", "~*flame*", ...) - the comparison is not case sensitive. By clicking on a message, its mark is toggled. If you want to mark all displayed messages, press the "MARK"-gadget. If all marks of the displayed messages must be cleared, select "CLEAR". To leave the mail list press either "OK" or "CANCEL". "OK" keeps all marks, while "CANCEL" deletes them. 26 Foozle's Manual 2.3. The Keys ------------- In the editor requesters will pop up very often. Generally, instead of clicking on the gadgets you can also press the first letter of that particular gadget. If you want to "CANCEL", you can just press the "C"-key. Special functions are designated to the [Return]- and the [Esc]-keys. [Esc] always means "Cancel", while [Return] stands for "OK". The other key functions are: Cursor_left : previous message Cursor_right : next message Shift-Cursor_left : first message Shift-Cursor_right : last message Alt-Cursor_left : previous reply Alt-Cursor_right : next reply Ctrl-Cursor_left : previous marked message Ctrl-Cursor_right : next marked message Cursor_up : scroll one page up Cursor_down : scroll one page down Shift-Cursor_up : first page Shift-Cursor_down : last page Alt-Cursor_up : scroll one line up Alt-Cursor_down : scroll one line down Del : toggle mark If you select "Next Area" from the menu or by pressing Right_Amiga-N, it's function can be modified by holding down the following keys: Right Shift: jump to the next area that contains new messages Left Shift : jump to the next area that contains new messages for you 27 Foozle's Manual 3. The Commandline Functions ---------------------------- All functions that do not deal with message reading or writing can be invoked from the command line or issued via the ARexx port. This is needed when you are running a node where everything has to work automatically. If you don't own ARexx you can also send commands via the ARexx port by using the program "TellFoozle". Just enter "TellFoozle " and these commands will be transferred to Foozle (Foozle must run in background or editor mode to receive orders via ARexx). The name of Foozle's ARexx port is (you surely guessed it) "Foozle". Some commands need to know on which areas the action shall be performed, so you have to specify those areas. Foozle recognizes your name as well as the net name and the comparison is not case sensitive. If you want to specify more than one area, the areas must be seperated by commas. If at least one area name contains a space you must embed all areas in quotation marks. If you want the action to be performed on all areas, just type "ALL". 3.1. Import ----------- This has the same effect as the import function of the editor. But here is a more technical description: At first, import scans your inbound directory. If any packets were found (see 9.1. Inbound) they will be split up into individual messages and put in the area they belong to (normally netmail). If you receive a message that belongs to an area you didn't install, the message will be put into the BAD_MSGS area with the first line being "AREA:" and the name of the area the message should go to. If a dupe is found it will be deleted or (depending on your settings) be put into the BAD_MSGS area with the first line being "DUPE:" and the area name. The next thing import does, is finding the bundles that came in. They get uncompressed one after the other by using the unpacker you previously chose for the originating system (if the system is unknown, the first unpacker is used unless you chose to not process bundles from unknown systems). After uncompressing a bundle, all packets get tossed as described above. If an error occurrs (maybe the packet is damaged) and the toss of that packet has to be aborted, Foozle renames the packet from "*.PKT" to "*.BAD" (this will also be logged in the logfile). 3.2. Export ----------- This is again the same function as in the editor. All areas are scanned for mails that didn't previously get exported. This is done by looking for mails which have a higher number than the HighWater mark. Every such mail is then loaded and the SEEN-BY: 28 Foozle's Manual lines are checked for containing receiving systems. If not, they will be added and the message is exported to them. After having exported all mails of an area, the HighWater mark is adjusted to the highest available message in this area. When all areas have been scanned, the created packets (remember: they are always placed in the T: directory) are compressed using the selected packer. If this packer returns an error, the created packet is not deleted but renamed to "zone.net.node.point.tmp" (e.g. 2.247.4.0.tmp). You have to check which error occured, rename this file to a valid packet name (see 9.2. Outbound) and compress it manually. Don't forget to include the name of the compressed file in the *.?LO file that contains the outgoing files for that system. You can also fix the error and run Export again. Foozle now continues the export and attempts to pack the mail again. If the packing was successful the compressed bundle will automatically be added to the flow file. Local areas and the BAD_MSGS area are never scanned so that no messages will be sent from these areas. The netmail area is scanned separately because of the routing which is performed on the netmails (see 5. Routing). Netmails are never compressed by Foozle, they are put into a *.?UT file, which will be sent as a *.PKT file by your mailer. 3.3. Himark ------------------- Himark sets the HighWater marks of the specified areas to the highest message that is found in each area. This may be used by points and nodes that are at the end of the echomail topology (that don't pass echomail on to other systems), because it prevents Foozle from checking all mails that came in, so that a lot of time can be saved. 3.4. Renum ------------------ Renumbers the messages of the specified areas so that they have numbers from 1 to the number of messages in this area. The last read pointer and the HiWater mark are adjusted to the new message numbers. 3.5. Rescan ------------------- Foozle maintains a file for each area which keeps track of the messages in this area (.map). If this file is damaged or any messages have been added to / deleted from the message base, a rescan of this area is necessary (see also 2.2.2.). If you don't know what areas have been changed, you can use the command "Rescan Chg" to let Foozle rescan all those areas, some other program than 29 Foozle's Manual Foozle wrote to. 3.6. FRescan ------------------- This performs the same actions as the rescan command with the only exception that Rescan performs an optimized rescan. FRescan rebuilts the .map-File from scratch. A FRescan should only be necessary if a program other than Foozle renumbered an area. 3.7. Maint ---------- Maintenance prevents the message base from growing too large. With FzI you can specify how many messages must be preserved (these are the messages with the lowest numbers, like the rules etc.) and how many new messages must be saved or after how many days a message gets deleted. 3.8. Editor ----------- This brings Foozle into the editor mode. It may be used like "Foozle import export editor" or via ARexx to wake Foozle from sleeping in the background. 3.9. Background/BG ------------------ The background command lets Foozle wait for a command being issued via the ARexx port. If you invoke Foozle like "FOOZLE BG", Foozle initialises itself and then just sits in the background until it receives a command. It is advisable to let Foozle wait in the background rather than start it anew for every command. This saves a lot of time as no files have to be loaded and processed again. 3.10. Config ------------------- You can have many different configuration files. The default name is "Foozle" followed by one of the extensions: .prefs : your setup .areas : your areas .remap : "manual" remapping functions (optional) .ext : your external programmes (optional) If you want to use another configuration file, just specify "config" followed by the name without any extension (e.g. "Foozle 30 Foozle's Manual Config Fz2"). If the configuration files are in another directory, but are named "Foozle.*", you only have to enter the path for the files appended by a "/" or a ":" (e.g. "Foozle Config dh2:foozle/"). To edit configuration files that aren't called "Foozle.*" you must start FzI followed by the configuration name (e.g. "FzI Fz2", "FzI dh2:Foozle/"). Please note that the config command MUST be the first argument on the commandline, e.g. "Foozle import config dh1:" is not valid (the config command is ignored) - use "Foozle config dh1: import". Another way of passing the configuration path and/or name to Foozle is the definition of the environment variable "FoozleConfig". Just set it in the way described above and Foozle as well as FzI are using the specified configuration unless the configuration files can be found in the current directory. 3.11. Quit ---------- Foozle is removed from memory completely and all resources are freed. This isn't really useful to be entered at the commandline. It's thought to be issued via ARexx only. 3.12. Prio ------------------ Changes Foozle's task priority to the given value. If you run Foozle and a mailer concurrently it is recommended to change Foozle's priority to -1, so that the mailer gets enough time. 31 Foozle's Manual 4. External Files ----------------- This chapter describes the format of all external textfiles accessed by Foozle. 4.1. External Functions ----------------------- Foozle can be expanded by external functions. These can easily be installed by creating a file named ".ext" (e.g. "Foozle.ext"). Each line in this file contains one external command. Blank lines and lines beginning with a ";" are ignored. Each line consists of the name of the function which will be displayed in the "External" menu and the actual command. These two fields are seperated by one or more white spaces (spaces and/or tabs). If the function name contains a space, the whole name must be embedded in quotation marks. The rest of the line (the actual command) should never be embedded in quotation marks. If you want to use a shortcut for one function (right amiga key together with another key), the line must begin with a "@" followed immediately by the key to be pressed. If you want Foozle's screen to be moved behind all other screens, the command must be preceded by a "#" and followed by a "1" (leave screen in the background) or a "2" (move Foozle's screen to front after having executed the command). The command line may contain some templates that will be replaced by an appropriate string. These keywords are: %a : your name of current area %A : net name of current area %d : directory of current area %D : destination of current message (netmail only) %F : from string of current message %n : number of current message %O : originating address of current message %q : ask the user to enter a value/string (a query string may follow directly, embedded in sqare brackets, "[" and "]") %s : your name %S : subject string of current message %t : date/time string of current message %T : to string of current message %z : your system's primary address Examples: ; open a new shell (and put Foozle's screen into the background) NewShell #1NewShell ; Get new mail from boss (Amiga-P) "@PPoll Boss" run TrapDoor call boss 32 Foozle's Manual ; uudecode the current message (Amiga-X) @XUUDeCode #2uudecode %d/%n ; call a node "Call Node" trapdoor call %q[Enter FidoNet address:] 4.2. The UserList ----------------- The userlist file contains all persons and their addresses you often write messages to. The file can have any name and each line must comply with the form: The nickname field is optional. Examples: Hasselmeyer, Peer 2:247/4 AreaFix 247/1 af Matthias Heilmann .1 mh 4.3. The Remap-File ------------------- The remap file is needed for additional and "manual" remapping (e.g. if you didn't enable Nodelist support). The file must be named ".remap" and can be created/edited with a simple text editor. Each line of this file represents one remapping instruction. There may be blank lines in this file but NO comments. Each entry must look like: , Example: 1,Peer Hasselmeyer 2,Matthias Heilmann 1,Sysop 99,UUCP 33 Foozle's Manual 5. Routing ---------- FidoNet began with two sysops exchanging private mails (echomail appeared much later). As FidoNet grew quickly, there were many nodes sending netmails directly to other systems. Because many long distance calls had to be made, the routing was introduced. This basically means that the netmails of a local area are collected at one system and then sent together to another system which transfers the mails to its final destination (again in a local area). Foozle has a built-in routing facility, so that you don't need any additional programmes (like oMMM). Every outgoing netmail must undergo the routing process, unless you set the "Crash" or the "Hold" attribute. The routing is very easy to set up - just load FzI and select "Routing". You can now see two lists containing the routing information. On the left side you have to enter the actual destination of the messages and on the right side, where they get routed to. One wildcard, the asterisk "*", is supported and stands for "all". On the right side of the lists you can choose the "flavour" of the packets. These switches do not affect the attributes of the messages in the packet, they only determine the filename of the packet so that your mailer / scheduler knows how to handle this packet. Please note: - there is no automatic point-routing, so be sure that all of your points appear in the list (preferably at the top) - once a routing is found, no further search will be attempted, so: put individual routings at the top and the more global ones at the end Examples (supposed that the node number is 2:247/4.0): Route all netmails to 2:247/1: *:*/*.* ---> 2:247/1.0 Route all netmails to 2:247/1, execpt for points 1, 2 and 3: 2:247/4.1 ---> 2:247/4.1 2:247/4.2 ---> 2:247/4.2 2:247/4.2 ---> 2:247/4.3 *:*/*.* ---> 2:247/1.0 This can be abbreviated to: 2:247/4.* ---> 2:247/4.* *:*/*.* ---> 2:247/1.0 The same as above, but route all zone 1 mails to the zonegate: 2:247/4.* ---> 2:247/4.* 1:*/*.* ---> 2:2/1.0 *:*/*.* ---> 2:247/1.0 34 Foozle's Manual Send everything directly to its destination (mail to points will be sent to the boss): *:*/*.* ---> *:*/*.0 Host route all netmails (each netmail is routed to the net's host, e.g. a message for 3:102/17.5 is routed to 3:102/0): *:*/*.* ---> *:*/0.0 If you operate a point (e.g. 2:247/4.1) you will probably route all of your netmails to your boss: *:*/*.* ---> 2:247/4.0 But maybe you poll at two different systems (e.g. 2:247/4 and 2:241/9000), you can set up the routing like: 2:241/*.* ---> 2:241/9000.0 *:*/*.* ---> 2:247/4.0 Foozle can (depending on your selection) automatically route all incoming netmails on import. If you receive netmails, which are not for your system or one of your AKAs, Foozle will add a kludge line at the end of the message looking like: Via Foozle on [system], [date] [time] e.g.: Via Foozle on 2:247/4, 28-Mar-91 14:35:54 The message must then undergo the normal routing process and is added to the outgoing netmails of the system it got routed to. Unless any errors occured, you will never see this message in your netmail area. This method is quite efficient if you run an import after each call. The netmails can be fetched just a few seconds after they arrived at your system. 5.1. Remapping -------------- Foozle includes a fully automatic remap tool. This feature is only enabled if you are running a node and using the traplist.library for the nodelist accesses. Every mail, that is for your FidoNet address, but contains the name of one of your points as addressee is remapped to that point on import. To use this feature, you must include all of your points 4 dimensionally in the nodelist (see 6. Installing Points). As an alternative routing method, Foozle offers the ability of using a Foozle.remap file. Please read chapter 4.3. for a description of this file. 35 Foozle's Manual 6. Installing Points -------------------- This chapter is only needed by nodes wanting to support points. Installing points is quite easy as they are treated just like nodes. To add a point, you must have set the pointnet value (the point must use the same). Now load FzI, select "Systems" and add the point to your list. Give him an appropriate access level, select a packer/unpacker and optionally add the areas he wants to receive. Don't forget to add the point to your routing (as described above). The point must have a session password, which also serves as his AreaFix password. To accomplish this, the point must get an entry in your private nodelist as described in the manual of TrapList 1.40 (that comes with TrapDoor 1.80). 36 Foozle's Manual 7. AreaFix ---------- 7.1. About AreaFix ------------------ AreaFix was introduced to save the sysop of a node from the annoying business of adding/removing systems to/from the echomail distribution list. Each system now has a specific access level and can add and remove itself to/from the topology of all areas that have a lower or the same access level. 7.2. Installing AreaFix ----------------------- As Foozle has a built-in AreaFix, activating this feature is as simple as specifying a logfile for AreaFix. AreaFix also requires access to the nodelist. 7.3. Using AreaFix ------------------ Other systems can access your AreaFix by writing a netmail to "AreaFix" (the destination must be your system). The session password must be placed into the subject field. The message text contains all areas (net name) the system wants to receive - one area per line. If an entry is preceded by a minus "-", the area will be removed. The message can optionally be terminated by three dashes "---". To obtain a list of all available echomail areas, the password must be followed by a space and the option "-L". To receive a status report, the option "-Q" must be specified. A status report is automatically generated when at least one change to the echomail topology has been attempted. 7.4. Hints ---------- All AreaFix messages are processed during the import, so that you will never see any of these messages in your netmail area. But if an error occures or Foozle detects an illegal access (e.g. the other system used a wrong password) the AreaFix message will be imported just like any other netmail. The AreaFix logfile tracks all changes that have been made to echomail topolgy by other systems. Also all illegal accesses are logged in it. As Foozle doesn't send anything to another system if it detects an illegal access, you should take a look into the AreaFix logfile if you encounter a mail for AreaFix in your netmail area and tell the other system what went wrong. 37 Foozle's Manual 8. Multiple Net Support ----------------------- Foozle can operate in a multi-net environment without the trouble of having different configuration files for each network. With Foozle, you only have to specify one address as your main address and the others as your AKAs. Every AKA address can now be used just as your main address. Foozle features automatic address adjustment, i.e. that it always uses the address which seems to be the right choice for the message / packet being processed. This includes netmail routing as well as echomail export. There is only one problem: you cannot have different points for each of your AKAs. Let's say you have the two addresses 2:247/4 and 4711:20/8. It's okay to have a point with the two addresses 2:247/4.2 and 4711:20/8.2. But, the same point cannot be 2:247/4.2 and 4711:20/8.99 - the point number of one specific point must always be the same for all of your addresses. 38 Foozle's Manual 9. Inbound / Outbound --------------------- This chapter describes the names of the files that are recognized / created by Foozle. 9.1. The Inbound ---------------- The files that are recognized by Foozle are: nnnnoooo.ddx - compressed mail bundles where: dd - name of the day, the packet was created (MO, TU, WE, TH, FR, SA, SU) x - the number of this bundle (0-9, a-z) nnnn - the difference between the other systems and my net number (hex) oooo - the difference between the other systems and my node number (hex) nnnnnnnn.PKT - uncompressed mail bundles 9.2. The Outbound ----------------- The files created by Foozle are: In other/TD 1.50 mode: nnnnoooo.ddx - compressed mail bundles, see above for a description In TD 1.74+ mode: z.n.o.p.ddx - compressed mail bundles, see above for a description of dd and x. z - zone number of receiving system n - net number of receiving system o - node number of receiving system p - point number of receiving system Files only created in TD 1.50/1.74+ mode: z.n.o.p.sUT - uncompressed mail bundle, will be sent as ????????.PKT by your mailer s - status of the packet, valid characters are: O - normal C - crash (high priority packet, to be sent immediately) 39 Foozle's Manual D - direct (a crash packet to a system that has no continous mail (CM) flag in the nodelist, to be sent during the ZMH) H - hold (packet to be picked up by the remote system) z.n.o.p.sLO - so called "flow files"; list all files to be transmitted to another system - see above for a description of z,n,o,p; status: F - normal C - crash D - direct H - hold z.n.o.p.REQ - file request; list of all files you want to receive from a system; created only by the File Request function (see above for a description of z,n,o,p) Files only created in 2D (other) mode: nnnnoooo.sUT - uncompressed mail bundles where: nnnn - net number of receiving system (hex) oooo - node number of receiving system (hex) s - status, see above nnnnoooo.sLO - flow files, see above nnnnoooo.REQ - file requests, see above 40 Foozle's Manual 10. The Logfile --------------- Most of the actions performed by Foozle are noted in the logfile. Each entry occupies one line and consists of an indicator character, the date, the time and a text string describing what happened. The indicator characters give you a hint on what is logged. Used characters are: | - plain information + - info on the completion of an action * - error # - security failure (only on import) ! - important information for you (e.g. mails for you; only on import) 41 Foozle's Manual 11. Limitations --------------- Number of areas: unlimited Number of areas(AreaFix): 32767 Number of msgs/area: 16383 Number of msgs(maillist): 423 Max. size of message: 32764 bytes (including header) Number of nodes: 255 Number of nodes/area: 63 Number of routings: 255 There may exist other limitations that you probably never reach. 42 Foozle's Manual 12. Registration ---------------- 12.1. Why Register ------------------ Foozle is a copyrighted piece of software that is brought to you under the concepts of shareware. The freely disributable version floating around on many BBSes may only be used for an evaluation period of up to 4 weeks. If, after this period, you find that Foozle fits your needs and you want to keep on using it, you must register. If you don't want to use Foozle anymore, just throw it in your trashcan. The registration fee also supports the programming efforts of the author. So by contributing the fee you will accelerate the further development of Foozle. As a side effect, the annoying requesters poping up on startup of the unregistered version will vanish. 12.2. How To Register --------------------- To register your copy of Foozle you must do the following: 1. Print out the file "Register.txt" (should be included in the archive you got this manual from), fill it out and send it to: Foozle Development Centre c/o Peer Hasselmeyer Bursastr. 6 W-6100 Darmstadt Germany You can optionally fill out the file with a text editor and send it via netmail (crash is recommended) to 2:247/4. Please note that the system is only guaranteed to be online from 23:00 - 05:00 UTC. 2. Pay the registration fee of 50,-- DM either by international postal money order, by cheque or let your bank transfer the amount to my account at Postgiroamt Frankfurt (BLZ 500 100 60), account 514143-606, name "Peer Hasselmeyer". 43 Foozle's Manual 13. License ----------- 13.1. Notice ------------ Peer Hasselmeyer, the author of Foozle, has exclusive rights to all programmes that came with the original distribution (archive or disk, also referred to as "the software") which are protected by both german and international copyright laws. You are licensed to use this software according to the terms that follow. Any use of the software indicates your acceptance of these terms, both for the supplied version plus for any updates you may receive. The software is offered to you under the concepts of shareware, which means that you can use it for an evaluation period of up to 28 days without paying any charge. If you use the software after this period, you must register. You may not use, copy, modify or distribute the software or any copy - in whole or in part - except as expressly provided for in the license. If you violate any terms of the license, your license is terminated. You agree to cease distributing the software if requested to do so by the author. 13.2. You May ------------- - install and use this software for your personal use on a single microcomputer - make verbatim copies of the original distribution without any files being ommitted/added/changed - distribute those copies of the software if NO charge is asked for except for the media - upload the software to as many BBSes as you like 13.3. You May Not ----------------- - alter the software and/or the accompanying files in any way - decompile, disassemble, translate, convert to another programming language or otherwise reverse engineer the software - grant sublicences, leases or other rights in the software - rent the software to others 44 Foozle's Manual 13.4. No Warranty ----------------- The software is provided "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. In no event will the author be liable to you for any incidental or consequential damages arising from your use or inability to use the software (including, but not limited to loss of data or data being rendered), even if the author has been advised of the possibility of such damages or for any claim by any other party. 45 Foozle's Manual 14. Acknowledgements -------------------- The following names are either trademarks or the efforts of the person and/or company listed: - Amiga, AmigaDOS, CLI and WorkBench by Commodore-Amiga, Inc. - Amiga DOS Resource Project and arp.library by ARP Authors - Arc by System Enhancement Associates - AreaFix (for MS-DOS) by Greg Dawson - ARexx by William S. Hawes - BinkleyTerm by Alan D. Applegate, Robert Hartman and Vincent Perriello - BinkleyTerm Amiga by Jürgen Hermann - Chameleon Editor by Jürgen Hermann - CheckPackets by Peer Hasselmeyer - ConfMail by Bob Hartman, Spark Software Inc. - EchoMail by Jeff Rush - FastFonts by C. Heath, Microsmiths Inc. - FastPoint by Paul Black - Fido and FidoNet are trademarks of Tom Jennings, Fido Software - Four dimensional addressing and FSC-0039 by Mark A. Howard - FTS-0001 by Randy Bush - Global Conference Control and GCChost by Davide Massarenti - Juliet by Gregory Kritsch - LHarc by Haruyasu Yoshizaki - LHarc Amiga by Paolo Zibetti - License Agreement inspired by SmarTerm, Persoft, Inc. and the TrapDoor license - MS-DOS is a trademark of Microsoft Corporation - MSGID/REPLY kludges and FSC-0041 by Jim Nutt - oMMM by BS Software - PID kludge and FSC-0046 by Joaquim Homrighausen - PointManager by Mario Pacchiarotti - RMB by Michael Richardson - ScanToss by Michael Matter - Tick by Barry Geller - TosScan by Joaquim Homrighausen - TrapDoor by Maximilian Hantsch and Martin Laubach - TrapList and traplist.library by Martin Laubach and Maximilian Hantsch - TrapToss by René Hexel and Maximilian Hantsch - Welmat by Michael C. Richardson and Russel McOrmond - Zoo by Rahul Dhesi Many thanks to: - the beta-testers: Timothy J. Aston, Matthias Heilmann, Carl-Christian Kanne, Andreas Netscher, Martin Ortlepp, Heiko Richter, Silvia Wenz - Tim Aston for the free registered TransAmiga - Maximilan Hantsch and Martin Laubach for their great TrapDoor/TrapList package - Städtische Kliniken Darmstadt for their MS-DOS machine - Günter Greschenz for the HD Installer 46