********************************************************************** * * * Nodelist entries in the nodelist must use one of the following * * keywords to be accepted: * * * * ZONE .......... Signifies a Zone Coordinator. * * * * REGION ........ Signifies a Regional Coordinator. * * * * HOST .......... Signifies a NET Host. NETs must be sanctioned * * by the Regional Coordinator in their geographic * * * location. * * * * PVT ........... Signifies a private node that does not have a * * listed phone number or is calling outside of their * * geographic area. * * * * DOWN .......... Signifies that the listed node is down and not * * able to send or receive mail. * * * * Nodelist entries should be formatted as follows: * * * * ,NODE NUMBER,SYSTEM NAME,LOCATION,SYSOP NAME,SYSTEM PHONE NUMBER, * * MAX BAUD RATE,MODEM PROTOCOL FLAGS,MAILER FLAGS * * * ********************************************************************** ********************************************************************** * * * The following flags define special operating conditions: * * * * Mail Processing Flags * * --------------------- * * * * Flag Meaning * * ---- ------- * * * * CM ...... Crash Mail. Node accepts mail 24 hours a day. * * MO ...... Mail Only. Node does not accept human callers. * * LO ...... Accepts calls from listed nodes only. * * * * Mailer Type * * ----------- * * * * XA ............ Bark and WaZOO file/update requests * * XB ............ Bark file/update requests, WaZOO file requests * * XC ............ Bark file requests, WaZOO file/update requests * * XP ............ Bark file/update requests * * XR ............ Bark and WaZOO file requests * * XX ............ WaZoo file/update requests * * * * The following flags define the type(s) of compression of mail * * packets supported. * * * * Flag Meaning * * ---- ------- * * * * MN No mail packet compression supported * * * * NOTE: The only compression method standard in * * FidoNet is archiving, using the standard SEA ARC * * format, with archive names defined by the * * specification for ARCMail 0.6. The absence of the * * MN flag indicates that ARCMail 0.6 compression is * * supported by this node. * * * ********************************************************************** ********************************************************************** * * * The following flags define modem capabilities supported: * * * * Protocol Flag Meaning * * ------------- ------- * * * * V21................... CCITT V21 300BPS FULL DUPLEX * * V22................... CCITT V22 1200BPS FULL DUPLEX * * V29................... CCITT V29 9600BPS HALF DUPLEX * * V32................... CCITT V32 9600BPS FULL DUPLEX * * V32B.................. CCITT V32bis 14400 FULL DUPLEX * * V33................... CCITT V33 * * V34................... CCITT V34 * * V42................... CCITT V42 * * V42B.................. CCITT V42bis COMPRESSION * * H96................... HAYES V9600 * * HST................... USR COURIER HST 9600 * * H14................... USR COURIER HST 14400 * * H16................... USR COURIER HST 16800 * * MAX................... MICROCOM AX/96xx SERIES * * PEP................... PACKET ENSEMBLE PROTOCOL * * MNP................... MICROCOM COMPRESSION * * CSP................... COMPUCOM SPEEDMODEM * * * * NOTE: Many V22 modems also support Bell 212A. * * * * If no modem flag is given, Bell 212A is assumed for 1200 bps * * systems, CCITT V22bis is assumed for 2400 bps systems. * * * * A separate modem capability flag should not be used when it can be * * determined by the modem flag. For instance, a modem flag of HST * * implies MNP. V32b implies V32 and V42b implies V42. MNP,HST and * * V32,V32b and V42,V42b flag pairs are unnecessary. * * * ********************************************************************** **************************************************** * * * The following flags indicate the types of * * file/update requests supported. * * * **************************************************** * * Bark * WaZOO * * ********************************************* * * File * Update * File * Update * * Flag * Requests * Requests * Requests * Requests * **************************************************** * XA * Yes * Yes * Yes * Yes * * XB * Yes * Yes * Yes * No * * XC * Yes * No * Yes * Yes * * XP * Yes * Yes * No * No * * XR * Yes * No * Yes * No * * XW * No * No * Yes * No * * XX * No * No * Yes * Yes * **************************************************** ****************************************** * The following software is qualified to * * use the appropriate file request flag * * according to information provided by * * developers: * * * ****************************************** * Flag Software Package * ************************************* * XA Frontdoor 1.99b and lower * * Frontdoor 2.01 and higher * * Dutchie 2.90c * * Binkleyterm 2.1 and higher * * D'Bridge 1.2 and lower * * TIMS * ************************************* * XB Binkleyterm 2.0 * * Dutchie 2.90b * ************************************* * XC Opus 1.1 * ************************************* * XP Seadog * ************************************* * XR Opus 1.03 * ************************************* * XW Fido 12N and higher * * Tabby * ************************************* * XX D'Bridge 1.30 and higher * * Frontdoor 1.99c/2.00 * * InterMail 2.01 * ************************************* * None QMM * *************************************