XConfig Combined Documentation and Example Configuration for XTick and XRaid Copyright (c) 1995 by Robert Williamson, FIDONET#1:167/104.0 ALL RIGHTS RESERVED This software is provided "as is", without warranty and/or guarantee of any kind. You may use and/or distribute this software and copies of it, as long as no alterations have been made, no files have been added to/omitted from the original distribution archive and no charge is asked for. This package may be freely distributed via BBSs, ADS, AmiNet and software libraries such as Fred Fish's and Aminet CD-ROMs, and other similar electronic channels. This package may NOT be distributed SAN, Disk magazines, PD libraries or BBSs and Services that charge extra for file transfers without authorization from, and compensation to the author. XConfig.DOC and the format of XTick.cfg are, Copyright (c) 1995 by Robert Williamson, FIDONET#1:167/104.0 This document may be used as the config file for both XTick and XRaid. Simply duplicate it as xtick.cfg and edit. There is no need to remove the text, as it is ignored when read as a config file. When you are satisfied that the configuration is correct, you can strip the text from this config by using the XRAID command STRIPCFG. The config is also stripped whenever XRaid updates it. Configuration keywords start in column 1, anything preceeded by at least 1 space is considered a comment. There are no 'comment' symbols required in this copyrighted config format. The Xconfig format uses the readargs() function and standard AmigaDos templates for all configuration items. Note that only a few template parameters are marked as '/A' (REQUIRED), since this also makes the parameter position-dependant. This allows a very freeform method of usage and configuration. It is not permitted to leave the value of an un-commented keyword blank. For those keywords which are not required, they are UN-SPECIFIED by commenting (inserting one or more spaces before it), or by setting the value to either "" or OFF as noted for the particular keyword. Although an effort is made to catch blank keyword value errors, it is not fool-proof. Any such errors that go undetected can produce unexpected results. A quick explanation of AmigaDos Template Parameters used: none - item is position dependant /C - item is a comma-separated string This is not a standard template /A - item is required and must be in this position. /K - item requires that both the KEYWORD and a value be specified. /N - item is a number /S - item is a boolean switch which is set TRUE when the keyword is specified, and FALSE when it is not. /F - a string may be specified, it MUST be the last item. /M - multiple items may be specified Configuration keywords are ordered as follows: Defaults and Globals This includes your name and default address, files, paths, file modes, tic modes and allowable xraid commands Groups config fileecho and FDN groups Uplinks config the systems that feed you, options, groups Site/SiteAKA config the systems that you feed, options, permissions, ticfile modes, groups Area config area and FDN names and descriptions area paths area execs overides area sites and overides Addressing: Addresses can be specified in a number of formats in the Xconfig format, the preferred being FQFA. The minimum acceptable is 3d (z:net/node.) for FidoNet and FTNS defined in FTNLIST. All other FTNs must be specified as 5D or FQFA. Address Formats: FQFA - ftn#zone:net/node.point (all must be present) 5d - zone:net/node[.point]@ftn (if no point, 0 is assumed) 4d - zone:net/node.point 3d - zone:net/node Paths: A trailing slash is automatically added to paths when required. Quotes: Configuration items do not need to be quoted. Command Parameter Expansion: An extensive set of parameter expansion/substitution variables are provided. The current design allows a maximum of 36. The six command keywords: PACKER, IMPORTER, HATCHEXEC, TICKEXEC, and the AREA overrides AHATCHEXEC and ATICKEXEC, allow for both multiple commands (» parameter) and the expansion of parameters somewhat similar in concept to SilverBox parameters and Ftick's EXECUTE keyword with some very special enhancements. Please see XTICK.doc for explanations. These command strings may contain the following templates. Note that the words or substrings in UPPERCASE refer to the values of TIC file keywords. Description Source of Value of parameter Ticked Hatched » : insert LF (ALT-0 on keyboard) config config %a : name of AREA tic file config %e : AREADESCription tic file config %n : FILEname tic file cmdline %g : original filename in FULLNAME internal internal %m : FNC version of FULLNAME internal internal %f : filename including path internal cmdline %d : DESCription of FILE tic file filenote %l : SIZE (length) of FILE tic file internal %y : size of FILE as calculated internal internal %c : CRC of FILE tic file internal %x : crc of FILE as calculated internal internal %b : bad directory config config %i : inbound directory config config %o : outbound directory config config %p : directory (path) of current area tic file config %j : directory (path) for autoadd area config config %t : name and path of recd tick file cmdline -- %u : name and path of created tick file internal internal %k : tic directory cmdline config %r : FROM address (FQFA) tic file internal %s : ORIGIN (source) address (FQFA) tic file internal %h : host address (FQFA) internal config %0 : host FTN (domain) internal internal %1 : host zone internal internal %2 : host net internal internal %3 : host node internal internal %4 : host point internal internal %5 : from/to FTN (domain) tic file internal %6 : from/to zone tic file internal %7 : from/to net tic file internal %8 : from/to node tic file internal %9 : from/to point tic file internal Explanation of Config Keywords and Example Configuration: SYSOP Robert Williamson This is the name used by XRaid when sending messages via the SENDCMD, GETHELP and GETSTATUS commands. HOST FIDONET#1:167/104.0 The default address for all filechos which do not have an OverRide HOST address specified. This must be YOUR address. POINTNET 30730/99 If specified in the format FakeNet/Point, this will be used in the Path and Seenby of POSTTICK and POSTHATCH echomail messages. If specified as a Point number only, this will be used as the point in MSGID address and in NetMail INTL and FMPT control lines. UTC -360 The offset in minutes will be used to calculate the UTC from your local time. This value is added to your local time before XTick inserts any date-/time-strings into the path-lines of a Tick file. In addition those path lines will be marked with the "UTC" string. FTNLIST "AMIGANET 39 AMIGANET 40 AMIGANET 41 IBMNET 40:6499 FishNet 77:77" The FTNLIST is a List of FTN NAMES and matching zones or zone:net. This list should only consist of those FTN's in which you are connected to FileEchos. If more than one FTN uses the same Zone, add the net to one of them in the list. When a Zone is qualified by Net, the Zone and Net must be separated by a ':'(colon). Zone:Net combinations MUST be the last in the list. FidoNet zones 1-6 need not be included in the list as these are handled internally. No other FTN is permitted to use Zone numbers 1 though 6, but the Zone:Net combination will handle this.. QTYPE XFQ Defines the method of queueing outbound files. Two methods are used on the Amiga: FLO - Flow File system (4d) XFQ - xferq.library system (5d) If QTYPE is set to FLO, 4 dimensional flow files and packets will be created. These may be either .FLO/.OUT or .HLO/.HUT, depending upon the configuration of the site. If QTYPE is set to XFQ, 5 dimensional packets of either type .OUT or .HUT will be created. (There are no flow files in xferq system). Please not that some mailers may be hybrid. These mailers will require 4d filenames but use xferq.library with a flo-file conversion utility. Such hybrid systems are not supported. XPRI 50 -50 This keyword is used for QTYPE XFQ ONLY Priority for Routed and Hold mail (range -127 to +127) These should be the same values as used in your mailer. You can set Routed to the same value you use for Crash or Normal. Paths: IN Mail:Inbound/fidonet Your inbound directory. There is NO default value. OUT Mail:outbound Your outbound directory. There is NO default value. BAD BBSF5:BAD The directory where XTick will move all bad files. These include Tic's and associated file for an unknown area, that did not match CRC or file size checks, from an unknown system, from a system without hatch permission etc. Tick files without the associated file are NOT moved. There is NO default value. AUTOADDPATH BBSF5: This is the directory where XTick will create new directories for auto added fileechos. The name of the directory created for the new fileecho area is based on the fileecho tag. If a directory already exists with that name, then XTick will use it, instead of creating a new one. TIC Mail:outbound/flo The directory where XTick will create all TIC files for transmission. This can be set to the same path as OUT. However, if your mailer was designed with security in mind, it is preferable that this be set to some other path. FLOWFLO This keyword is valid for QTYPE FLO ONLY. Please note that it is commented out here by the preceeding space. This is the directory where your flow file system mailer expects to find ?lo files. Mailers designed with security in mind allow setting this to something other than OUTBOUND:. FLOWFNC This keyword is valid for QTYPE FLO ONLY. Please note that it is commented out here by the preceeding space. The directory where files with filenames converted to msdos 8.3 format will be stored for transmission. XTick places renamed copies here of all files that require FNC (File Name Conversion) for sites marked as needing FNC. Mailers designed with security in mind allow setting this to something other than OUTBOUND:. It is the operators responsiblity to clean-up. AUDIT MBACK:audit/ Please note that it is commented out here by the preceeding space. GLOBAL Directory to backup created TICs and packets. If set to "" or not specified, they will not be saved. BACKUP MBACK:INHOLD/ Please note that it is commented out here by the preceeding space. GLOBAL Directory to backup received TICs that were successfully processed. If set to "" or not specified, processed tic's will be deleted. LOGFILE LOG:XTICK.LOG Full PathName of the logfile. XTick and XRaid will use the same log. LOGLEVEL 3 Loglevel control tha mount of info appearing in the log. The range is 0 to 9. HELPFILE CFG:XRAID.HLP Full path Name of the help file to be used by XRaid. FILEBONE BBSF5:echolist/FILEBONE.NA Global FileEcho List used by XRAID. You can edit this file to add any information you wish. You must follow the format described. Display Configuration: WSPEC "KCON:0/10/640/100/" GLOBAL device and size/position of XTick window, must be terminated with a '/' WFLAGS "/INACTIVE/AUTO/" GLOBAL Window flags for XTick window, must begin and end with a '/' PSCREEN "The Roof Multi-FTN Server" GLOBAL public screen, set to "" if unused NewFile Annoucements: A newfiles message can be posted in one or more echos when a file is hatched or ticked (received). In both *POST cases, if set to OFF, or if not specified, no messages are posted. These can be overidden by the AREA post overides: AHATCHPOST ATICKPOST The echomail Messages are written as .PKTs in the GLOBAL default IN directory or the AREA's IN overide and will be imported using the defined IMPORTER command. TICKPOST NEWFILES TICKPOST (TAGNAME...TAGNAME> A list of space separated ECHO TagNames in which to post a message to announce received files. HatchPost is never executed when Forwarding (processing a Tic) HATCHPOST (TAGNAME...TAGNAME> A list of space seperated ECHO TagNames in which post a message to announce hatched files. Command Configuration: PACKER run >nil: XPack GLOBAL Command to route and pack outbound netmail Accepts multiple commands and command parameter expansion. IMPORTER "run >nil: RX mail:rexx/InboundMGR TOSSPKT %0" GLOBAL command to import echomail created by *POST commands and netmail to yourself generated by Xtick or Xraid. Accepts multiple commands and command parameter expansion. Execute on Hatch or on Tick: If a file for an AREA is hatched or ticked (received), the given command is executed (unless the keyword is set to OFF for the AREA). See 'EXEC Commands and AREA OverRides' section of XTICK.DOC for more information. HATCHEXEC "Echo >>LOG:TICKLIST %n %s %l %a %d" GLOBAL default command to execute when a file is HATCHED. Accepts multiple commands and command parameter expansion. Set to "" to disable. Can be overidden by Area. HatchExec is never executed when Forwarding (processing a Tic) TICKEXEC "Run Rx Mail:rexx/TickMGR PROCESS %n %s %l %a %d" GLOBAL default command to execute when a file is TICKED. Accepts multiple commands and command parameter expansion. Set to "" to disable. Can be overidden by Area. File Modes: FILEMODES defines how old tic files are handled when rehatching, how files are handled when hatching from a different path than that defined for an area, when processing a tic that has a REPLACES keyword, and when duplicate filename is encountered. Template: KILLTICS/S,TICKREPLACE/S,HATCHREPLACE/S,TICKOVERWRITE/S,HATCHOVERWRITE/S FILEMODES KILLTICS HATCHOVERWRITE HATCHREPLACE TICKREPLACE the REPLACES file named in the tic file will be deleted if it is found in the filearea PATH. If TICKREPLACE IS NOT specified, the REPLACES file is renamed to filename".OBS" TICKREPLACE can be OverRidden per area by an AREA NOREPLACE option. TICKOVERWRITE any file of same name as FILE will be over-written by new one. If TICKOVERWRITE is NOT specified, any file with the same name as FILE is renamed to filename".OLD" before new one is moved to the filearea. HATCHREPLACE if REPLACES name is specified, the file will be deleted. If HATCHREPLACE is NOT specified, the REPLACES file is renamed to filename".OBS". HATCHOVERWRITE if a file is hatched from a path other than AREA path, FILE will be moved to area and any file of same name as FILE will be over-written. If HATCHOVERWRITE is NOT specifed, any file with the same name as FILE is renamed to filename".OLD" before the new file is moved to the filearea. KILLTICS the TICDIR will be scanned for old tic files for the same AREA, SITE AND FILENAME. If KILLTICS is specified, ALL tics will be read, and all matchs found will be deleted. If NOT specified, only the first old tic found is deleted. Tic Modes: TICMODES defines the default format of the tic files created by XTICK. This default format can be over-ridden by each SITE's config. TICMODES Template: STRIPSB/K,USEMLD/S,USEVIA/S,USETO/S,USEMAGIC/S,USEAD/S,USEFN/S,USETI/S TICMODES STRIPSB FTN USEMLD USEVIA USETO USEMAGIC USEAD USEFN USETI STRIPSB (ALL|FTN|ZONE|NET) ALL - All SEENBYS are stripped FTN - All SEENBYS from other FTNs are stripped ZONE - All SEENBYS from other ZONES are stripped NET - All SEENBYS from other NETs are stripped USEMLD - LDESC lines are added to TIC USEVIA - CREATED lines are written to TIC as VIA lines, "Created by' is stripped from CREATED line before conversion. USETO - TO lines are added to TIC Some TICK handlers will choke on TO lines, notably FTick. USEMAGIC - MAGIC lines are added to TIC USEAD - AREADESC lines are added to TIC USEFN - FULLNAME lines are added to TIC USETI - when hatching, XTick will search for a TicInclude file with the same names as the fileto hatch and the extension "TINC". The TINC file will be read and fields added to the TIC according to the TICMODES options and the Site's TICK options. In all cases, the lines are added only if the information is available. ie a MAGIC line will not be added if the MAGIC name is not defined. Allowable XRaid commands: ALLOWCMDS defines which sensitive functions and AreaMgr commands will be accepted. See XRAID.DOC for more information. Template: ALLOWFWD/S,AUTOADDUSERS/S,AUTOADDAREAS/S,ALLOWALL/S,ALLOWNOTIFY/S, ALLOWPASSWORD/S,ALLOWECHOPASSWORD/S,ALLOWMESSAGE/S,ALLOWTICK/S, ALLOWPAUSE/S,NORESUME/S,MINLEVEL/K/N ALLOWCMDS ALLOWNOTIFY ALLOWMESSAGE ALLOWTICK NORESUME MINLEVEL 30 AUTOADDAREAS Should areas be created when files are received for an unknown area. AUTOADDUSERS Should unknown users be automatically added if an XRaid request is received. (NOT YET IMPLEMENTED) ALLOWFWD Should a system be able to request fileechos not on site. If not specified, FWDREQ will be false for all sites. ALLOWALL Should a system be able to use the %+ALL command to connect all available areas. ALLOWGROUP Should a system be able to use the %+ command to to connect to all areas i a group.. ALLOWNOTIFY Should a system be able to use the %NOTIFY command to toggle the notify option. ALLOWPASSWORD Should a system be able to use the %PASSWORD command to change the areamgr (raid) password. ALLOWECHOPASSWORD Should a system be able to use the %ECHOPASSWORD command to change the fileecho (ticfile) password. ALLOWMESSAGE Should a system be able to use the %MESSAGE command to toggle the netmail announcement/file attach. ALLOWTICK Should a system be able to use the %TICK command to toggle the Tic file options. ALLOWPAUSE Should a system be able to use the %PAUSE command to temporarily turn off all the areas. If this is not specified then XRAID will also prevent the system from using the %RESUME command. NORESUME Disables the use of the %RESUME command even in %PAUSE is allowed. COMPRESSION Should a system be able to use the %COMPRESSION command to change the archiver for the TicPack options. Please note %COMPRESSION is neither supported, nor included in template, but is documented in case we do add support in the future. MINLEVEL The minimum raid level a user must have to use the allowed commands. Group Configuration: Each GroupList defines a set of FDNs as a GROUP. These FDNs can be those defined as an AREA FDN (acroynom of a File Distribution Network) such as LOCAL, or real FDN names as found in FILEBONE.NA. The FIRST GROUPLIST defined is GROUP 1 and is considered as the LOCAL FDN. GROUP numbers are automatically assigned in a sequential manner as the config is read. Each AREA must be assigned to one of these GROUPs. Each UPLINK will have one of more of these GROUPs defined and will be considered the FEED for the GROUP and the FDNS in that GROUP. Each SITE will have a permission set to allow access to one or more of the GROUPs. All SITEs have access to GROUP 1. GROUPLIST Template: GROUPLIST/K/A/F GROUPLIST LOCAL,MTL GROUPLIST ADS,ANET GROUPLIST SDS Uplink Configuration: Uplinks are the default systems to which XRAID will forward requests for fileechos not presently on the system. UPLINK Template: UPLINK/K,MANAGER/A,PASSWORD/A,GROUPS/A UPLINK FIDONET#1:167/100.0 ALLFIX PASSWD 1,3 UPLINK FIDONET#1:167/207.0 ALLFIX PWDPWDP 2 UPLINK AMIGANET#40:6/0.0 ALLFIX PASSAWORD 2 UPLINK address of site MANAGER name of FIleEcho ARea Manager used PASSWORD our raid password with this site GROUPS Comma-separated lists of GROUPS that we have access to on this site. This list may be of FDNs or groups of FDNs as defined by GROUPNAME. UPLINK FIDONET#1:167/100.0 ALLFIX mypassword SDS,ADS,DFN UPLINK AMIGA#40:600/0 ALLFIX mypwds ANET Site Configuration: SIte configuration defines the addresses, options, passwords, levels, and permissions for a site. Two forms of site configuration are used: the SITE and the SITEAKA templates. The SITEAKA template is used to define additional addresses and aka-specific parameters when site having more than one address is connected to FDNs in more than one FTN. The SITEAKA entry always applies to the previous SITE entry. SITE Template: SITE/K,PW/K,RPW/K,RLVL/K,FWDREQ/S,AUTOADD/S,GROUPS/K, HOLD/S,ATTACH/S,FNC/S,NOTIC/S,TIC3D/S,NOREPORT/S, NOTO/S,NOMD/S,NOMA/S,NOAD/S,NOFN/S,NOTI/S SITEAKA Template: SITEAKA/K,PW/K,RPW/K,RLVL/K,FWDREQ/S,AUTOADD/S,GROUPS/K, HOLD/S,ATTACH/S,FNC/S,NOTIC/S,TIC3D/S,NOREPORT/S, NOTO/S,NOMD/S,NOMA/S,NOAD/S,NOFN/S,NOTI/S SITE - primary address of site, cannot be specified in the same line as SITEAKA SITEAKA - aka of SITE, cannot be specified in the same line as SITE accepts all options, over-riding those set for the SITE or a SITEAKA defined previously. PW - TIC file password, minimum 6 characters, case insensitive RPW - RAID password, minimum 6 characters, case insensitive RLVL - RAID Access Level FWDREQ - site can request filechos we don't have and the request will be forwarded to uplink AUTOADD - new areas from this site will be automatically added GROUPS - Groups to which site has access TIC3D - addresses in TIC file are 3d instead of FQFA for sites running poorly written File Forwarders NOREPORT - do not send report to site FNC - send filenames in 8.3 format The following three can be overidden by an AREA's ECHOTO config HOLD - Put stuff on hold for site NOTIC - do not send TIC file to site ATTACH - send file attach message to site Disable of TicFile extensions: NOTO - TO keyword is not added to TIC file for this site NOMA - MAGIC keyword is not added to TIC file for this site NOAD - AREADESC keyword is not added to TIC file for this site NOFN - FULLNAME keyword is not added to TIC file for this site NOTI - TICINCLUDE data (execpt for an included DESC), is not added to TIC file for this site SITE FIDONET#1:167/192.0 PW ROOFRX RPW erwrwewer RLVL 50 GROUPS 1,2,3 SITEAKA AMIGANET#40:600/12.0 RLVL 20 GROUPS 2 SITE FIDONET#1:167/151.0 PW xcxcxcxc RPW bvbvbvbv RLVL 50 NOTO SITEAKA AMIGANET#40:600/0.0 RLVL 75 HOLD SITEAKA AMIGANET#40:6/1.0 SITE FIDONET#1:167/107.0 PW sdsdsd RPW Tasdasd RLVL 50 GROUPS 1,2,3 SITE FIDONET#1:167/104.99 PW werwer RPW dfgfdg RLVL 50 FNC NOTO NOAD GROUPS 1,2,3 SITE FIDONET#1:167/104.98 PW werwere RPW hjkhjkhjk RLVL 50 FNC TIC3D GROUPS 1,2,3 SITE FIDONET#1:167/104.97 PW rtyrtyy RPW dfgdfgg RLVL 50 TIC3D GROUPS 1,2,3 SITE FIDONET#1:167/100.0 PW dfgdfgdf RPW dfgdfg RLVL 50 FNC GROUPS 1,3 FileEcho Configuration: Areas configuration uses the AREA, ECHOTO, ADESC, CROSSHATCH, ATICKPOST, AHATCHPOST, ATICKEXEC, AHATCHEXEC keywords. The first two are REQUIRED. AREA Defines the tagname and path of the filearea, with optional area host address, area password, area description and REPLACES disable. AREA Template: AREA/K,APATH/K,APW/K,ARLVL/K,FDN/K,GROUP/K/N,IN/K,OUT/K,ANOHATCH/S,ANOREPLACE/S,HOST/K AREA - TAGNAME of FileEcho (required) APATH - Path of fileecho (required) FDN - acrynom of File Distribution Network GROUP - group number for this fileecho IN - Inbound post message directory for AREA OUT - Outbound notify/report message directory for AREA APWD - Password of AREA ARLVL - User RAID Level needed to request AREA HOST - our address for this FileEcho ANOHATCH - hatching is not permitted in this AREA ANOREPLACE - disallow Replaces filename ADESC Provides a Description of the AREA. This is used in reports and in the AREADESC field of the TIC file. ADESC Template: ADESC/K FDND Provides a description for the FDN for this fileecho. FDND Template: FDND/K CROSSHATCH Defines the tagname and file specs for cross hatching. CROSSHATCH Template: CROSSHATCH/K,CROSSSPECS/A CROSSHATCH - TAGNAME of AREA to hatch any file matching patterns in CROSSSPECS CROSSSPECS - AmigaDos file specifications multiple specs, as well as pattern matching,is permitted eg: CROSSHATCH POINTDIFFS SMALLNL.#? ECHOTO Defines the sites connected to the filearea and the permisssions and overrides for each site. ECHOTO Template: TOSITE/A,ISFEED/S,CANHATCH/S,HOLD/S,NOTIC/S,NOSEND/S,ATTACH/S TOSITE - address of site connected to FileEcho ISFEED - TOSITE is the FEED for this echo Do not send files if recd from TOSITE NOSEND - TOSITE is the FEED for this echo NEVER send files to TOSITE CANHATCH - TOSITE can hatch files in this echo The following three will overide the settings in the SITE defaults, for this AREA only. If NOT SPECIFIED, the GLOBAL default will be used, if any. HOLD - Put files on Hold for TOSITE NOTIC - do not send TIC file to TOSITE ATTACH - send file attach message to TOSITE ATICKPOST Defines the echos in which to post TICK annoucements for this AREA. If specified, these echos are used instead of the GLOBAL TICKPOST echos. If set to OFF, the function is DISABLED for the AREA. If NOT SPECIFIED, the GLOBAL definition will be used, if any. ATICKPOST Template: ATICKPOST/K/F AHATCHPOST Defines the echos in which to post HATCH annoucements for this AREA. If specified, these echos are used instead of the GLOBAL HATCHPOST echos. If set to OFF, the function is DISABLED for the AREA. If NOT SPECIFIED, the GLOBAL definition will be used, if any. ATICKPOST Template: ATICKPOST/K/F ATICKEXEC, AHATCHEXEC These are the commands to execute when a tick or hatch has occured in the AREA. These keywords accept multiple commands and parameter expansion. If set to OFF, the function is DISABLED for the AREA. If NOT SPECIFIED, the GLOBAL definition will be used, if any. See 'EXEC Commands and AREA OverRides' section for more information. Templates: ATICKEXEC/K/F AHATCHEXEC/K/F FILETICKEXEC,FILEHATCHEXEC (not yet implemented) These commands will be executed if the ticked or hatched file matches the defined file specification. Templates: FILEHATCHEXEC/A,CMD/F FILETICKEXEC,CMD/F eg: FILETICKEXEC ????DIFF.A?? run >nil: DIFFMGR %f FILETICKEXEC #?.ADS Delete %f AREA ROOF APATH BBSF6:roof/ FDN LOCAL GROUP 1 APW ROOFRX ARLVL 0 ADESC Roof Utilitites FDND Local FileEchos CROSSHATCH TEST XTICK.#? XRAID.#? AHATCHPOST ROOF_PROJECT ECHOTO FIDONET#1:167/100.0 CANHATCH NOSEND ECHOTO FIDONET#1:167/151.0 CANHATCH ATTACH ECHOTO AMIGANET#40:600/12.0 ATTACH AREA SHELTER APATH BBSF6:WPL/ FDN LOCAL GROUP 1 ARLVL 0 ADESC Shelter and Melody Mailers FDND Local FileEchos AHATCHPOST ROOF_PROJECT FALCON_CBCS ECHOTO FIDONET#1:167/151.0 CANHATCH ATTACH ECHOTO AMIGANET#40:600/12.0 ATTACH AREA ADSFIDO APATH BBSF5:ADSFIDO/ FDN ADS GROUP 2 ARLVL 50 ADESC Amiga FidoNet Software FDND Amiga Distribution System ECHOTO FIDONET#1:167/151.0 CANHATCH ATTACH ECHOTO FiDONET#1:167/192.0 CANHATCH ATTACH AREA ECHOLIST ANOHATCH FDN SDS GROUP 3 APATH BBSF5:ECHOLIST/ ARLVL 60 ADESC EchoList and Policies FDND Software Distribution Service AHATCHEXEC OFF ECHOTO FIDONET#1:167/100.0 ISFEED NOSEND ECHOTO FIDONET#1:167/151.0 AREA TEST APATH RDEV:xT/TEST/ FDN LOCAL GROUP 1 ARLVL 10 ADESC Test File echo FDND Local FileEchos ECHOTO FIDONET#1:167/104.97 ECHOTO FIDONET#1:167/104.98 ECHOTO FIDONET#1:167/104.99