(Continued from previous message)
 
FILEECHO/TIC SETTINGS
---------------------
 
In this screen, basic parameters relating to the filecho/TIC subsystem are
defined here:
 
FILEFIX SYSTEM ON/OFF:
 
D'Bridge automates Echomail management with a subsystem called AREAFIX. So
it makes sense that fileecho/TIC areas be managed with a simular system, and
that is called FILEFIX. Answer YES if you wish to accept FILEFIX requests
or answer NO to shut this feature off.
 
NOTE: D'Bridge responds to FILEFIX requests from FileFix, FileMgr and Allfix
      keywords. Those three are usually the most "common names" in Fidonet.
 
FILEFIX USES AREAFIX:
 
Answer YES if you wish to merely use the exact same passwords and group/
security access defined in the PACKET/MAIL CONTROL screen. Note that any
defined forwarding-information files defined in that screen will NOT be
applicable here; so only answer yes if you are the main "Hub" for your
network or you carry an entire fileecho feed from your uplink.
 
FILEFIX Information: 1:229/426 PASSWORD A,501 Normal Yes Yes AREAS426.BBS
 
This window controls the FILEFIX subsystem, allowing automated area
list and ECHOmail distribution management. For each system, specify:
 
   
  
 
Where:
 
 is the address of the system in the form ZONE:NET/NODE.POINT
 
 is a codeword agreed upon by both systems (you and the system
specified) for FILEFIX. The password may be from 1 to 32 characters.
 
 contains the groups allowed and security level assigned to
the system. ie. ABC,501 allows groups A, B and C and areas with a security
level equal to or less than 501.
 
 is the file priority associated with the link. In most cases,
you would use CRASH for systems in your local calling area and NORMAL or
HOLD for long-distance links. Valid priorities are: Immediate, Crash,
Normal and Hold.
 
 asks whether the specified system should be sent a notification
NETmail when files are sent to it. In most cases answer YES or NO if the
specified system is an uplink.
 
 determines whether requests for unavailable fileecho areas
will be forwarded to your file hub(s). If you answer Yes, all unknown
requests will be passed along to the first applicable fileecho hub. As per
the next question, you should specify an AREAS.BBS file for forwarding. It
is not required however.
 
 specifies the filename of the system's AREAS.BBS file to
use when forwarding fileecho/TIC requests. This should only be specified
for the systems which are your hubs or uplinks. Any conference listed
in this file may be requested by other allowed systems. Make sure these
lines are listed in the desired search order.
 
* REMEMBER *  CTL-N inserts lines, CTL-Y deletes lines in a window.
 
TIC PASSWORDS: 1:110/68   Secret
 
This window allows you to specify any TIC passwords that may be required
by systems you exchange files with. Passwords are case sensitive.
 
Auto-add TIC areas? Yes       Only add from specified systems? Yes
 
Answer YES if you wish to automatically add unknown TIC areas from specified
systems or NO if not. If you answer NO, any TIC files that are received that
do not have areas defined will be moved to the "BADTICS" directory.
 
The next two questions control if you wish to allow auto-adding from
certain systems only. Answer YES and then specify which systems D'Bridge
should only auto-add fileecho areas from. If you answer NO to the next
question, D'Bridge will auto-add fileecho areas from any system.
 
Level/Add controls the default security level assigned for auto-added
fileecho areas. Level/Passthru controls the default security applied
to areas that are added as Passthru. Passthru areas should have a low
security level in order to allow any downlinks to un-Filefix them later.
 
Remove empty passthrus? Yes (Yes/No)
 
Fileecho/TIC hubs which carry many passthru areas may wish to remove
unused conferences automatically. D'Bridge will erase these unused areas a
few days after the last fileecho feed is cut. FILEFIX TIMEOUT DAYS will
control the number of inactive days to wait before killing the last feed
and sending a FILEFIX request to your feed, removing the conference.
 
Filefix forwarding days? 3
 
This parameter controls the number of days to wait for a new conference
to arrive after forwarding a request. After this many days, if a new
conference requested has not been received, a message is generated to
the original requesting system, explaining why their request was not
honored.
 
This also controls the number of days before removing a passthru area
with no links left.
 
Route Receipts? Yes
 
When a downlink requests a fileecho conference that does not exist on your
system, and that request is forwarded to your uplink, D'Bridge can route
the Filefix reply that your uplink generates back to the downlink that made
that request. Answer YES to turn this feature on. Answer NO (default setting)
to leave it shut off.
 
Unknown area forwarding:
 
Here, you may specify the address of a fileecho hub to use "blindly",
forwarding FILEFIX requests for unknown areas. If the area is not found
in any listed AREAS.BBS file, it will be sent to the specified system.
 
(Continued in next message)

--- D'Bridge 3.7