; IOSMAIL.CFG => IOSMAIL Configuration File! ; ; by.... ; ; *** ** Erik Williams ; ** *** SunFox Productions, Ltd. ; *** ** University of Central Florida, Orlando ; ** *** REALITY.SYS corrupted! Restart universe (Y/N)? ; ; ; Like BINKLEY.CFG in this archive, all you should have to do with ; this file is edit the node numbers and paths. ; ; ; This is the only label I have needed for IOS...it imports and ; exports mail in one pass and keeps the mail packets around in ; case there was any problems. The three events prepare a "POLL ; FILE" for 51:1/0...a 60-byte file that will cause Bink/ST to ; call out automatically to the Twilight Zone. ; ; #INANDOUT Commands -a -i -s -c -x -p -o -t Event All 00:00 00:05 Prepare-Poll 51:1/0.0 Event All 05:59 06:05 Prepare-Poll 51:1/0.0 Event All 11:59 12:05 Prepare-Poll 51:1/0.0 SendAlwaysPKT #endlabel ; #ENDALL ; ; ; "Hello, my name is..." ; ; SysOp Erik Williams ; ; ; These address statements are placed in the exact same order as ; used in BINKLEY.CFG. ; ; Address 51:1/11.0 Address 1:363/169.0 ; ; ; ApplZone is roughly equivalent to the Domain statement in ; BINKLEY.CFG. It takes the zone number, the path to the outbound ; folder associated with that zone (*WITHOUT* the hex representation ; of the zone number...IOS figures that out with the first parameter), ; and the nodelist associated with that zone. ; ; ApplZone 51 d:\atarinet\ atrinet.ftn ApplZone 1 d:\fidonet\ fidonet.org ; ; ; The password statements are very important in terms of routing mail. ; Every node you communicate with must have a Password keyword associated ; with it, even if that Password keyword does not have an actual session ; password in the directive! An example of the latter is the Password for ; 51:3/6...all I am doing is telling IOS that I want all mail to Bryan ; Hall's board to be LZHmail. ; ; Before you send crashmail to a node, make sure your IOSMAIL.CFG has a ; Password and a Route for that node (more on Route in a minute). ; ; Password 51:1/0.0 # $xxxxx %LZHmail Password 51:3/6.0 # %LZHmail Password 1:363/31.0 # $xxxxx %ARCmail Password 1:363/112.0 # $xxxxx %LZHmail Password 1:363/32.0 # %ARCmail ; ; ; The following keywords control the logging done by IOS. LogFile tells ; IOS where to place the log, LogLevel tells IOS how much I want (level ; 1 is pretty darned verbose), and DateFormat allows me to specify the ; time stamping to log entries. ; ; My DateFormat will produce a log-line like this: ; ; # 06 Oct 00:00:06 IOS IOSmail 0.89 execute INANDOUT ; ; NiceOutput and MSGreport add some descriptive logging to the logfile. ; ; Logfile d:\logs\ios.log LogLevel 1 DateFormat %d %b %H:%M:%S NiceOutput MSGreport ; ; ; Here are two special message area definitions. Netmail is just like ; its counterpart in BINKLEY.CFG. The TrashArea is for messages that ; do not fit with the echoes defined in AREAS.BBS (my AREAS.BBS is ; included in this archive)...so they will be dumped here! ; ; An example would be if A_BBS_ADDS is the definition in AREAS.BBS, but ; the incoming messages are for area A_BBS_ADS, then the incoming messages ; will be tossed into the TrashArea. ; ; Netmail d:\netmail\ TrashArea d:\mess\a_bad ; ; ; Here are the archiver specifications for ARC, LZH, and ZIP...the three ; major compression schemes. If the inbound packet does not match one of ; these schemes, then the archiver specified with the Archiver keyword ; will try to work with the packet (in this case, I use WhatArc 2.02). ; ; Archiver c:\turbo\bink\whatarc\whatarc.ttp x a ARCarchive c:\turbo\bink\whatarc\arc602.ttp x m LZHarchive c:\turbo\bink\whatarc\lharc.ttp x m -m ZIParchive c:\turbo\bink\whatarc\zipjr.ttp -x -a -mt ; ; ; Here are the paths I use for IOS...the Inbound and Outbound are ; exactly the same as the inbound and hold paths in BINKLEY.CFG. The ; MailTemp keyword specifies a temporary directory for uncompressing and ; working with the mail packet. ; ; Inbound d:\netfile\ Outbound d:\atarinet.033\ MailTemp d:\temp\ ; ; ; The Route statements are used to tell IOS where mail should go out ; there in net.land. The Routes work in conjunction with the Password ; directives earlier in this configuration file. Note that you can use ; wildcards to replace specific node numbers...in fact, you will more ; than likely use this for all of your host-routed mail! ; ; You must have a route to a node for crashmail (hence the reason for ; the routes without wildcards. When you write crashmail, make sure ; that you have the Route and the corresponding Password entries in ; this file. ; ; Route 51:1/0 51:* Route 51:3/6 51:3/6 Route 1:363/31 1:* Route 1:363/32 1:363/32 Route 1:363/42 1:363/42 ; ; ; Miscellaneous mail traffic control directives and other stuff. ; ; File-To * Arc-For 51:* 1:* NewBinkley ; ; ; Other miscellaneous directives. ; ; AddDomain 51 1 AreaConsultant -R -L -Q PKTtemp d:\temp\ SendAlwaysPKT MinMessages 10000