Joining Fidonet and Net275

Procedure to apply for FidoNet Node number
==========================================

  1. Get your BBS software up and running. You may need to obtain an echomail "scanner/tosser" specific to your BBS software, that will allow it to interface with a FidoNet style of mail import and export.

  2. Get your mailer software working. You will need to thoroughly read your mailer docs, as this is by far the most important step to getting your system online in the Network. Currently, the most popular mailers are FrontDoor and BinkleyTerm, though there are others as well. You may also need to get a "nodelist compiler" Test your system thoroughly before submitting your application. New nodes are to use the 1:275/999 address as their primary address until assigned a permanent one by the NC. Exception is systems who are currently operational as 'point-operators' or existing addresses from other fidonet networks, may continue with their current address as their primary, but must add 1:275/999 as an 'aka' presented on connection until a new permanent nodenumber is assigned.

  3. Download the latest nodelist from any FidoNet BBS, though it is usually best to call your local Net's Network CoOrdinator (NC) since s/he will have the latest compiled listing. The filename for the nodelist is usually NODELIST.xxx, where xxx is the number of the day of the year. It may however be named NODELIST.ZIP and contain the current week's version.

  4. The FidoNet Host Net for the Southside Tidewater area (Chesapeake, Norfolk, Portsmouth, Virginia Beach, and Suffolk) is FidoNet 275. Using the temporary applicant's node number 1:275/999, send a netmail message to 275/0, the SE Virginia Net Coordinator (Internet only sites see notes below). 275/0 can accept mail anytime. The file called APPLY.275 is the appropriate information needed by the Net Coordinator to assign you a Fido address. Please use a text editor to view and add the information to this file.

  5. Once it's completed, rename the application to your LAST name with an extension of .APP. Also send me a quick note letting me know that this file is on my system so I can process it. Example of naming is this. If your name was John Doe, name the file that you are sending me to DOE.APP.

  6. Your node address will be sent, within seven days, via netmail. If your system is CM (Continuous Mail) it will go out immediately. If running limited hours, your node number will be sent during ZMH. See the Policy4.txt document included in the FIDO_275 file regarding the ZMH (Zone Mail Hour).

  7. Requests that are in by Tuesday will normally be forwarded for inclusion on that Friday's nodelist.

    It is recommended that you carry SYSOP_275. It serves, in addition to netmail, as a common link between the Net sysops and as the area used for official announcements and discussions. Use of an ALIAS is discouraged in this echo. This echo is is not for cross-linking with or passing on to Sysops outside of our own net.

  8. If you need help with this process during any phase, feel free to contact Mark Hoover, the current Net275 CoOrdinator (the "NC") via his System at 1:275/0 for OFFICIAL net business or 1:275/103 for other NETMAIL. This will require that your system has a compiled nodelist.

  9. You are invited to join other sysops in a monthly brunch social held normally the 2nd Saturday of each month. The socials are advertised in the SYSOP_275 echo and the LCHATTER conferences.

  10. It will be your responsibility to see that your Nodelist entry is kept current. Notify your HUB and your NC if your system will be DOWN for more than 24 hours. Note that all systems found to be "out of service" will be marked DOWN in the Nodelist for 2 weeks and removed automatically on the 3rd week. Again, it is YOUR responsibility to make the proper notifications. It is understood that there are a great many military personnel in our Net, which means a more than normal amount of time away from the computer. If you are going to be deployed or otherwise unable to monitor your system and intend to keep it "up" while gone, please make arrangements with someone to keep an eye on it for you. Information about your absence will be kept confidential for the obvious reasons. If you are unable to find a person to maintain your system under such circumstances, contact the NC to ensure your nodelist entry is maintained should your system 'crash' for an extended time while you are away. Net_275 policy is to maintain a nodelist entry for such special circumstances for as long as 8 months.

  11. Passthru mail for any system (including PVT) will be kept for 48 hours. If for any reason you can not receive or POLL for your mail, it is your responsibility to make the necessary arrangements with the proper parties, ie: HUB, NEC/NFC, NC, etc.

  12. It will be assumed that by submitting an application, you have read and agree to abide by FidoNet Policy4.txt and this document.

Additional Notes From The Net Coordinator
========================================

Please do not request membership in the Net until your system is actually online and has been tested locally. You may do this by using the temporary node address of 1:275/999. Once you think all is well, send me a netmail at 1:275/0 and we will work from there.

Sites who are FTP or IP only, may apply via email to mahoover@ispaceonline.org and we will work out arrangements for netmail testing from there. The minimum requirement of being able to send/recieve netmail still applies but the transport method of that netmail may be via internet protocol. Such nodes will be listed in compliance with the 5000 series of FTSC nodelisting methodology.

FidoNet Net 275
Maintained By: Mark A. Hoover (mahoover@ispaceonline.org)