Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
fido:start [2024/03/18 13:04] – 2003:e4:df3b:aa00:eda5:d4ee:4d1f:72ec | fido: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/ | + | ===== Fido Menu Options/ |
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 | + | |
- | | **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", | **1.** Starting with "Fido Configuration", | ||
Line 236: | Line 236: | ||
done with the following entry: | done with the following entry: | ||
- | Find Change To | + | |
- | | + | |
1) 1-801- | 1) 1-801- | ||
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 308: | Line 308: | ||
Status : Processing nodelist file: C: | Status : Processing nodelist file: C: | ||
Message: Processing Net: 1:251 | Message: Processing Net: 1:251 | ||
- | % Done : ÛÛÛÛÛÛÛ°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° | + | % Done : ███████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ |
This process will take several minutes to complete. | This process will take several minutes to complete. | ||
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/ | **1.** Change the name/ | ||
Line 391: | Line 391: | ||
referred to as the tag for the area. | referred to as the tag for the area. | ||
- | === " | + | ==== " |
**1.** Change the name/ | **1.** Change the name/ | ||
Line 409: | Line 409: | ||
the message to the coordinator. | the message to the coordinator. | ||
- | ==== Sending the Netmail Message ==== | + | ===== Sending the Netmail Message |
Congratulations! | Congratulations! | ||
Line 498: | Line 498: | ||
is honored/ | is honored/ | ||
- | ==== Configuring Zone Mail Hour ==== | + | ===== Configuring Zone Mail Hour ===== |
Now that the mail has been sent to the coordinator, | Now that the mail has been sent to the coordinator, | ||
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. | Normally, netmail is sent directly from one site to another. | ||
Line 568: | Line 568: | ||
column brings up a list of valid Fido verbs. | column brings up a list of valid Fido verbs. | ||
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
Cursor down to " | Cursor down to " | ||
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 |
- | 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. | ||
- | 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 " | ||
- | usually only required by hubs. Valid options for this field are: | ||
- | Y | + | The purpose of this option is to control whether inbound routing is |
- | your system. | + | enabled. |
+ | can be transferred to your system | ||
+ | transfer | ||
+ | operates in a " | ||
+ | usually only required by hubs. Valid options for this field are: | ||
- | | + | | **Y** | Packets can be routed from one system to another through your system. | |
- | | + | | **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. | ||
- | 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: | ||
- | Node: Enter the node number to which mail will be sent. | + | When this menu option is selected, an editor screen is displayed where |
- | for the node number is < | + | nodes receiving outbound packets can be configured. |
+ | 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. | ||
- | Arc: Enter the archive type to be used for the node being defined. | + | The fields on this screen |
- | Valid entries | + | |
- | 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 | + | |
- | | + | | **Node:** | Enter the node number to which mail will be sent. The format for the node number is < |
- | | + | | **Arc: |
- | | + | | **Pkt:** | PCBoard' |
- | | + | |
- | | + | **NOTE:** The default settings for every site are to use ZIP compression |
- | and Type 2+ packets. | + | and Type 2+ packets. |
- | these values, an entry does not need to be made. Only add an entry | + | these values, an entry does not need to be made. Only add an entry |
- | when you must override the default values. | + | when you must override the default values. |
==== System Address ==== | ==== System Address ==== | ||
- | -------------- | ||
- | | + | On this screen you must enter the Fido address/ |
- | you. Remember the format is in the < | + | you. Remember the format is in the < |
- | 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 |
- | address in the standard form of zone: | + | address in the standard form of zone: |
- | entries to allow for AKA' | + | entries to allow for AKA' |
- | 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 |
- | security. | + | security. |
- | 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: |
- | | + | |
- | 1:583/5 | + | 1:583/5 |
- | 6:5/82 | + | 6:5/82 |
- | | + | 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 | 1) BOBOB | ||
- | | + | 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=" | ==== "SET PCBFIDO=" | ||
- | | + | This is actually a newly supported environment variable. |
- | 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). | + | opposite of the /NOFIDO switch). |
- | 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 |
- | two new command line parameters. | + | two new command line parameters. |
- | 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 |
- | node acts as a hub to the point. | + | node acts as a hub to the point. |
- | get a better picture as to what is going on: | + | get a better picture as to what is going on: |
+-------+ | +-------+ | ||
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 | + | directory (PCBSetup |
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 | + | setting in PCBSetup |
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. | | ||