| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | fido.doc cont... |
PCBSetup
-----------------------------------------------------------------------------
Nearly every option and file location related to the Fido
implementation within PCBoard can be edited from the Fido
Configuration menu on PCBSetup's main menu. Once this option is
selected, several other menu options become available. The following
sections describe each option:
Fido Configuration
------------------
Enable Fido Processing
~~~~~~~~~~~~~~~~~~~~~~
This selection determines whether or not Fido processing is enabled
for the current node. Valid options are:
Y Fido processing is enabled.
N Fido processing is disabled.
Import/Export Configuration File
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The filename entered in this field is the Fido configuration file.
This file stores many of the other options/paths configured in
subsequent Fido screens. The default for this file is a file named
PCBFIDO.CFG in the \PCB\MAIN\ subdirectory.
Name/Location of Fido Queue
~~~~~~~~~~~~~~~~~~~~~~~~~~~
The queue file contains information about what packets to send, when
they will go, and to which site they should be sent. The filename
entered in this field determines the location of this file. When two
or more nodes process Fido packets, it is advisable to insure the
nodes share the same queue file.
Import Immediately After File Transfers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
An efficient way to handle the importing of mail is to disable all
scanning for mail to import (scan every 0 minutes) and enable
importing directly after a file transfer. Once mail has been exchanged
between two sites, any messages waiting for import will be in the
incoming subdirectory on your system. The following are valid
responses:
Y A scan for new mail will occur immediately after the call
takes place. Any messages waiting to be imported are added
to the system at this time. Make sure you disable the
periodic scanning of messages to import as it is pointless
when this switch is enabled.
N PCBoard will not scan for mail to import upon hanging up the
phone. Make sure periodic scanning of mail to import is
enabled (scan every 1 minute or greater) or messages will
never get added to the system.
NOTE: When enabled, this setting forces a node to process mail even
if the node is configured to not allow the processing of
incoming packets.
Allow Node to Process Incoming Packets
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This setting determines if the node will process incoming packets. It
is entirely possible for a setup to exist where the node(s) on your
system will receive the incoming packets to a network drive and then
have a local-only node do all of the processing (importing into the
message bases). The valid settings for this field are:
Y The node will process all incoming packets as per the Scan
for Inbound Packets Frequency field also found on this
screen.
N The node will NOT process incoming packets. Instead, some
other node will have to process or import the messages into
PCBoard's message base files.
Scan for Inbound Packets Frequency (min)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PCBoard scans for incoming Fido packets while at the call-waiting
screen. The value entered in this field determines how many minutes
elapse between each import scan. Please understand that the elapsed
time is only counted while at the call-waiting screen. If a caller
calls in before the time has elapsed, the timer will be reset when the
caller hangs up. For this reason, it is important to set the value in
this field to a small enough value that all mail can be processed. A
setting between 2 and 10 is a good starting point. 2 minutes for the
busier system and 10 for a system which is not quite as busy. Valid
responses are between 1 and 1439.
NOTE: This option is only applicable if the node is configured to
process incoming Fido packets.
Allow Node to Export Mail
~~~~~~~~~~~~~~~~~~~~~~~~~
A good recommendation for exporting Fido mail on your system is to
allow only one node to export. All other nodes should be configured
to NOT export mail. This setting controls whether or not the current
node will build the outbound packets. Valid responses are:
Y This node will export mail posted on the system.
N Mail will not be exported by this node.
Scan for Mail to Export Frequency (min)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This selection is similar to scanning for inbound mail frequency in
that it tells PCBoard how often to scan your Fido conferences for
outbound mail (in minutes). The same recommendations for inbound
frequency settings apply to outbound frequency settings. Valid
responses are between 1 and 1439.
NOTE: The value entered here only has relevance when
the node is configured to export mail.
Allow Node to Dial Out
~~~~~~~~~~~~~~~~~~~~~~
This selection determines whether or not this node will dial out to
send packets or to poll another Fido node. Always make sure at least
one node is configured to dial out. Valid selections are:
Y The node will be able to make calls to poll other nodes or
to send outbound mail.
N This node cannot dial-out.
Scan for Outbound Packets Frequency (min)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If outbound packets exist and the current node is allowed to dial out,
the outbound packets will be sent to another node/hub. The amount of
time which must elapse between each scan for outbound mail is
determined by this field. Remember, only the time spent at the
call-waiting screen counts. If you have the frequency set at every
five minutes and callers are logging in every 3 minutes to your
system, a successful scan will never occur. Use a low enough setting
that mail can be sent as often as you desire.
NOTE: Each time PCBoard dials a system it will only attempt that one
system. This is an important fact to remember especially if
circumstances require multiple sites to be dialed. The next time the
timer triggers, the next system is called.
Default Zone and Net
~~~~~~~~~~~~~~~~~~~~
When used in conjunction with the Default Net field, default values
will be used when entering an address at the Fido menu available from
the call-waiting screen. Using the defaults you may enter just the
node number to poll and PCBoard will fill in the zone and net numbers
with the default values.
The defaults can be overridden simply by including the zone or net
information when polling. Here are some examples based on a default
zone=1 and net=828
You Enter: 5
Site Polled: 1:828/5 (Use default values)
You Enter: 56/6
Site Polled: 1:56/6 (Default net overridden)
You Enter: 2:29/30
Site Polled: 2:29/30 (All defaults overridden)
Security Req'd for +C and +D Modifiers
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When a netmail message is addressed with a on the addressee line,
it becomes what is known as crash mail. Crash mail ignores all event
information which means a message can be sent to any sight regardless
of the settings of the crash Fido verb in the current event.
Entering the flag on a netmail message forces PCBoard to ignore
any routing and instead go directly to the node. With an
international network, this can be a very costly feature if put in the
power of unauthorized individuals.
If you give users access to the netmail conference, set an appropriate
security level to send Crash and Direct mail. It's not hard for a user
to abuse the netmail privileges if you let them.
Fido Logging Level (higher=more detail)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This configuration option controls how detailed the log entries are
for Fido transfers and tossing. The higher the number you enter, the
more detailed the entries in the caller logs will be. The following
list summarizes the valid options for this field:
0 Normal log entries
1 More details for mail transfers
2 More details for tossing
3 More details for mail transfers and tossing
4 Used only for debugging purposes
5 Used only for debugging purposes
NOTE: Because selecting a value higher than 1 results in more
information being logged, be aware that the size of logs on disk will
increase.
Create MSG with Outbound Packets Attached
-----------------------------------------
This option is designed for use with a configuration where PCBoard
will not be the one exporting the packets to other systems. If
PCBoard will be the software used to transfer packets to other
systems, leave this option set to N. Valid options for this field
follow:
Y All outbound packets created by PCBoard are placed as file
attachment to MSG files. Any MSG compatible mailer can then
transfer the mail to the necessary sites. You must simply
tell the third-party mailer that the import/export directory
for MSG files is the directory specified by PCBSetup | Fido
Configuration | File & Directory Information. Make sure the
/MSG switch is not specified in the PCBFIDO environment
variable when this option is selected.
N PCBoard will handle both the exporting of mail and also the
dialing of other systems. This is the default choice.
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
your system.
N All packets sent to your system are imported. In other
words, all routing information is ignored.
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:
Node: Enter the node number to which mail will be sent. The format
for the node number is :/.
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.
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.
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
--------------
On this screen you must enter the Fido address/node number assigned to
you. Remember the format is in the
:/ format. Use
ALT-I to add new fields where AKA (Also Known As) addresses can be
entered.
This selection allows you to tell PCBoard what your Fido system
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
multiple Fido based networks, you'll have more than one node address
and will need the AKAs to properly identify your node.
A question that gets asked quite often revolves around node number
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
answer is that you cannot stop them from entering the number.
However, a password can be defined on the host system to prevent
others from acting as your node number.
Example system addresses follow:
10:125/56
1:583/5
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
change.
EMSI Profile
------------
EMSI could be described as a negotiation protocol for Fido systems.
The information regarding your system name, city, phone number, baud,
etc. are sent during the negotiation sequence.
Normally this information is available in the node list but PCBoard
will gather the information from this screen and use it to override
what is in the nodelist. It is important to enter the information
accurately because some hosts may use it to update node lists. The
following describes each field:
BBS Name : Enter the name of your BBS in this field.
SysOp Name: In this field, enter the name of the SysOp in the first
name / last name format.
City/State: Enter the city and state / province information where your
BBS operates.
Phone : Enter the phone number used for incoming Fido calls. Make
sure you do not list your general BBS number if it is different from
the Fido number.
Baud: Enter the maximum baud rate your system supports. In FidoNet,
9600 is generally considered to be a maximum value. What you enter
here has no effect on what speed you call other systems; it is for
informational purposes only.
Flags : Ask your node coordinator what should be entered in the flags
field. If in doubt, leave the default values.
cont...
* Origin: (1:226/600)SEEN-BY: 10/1 3 14/300 400 34/999 90/1 120/228 123/500 132/500 134/10 140/1 SEEN-BY: 222/2 226/0 229/4000 236/150 249/303 261/20 38 100 1381 1404 1406 SEEN-BY: 261/1410 1418 266/1413 280/1027 320/119 633/104 260 262 267 712/848 SEEN-BY: 800/432 801/161 189 2222/700 2905/0 @PATH: 226/600 123/500 261/38 633/260 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.