home *** CD-ROM | disk | FTP | other *** search
- ; TOSS'in for FTP'in v1.50
- ; Sample Configuration File
- ;
- ; General Format. Semi-Colons in the first column of a line cause that
- ; line to be ignored during processing. This is so you can have
- ; comments in your config file.
- ;
- ; Keywords. These are words that have special meaning to the program.
- ; They must be the left most thing on a line and they must have a colon
- ; after them.
- ;
- ; Blank lines are ignored.
- ;
- ; Case is insensitive.
- ;
- ; Currently, there can be no spaces between a keyword and it's data.
- ;
- ; ┌──────────────────────────────────────────────────────────────────────┐
- ; │ OWNER: = Your full name goes here. Remember, no spaces after the │
- ; │ colon (:). │
- ; └──────────────────────────────────────────────────────────────────────┘
-
- OWNER:Lyn Borchert
-
- ; ┌──────────────────────────────────────────────────────────────────────┐
- ; │ SERIAL#: = Your serial number goes here. If you haven't registered│
- ; │ yet then make sure there are zeros here to run in evaluation mode. │
- ; └──────────────────────────────────────────────────────────────────────┘
-
- SERIAL#:000000
-
- ; ┌──────────────────────────────────────────────────────────────────────┐
- ; │ OUTBOUND: = The full drive and path to a temporary directory where │
- ; │ you place all your outgoing files for uploading to the Internet │
- ; │ provider. This is where TOSSFTP will create it's *.PKT files. │
- ; └──────────────────────────────────────────────────────────────────────┘
-
- OUTBOUND:C:\internet\outbound
-
- ; ┌─────────────────────────────────────────────────────────────────────────┐
- ; │ NETMAIL: = This is the full drive and path where your *.msg Netmail │
- ; │ files are kept. TOSSFTP scans this direcory for any messages destine │
- ; │ for your uplink and turns them into *.PKT files in the OUTBOUND path. │
- ; │ It will also move the bundles of file attach messages to the OUTBOUND │
- ; │ directory and truncate the file in the original path just like your │
- ; │ mailer would do after a successful send of this bundle. Bundles have │
- ; │ specail file names that end in MO1, TU1, WE1, etc.. depending on what │
- ; │ day of the week it was created. All netmail messages that TOSSFTP │
- ; │ processes are deleted after processing. │
- ; └─────────────────────────────────────────────────────────────────────────┘
-
- NETMAIL:C:\fd\mail
-
- ; ┌─────────────────────────────────────────────────────────────────────────┐
- ; │ PACKETS: = This is the full drive and path to where your echomail │
- ; │ processor places the *.MO1 files. It is used to determine if a file │
- ; │ attach message is valid. In other words, when TOSSFTP comes across a │
- ; │ netmail message that is destine for the uplink and does not have │
- ; │ either the AREAMGR or FILEMGR name in the TO field, it then looks at │
- ; │ the subject line to see if it contains the PACKETS path. If it does, │
- ; │ then the file listed on the subject line is copied to the OUTBOUND │
- ; │ directory, then the original is truncated, and finally, the .msg is │
- ; │ deleted. │
- ; └─────────────────────────────────────────────────────────────────────────┘
-
- PACKETS:C:\fd\packet
-
- ; ┌──────────────────────────────────────────────────────────────────────────┐
- ; │ AREAMGR: = This is the name you have told your areafix program to │
- ; │ send requests to link into echos. It must match or TOSSFTP will not │
- ; │ find and process your outgoing areafix messages to your uplink. │
- ; └──────────────────────────────────────────────────────────────────────────┘
-
- AREAMGR:Areafix
-
- ; ┌──────────────────────────────────────────────────────────────────────────┐
- ; │ FILEMGR: = This is just like AREAMGR except for your file echo │
- ; │ processor. │
- ; └──────────────────────────────────────────────────────────────────────────┘
-
- FILEMGR:Raid
-
- ; ┌──────────────────────────────────────────────────────────────────────────┐
- ; │ ZONE: = Put your Zone Number here. │
- ; └──────────────────────────────────────────────────────────────────────────┘
-
- ZONE:1
-
- ; ┌──────────────────────────────────────────────────────────────────────────┐
- ; │ NET: = Put your Net Number Here. │
- ; └──────────────────────────────────────────────────────────────────────────┘
-
- NET:300
-
- ; ┌──────────────────────────────────────────────────────────────────────────┐
- ; │ NODE: = Put your Node Number Here. │
- ; └──────────────────────────────────────────────────────────────────────────┘
-
- NODE:1
-
- ; ┌──────────────────────────────────────────────────────────────────────────┐
- ; │ DEST: = Put the Full Zone:Net/Node number of your uplink system here. │
- ; └──────────────────────────────────────────────────────────────────────────┘
-
- DEST:1:300/102
-
- ; ┌──────────────────────────────────────────────────────────────────────────┐
- ; │ DEBUG: = If ON, lots of extra info will print to the log and screen. │
- ; │ This is to help find routing logic problems and should │
- ; │ be OFF for normal operations or your log file will get very │
- ; │ large very fast! │
- ; └──────────────────────────────────────────────────────────────────────────┘
-
- DEBUG:OFF
-
- ; ┌──────────────────────────────────────────────────────────────────────────┐
- ; │ DELETE: = If ON, TOSSFTP will clean up after itself by deleting all │
- ; │ routed Netmail messages that it packetizes. If OFF, TOSSFTP │
- ; │ will NOT delete tossed *.msg files but instead will just set │
- ; │ the SENT flag to be ON. (default setting is ON) │
- ; └──────────────────────────────────────────────────────────────────────────┘
-
- DELETE:OFF
-
-
- LOGFILE:TOSSFTP.LOG
-
-
- ; ┌──────────────────────────────────────────────────────────────────────────┐
- ; │ NOROUTE: = This is a special Keyword to deal with Host Routed │
- ; │ Net Mail. What makes this keyword special, is it MUST be the last │
- ; │ keyword in the config file, it can have multiple arguements, and the │
- ; │ arguements are not on the same line as the keyword. Every line after │
- ; │ the NOROUTE keyword is treated as a system that you do NOT wish to │
- ; │ route mail to. You can use the * character to represent ALL. For │
- ; │ example, 1:300/* would mean do NOT host route any mail that is │
- ; │ destine to any node in zone 1 net 300. You MUST use a Zone number! │
- ; │ If you were to put 300/*, TOSSFTP would misinterpret your meaning. │
- ; │ Currently, the Zone number is nothing more than a place holder. *.msg │
- ; │ files don't have a zone number in them that I have found as yet. │
- ; │ │
- ; │ There are some other things the TOSSFTP checks for before allowing a │
- ; │ message to be considered a host routed message. The IN TRANSIT flag │
- ; │ must be turned on, the HOLD Flag must NOT be turned on, the SENT flag │
- ; │ must NOT be turned on, and the FrontDoor DIRECT kludge must NOT be │
- ; │ present. (In the FD Message Editor, this looks like just another │
- ; │ flag, but in fact, FD places a Kludge line in the message body to │
- ; │ denote when a message is to be sent Direct. There is no DIRECT flag │
- ; │ in the message headers. After meeting all those conditions, TOSSFTP │
- ; │ then checks the destination against the NOROUTE lines here. │
- ; │ │
- ; │ In most cases you will put your zone:net/* under the NOROUTE keyword │
- ; │ and any systems you communicate with via netmail that are not in │
- ; │ your zone. Here-in lies a problem. If you send netmail to a node │
- ; │ in another zone who has the same net/node number as someone else you │
- ; │ send mail to in your zone TOSSFTP cannot resolve that issue. │
- ; │ Example: mail to 1:300/12 and 2:300/12 are the same address to │
- ; │ TOSSFTP since it is virtually Zone Dumb. Since 1:300/* is in the │
- ; │ NOROUTE section, TOSSFTP will not route mail to 2:300/12 or │
- ; │ 1:300/12. │
- ; │ │
- ; └──────────────────────────────────────────────────────────────────────────┘
-
- NOROUTE:
- 1:300/*
- 1:138/146
- 1:355/*
- 1:105/341
-
-