≪ View Page

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
fido:start [2024-03-18 13:09] – 2003:e4:df3b:aa00:eda5:d4ee:4d1f:72ecfido:start [2024-03-18 13:35] (current) – 2003:e4:df3b:aa00:eda5:d4ee:4d1f:72ec
Line 148: Line 148:
 the nodelist was obtained from as this is vital information. the nodelist was obtained from as this is vital information.
  
-===== 4. Configure PCBoard to Send netmail =====+====== Configure PCBoard to Send netmail ======
  
 Before configuring PCBoard to send netmail, make sure you have the Before configuring PCBoard to send netmail, make sure you have the
Line 156: Line 156:
   * Fido address of the net coordinator   * Fido address of the net coordinator
  
-==== Fido Menu Options/Settings ====+===== Fido Menu Options/Settings =====
  
 Our next step is to configure the bare essentials of Fido so we can Our next step is to configure the bare essentials of Fido so we can
Line 163: Line 163:
 menu options: menu options:
  
-| **A** | Fido Configuration | +    A Fido Configuration 
-| **B** | Node Configuration | +    B Node Configuration 
-| **C** | System Address | +    C System Address 
-| **D** | EMSI Profile | +    D EMSI Profile 
-| **E** | File & Directory Configuration | +    E File & Directory Configuration 
-| **F** | Archiver Configuration | +    F Archiver Configuration 
-| **G** | Phone Number Translation | +    G Phone Number Translation 
-| **H** | Nodelist Configuration | +    H Nodelist Configuration 
-| **I** | FREQ Path List | +    I FREQ Path List 
-| **J** | FREQ Restrictions | +    J FREQ Restrictions 
-| **K** | FREQ Magic Names | +    K FREQ Magic Names 
-| **L** | FREQ Deny Nodelist |+    L FREQ Deny Nodelist
  
 **1.** Starting with "Fido Configuration", the first menu option, mark each of the following fields with a "Y": **1.** Starting with "Fido Configuration", the first menu option, mark each of the following fields with a "Y":
Line 264: Line 264:
 the Fido Main Menu. the Fido Main Menu.
  
-==== Compiling the Node List ====+===== Compiling the Node List =====
  
 With each Fido site being referred to by a bunch of numbers, we need With each Fido site being referred to by a bunch of numbers, we need
Line 314: Line 314:
 screen. screen.
  
-==== Adding a User Record for the Coordinator / Host ====+===== Adding a User Record for the Coordinator / Host =====
  
 PCBFido keeps track of information about other sites you exchange mail PCBFido keeps track of information about other sites you exchange mail
Line 354: Line 354:
 the network, you will probably have a session password assigned the network, you will probably have a session password assigned
  
-==== Creating the Netmail Conferences ====+===== Creating the Netmail Conferences =====
          
 The final setup step for sending netmail is to setup the netmail The final setup step for sending netmail is to setup the netmail
Line 379: Line 379:
 being cloned. being cloned.
  
-=== "Bad Mail" (Conference 100) ===+==== "Bad Mail" (Conference 100) ====
  
 **1.** Change the name/location of the message base to P:\PCB\FIDO\BADMSGS or whatever is appropriate for your system. **1.** Change the name/location of the message base to P:\PCB\FIDO\BADMSGS or whatever is appropriate for your system.
Line 391: Line 391:
 referred to as the tag for the area. referred to as the tag for the area.
  
-=== "Netmail" (Conference 101) ===+==== "Netmail" (Conference 101) ====
  
 **1.** Change the name/location of the message base to ..\FIDO\NETMAIL or whatever is appropriate for your system. **1.** Change the name/location of the message base to ..\FIDO\NETMAIL or whatever is appropriate for your system.
Line 409: Line 409:
 the message to the coordinator. the message to the coordinator.
  
-==== Sending the Netmail Message ====+===== Sending the Netmail Message =====
  
 Congratulations!  The hard part of the configuration has been done. Congratulations!  The hard part of the configuration has been done.
Line 498: Line 498:
 is honored/configured on the system. is honored/configured on the system.
  
-==== Configuring Zone Mail Hour ====+===== Configuring Zone Mail Hour =====
  
 Now that the mail has been sent to the coordinator, zone mail hour must Now that the mail has been sent to the coordinator, zone mail hour must
Line 534: Line 534:
 patient. patient.
  
-==== Routing Mail to Your Hub ====+===== Routing Mail to Your Hub =====
  
 Normally, netmail is sent directly from one site to another.  While this Normally, netmail is sent directly from one site to another.  While this
Line 638: Line 638:
 Congratulations on a job well done. Congratulations on a job well done.
  
-==== Setting Up Echo Mail Areas ====+===== Setting Up Echo Mail Areas =====
  
-    The procedure for adding the conferences for Fido echo areas include the +The procedure for adding the conferences for Fido echo areas include the 
-    following steps:+following steps:
  
   - Get a FIDONET.NA file from your coordinator.   - Get a FIDONET.NA file from your coordinator.
Line 781: Line 781:
 appropriate tag information. appropriate tag information.
  
-==== What AreaFix Is and How to Use It ====+===== What AreaFix Is and How to Use It =====
  
 AreaFix is a function of hubs allowing you to subscribe and unsubscribe AreaFix is a function of hubs allowing you to subscribe and unsubscribe
Line 847: Line 847:
 nothing you can do with AreaFix requests that will cause damage. nothing you can do with AreaFix requests that will cause damage.
  
-==== Setting Up The Archivers ====+===== Setting Up The Archivers =====
  
 In our initial steps to get netmail working we skipped over a few of the In our initial steps to get netmail working we skipped over a few of the
Line 1332: Line 1332:
  
 ==== Enable Inbound Routing ==== ==== Enable Inbound Routing ====
-  ---------------------- 
-      The purpose of this option is to control whether inbound routing is 
-      enabled.  With inbound routing enabled, a packet for another system 
-      can be transferred to your system and held in your outbound queue for 
-      transfer to another site.  In this type of configuration the system 
-      operates in a "middle-man" type role.  This type of functionality is 
-      usually only required by hubs.  Valid options for this field are: 
  
-        Y       Packets can be routed from one system to another through +The purpose of this option is to control whether inbound routing is 
-                your system.+enabled.  With inbound routing enabled, a packet for another system 
 +can be transferred to your system and held in your outbound queue for 
 +transfer to another site.  In this type of configuration the system 
 +operates in a "middle-man" type role.  This type of functionality is 
 +usually only required by hubs.  Valid options for this field are:
  
-        N       All packets sent to your system are imported. In other +| **Y** | Packets can be routed from one system to another through your system. | 
-                words, all routing information is ignored.+| **N** | All packets sent to your system are imported. In other words, all routing information is ignored. |
  
 ==== Node Configuration ==== ==== Node Configuration ====
-  ------------------ 
-      When this menu option is selected, an editor screen is displayed where 
-      nodes receiving outbound packets can be configured.  In other words, 
-      this screen will list all nodes who will receive mail from your 
-      system, what type of archiver they use, and what type of packet to 
-      create. 
  
-      The fields on this screen are as follows:+When this menu option is selected, an editor screen is displayed where 
 +nodes receiving outbound packets can be configured.  In other words, 
 +this screen will list all nodes who will receive mail from your 
 +system, what type of archiver they use, and what type of packet to 
 +create.
  
-      Node: Enter the node number to which mail will be sent.  The format +The fields on this screen are as follows:
-      for the node number is <zone>:<net>/<node>.+
  
-      Arc: Enter the archive type to be used for the node being defined. +| **Node:** | Enter the node number to which mail will be sent.  The format for the node number is <zone>:<net>/<node>. | 
-      Valid entries are 0-3: 0=ZIP, 1=ARJ, 2=ARC, and 3=LZH.  Make sure  the +| **Arc:**  | Enter the archive type to be used for the node being defined. Valid entries are 0-3: 0=ZIP, 1=ARJ, 2=ARC, and 3=LZH.  Make sure  the proper entries are made in PCBSetup > Fido Configuration > Archive Configuration for each type.  If you are unsure of the type to enter, contact the SysOp of the node for the proper  setting. | 
-      proper entries are made in PCBSetup | Fido Configuration | Archive +| **Pkt:**  | PCBoard's implementation of Fido supports two type of packets: 1) Stone Age (type 1) and 2) Type 2+.  Select the appropriate type  for the node being defined.  If unsure of which selection to make, contact the SysOp of the node in question to get the proper setting. |
-      Configuration for each type.  If you are unsure of the type to enter, +
-      contact the SysOp of the node for the proper  setting.+
  
-      Pkt: PCBoard's implementation of Fido supports two type of packets: 1) +**NOTE:** The default settings for every site are to use ZIP compression 
-      Stone Age (type 1) and 2) Type 2+.  Select the appropriate type  for +and Type 2+ packets.  If the site you are exchanging mail with uses 
-      the node being defined.  If unsure of which selection to make, contact +these values, an entry does not need to be made.  Only add an entry 
-      the SysOp of the node in question to get the proper setting. +when you must override the default values.
- +
-      NOTE:  The default settings for every site are to use ZIP compression +
-      and Type 2+ packets.  If the site you are exchanging mail with uses +
-      these values, an entry does not need to be made.  Only add an entry +
-      when you must override the default values.+
  
 ==== System Address ==== ==== System Address ====
-  -------------- 
  
-      On this screen you must enter the Fido address/node number assigned to +On this screen you must enter the Fido address/node number assigned to 
-      you.  Remember the format is in the <zone>:<net>/<node> format. Use +you.  Remember the format is in the <zone>:<net>/<node> format. Use 
-      ALT-I to add new fields where AKA (Also Known As) addresses can be +ALT-I to add new fields where AKA (Also Known As) addresses can be 
-      entered.+entered.
  
-      This selection allows you to tell PCBoard what your Fido system +This selection allows you to tell PCBoard what your Fido system 
-      address in the standard form of zone:net/node. You can make several +address in the standard form of zone:net/node. You can make several 
-      entries to allow for AKA's.  Why use AKAs?  If you are involved with +entries to allow for AKA's.  Why use AKAs?  If you are involved with 
-      multiple Fido based networks, you'll have more than one node address +multiple Fido based networks, you'll have more than one node address 
-      and will need the AKAs to properly identify your node.+and will need the AKAs to properly identify your node.
  
-      A question that gets asked quite often revolves around node number +A question that gets asked quite often revolves around node number 
-      security.  If you can enter any node number, how can you stop someone +security.  If you can enter any node number, how can you stop someone 
-      from enter your assigned node number and picking up your mail?  The +from enter your assigned node number and picking up your mail?  The 
-      answer is that you cannot stop them from entering the number. +answer is that you cannot stop them from entering the number. 
-      However, a password can be defined on the host system to prevent +However, a password can be defined on the host system to prevent 
-      others from acting as your node number.+others from acting as your node number.
  
-      Example system addresses follow:+Example system addresses follow:
  
-        10:125/56 +    10:125/56 
-        1:583/5 +    1:583/5 
-        6:5/82+    6:5/82
  
-      NOTE:  If running more than one mail network, see The Fido Conference +NOTE:  If running more than one mail network, see The Fido Conference 
-      Configuration Screen section for additional fields you may want to +Configuration Screen section for additional fields you may want to 
-      change.+change.
  
 ==== EMSI Profile ==== ==== EMSI Profile ====
Line 1706: Line 1692:
     1) BOBOB                 C:\PCB\FILES\BOBOB-?.ZIP     1) BOBOB                 C:\PCB\FILES\BOBOB-?.ZIP
  
-      Notice how the ? DOS wildcard character is used to make sure all 3 +Notice how the ? DOS wildcard character is used to make sure all 3 
-      disks are included when BOBOB is requested.+disks are included when BOBOB is requested.
  
 ==== FREQ Deny Nodelist ==== ==== FREQ Deny Nodelist ====
Line 1984: Line 1970:
 ==== "SET PCBFIDO=" Environment Switches ==== ==== "SET PCBFIDO=" Environment Switches ====
  
-      This is actually a newly supported environment variable.  The +This is actually a newly supported environment variable.  The 
-      existence of the variable will enable Fido Processing (just the +existence of the variable will enable Fido Processing (just the 
-      opposite of the /NOFIDO switch).  This new variable supports the +opposite of the /NOFIDO switch).  This new variable supports the 
-      following switches:+following switches:
  
 === /MSG === === /MSG ===
Line 2021: Line 2007:
 ==== Command Line Parameters ==== ==== Command Line Parameters ====
  
-      To better facilitate manual processing of Fido mail, PCBoard accepts +To better facilitate manual processing of Fido mail, PCBoard accepts 
-      two new command line parameters.  When used, PCBoard will +two new command line parameters.  When used, PCBoard will 
-      automatically import or export mail.+automatically import or export mail.
  
 === /IMPORT === === /IMPORT ===
Line 2046: Line 2032:
  
 ===== Point Support ===== ===== Point Support =====
-    A point can be best described as a extension to a node.  In fact, the +A point can be best described as a extension to a node.  In fact, the 
-    node acts as a hub to the point.  Look at the following illustration to +node acts as a hub to the point.  Look at the following illustration to 
-    get a better picture as to what is going on:+get a better picture as to what is going on:
  
     +-------+        +------+ ----> Point     +-------+        +------+ ----> Point
Line 2082: Line 2068:
 How does PCBoard import the messages if it never makes the call?  To How does PCBoard import the messages if it never makes the call?  To
 add mail to your system, PCBoard will simply scan the inbound packet add mail to your system, PCBoard will simply scan the inbound packet
-directory (PCBSetup | Fido Configuration | File and Directory+directory (PCBSetup > Fido Configuration > File and Directory
 Configuration). Configuration).
  
Line 2089: Line 2075:
 importing is either to use the /IMPORT command line switch or to importing is either to use the /IMPORT command line switch or to
 periodically scan the inbound directory every x minutes with the periodically scan the inbound directory every x minutes with the
-setting in PCBSetup | Fido Configuration | Fido Configuration.+setting in PCBSetup > Fido Configuration > Fido Configuration.
  
 Because satellites offer just the delivery of messages, you must make Because satellites offer just the delivery of messages, you must make
Line 2096: Line 2082:
 requires: requires:
  
-| **1) | Make a user record for the outbound site. |+| **1)** | Make a user record for the outbound site. |
 | **2)** | Add RS conference flags for every area you send to the outbound site. Otherwise, new mail will not be packetized for export. | | **2)** | Add RS conference flags for every area you send to the outbound site. Otherwise, new mail will not be packetized for export. |