Subj : Re: Retiring this echo
To   : Dumas Walker
From : Dan Clough
Date : Sat May 31 2025 20:47:13

-=> Dumas Walker wrote to DAN CLOUGH <=-

 >  MP> See above.  Your information is not correct for hubs, especially if you
 >  MP> are on multiple networks.

 > Mike, you really need to look at the Wiki, specifically the terms
 > "echolist", and the "Keys" specifier in sbbsecho.ini, applicable to each
 > linked node.  Basically, you specify a key which points to a filename,
 > which is essentially a .NA file for that FTN.  Then that linked node can
 > only see/request echos for that FTN.  It's very easy to set up, and
 > works perfectly.  It *EXACTLY* solves the problem you're describing for
 > hubs on multiple networks.

 DW> We are saying the same thing, and it points to why the BACKBONE.NA *is*
 DW> important.  I am using the BACKBONE.NA for the "FIDO" keyed nodes, and
 DW> suspect that others do, too.  I would hope they are not attempting to
 DW> keep a FIDO NA file by hand.

Well, it is important (maybe) as a base/starter point.  I've edited my 
copy to remove the obvious garbage and deadwood.  I have another Key 
with the names of some echos that don't come from the "backbone".  But 
the real point here is how this keeps FTNs separated from each other 
when you are a hub in multiple networks.  The actual FidoNet 
"BACKBONE.NA" file is not very accurate any more as to what is actually 
available.



.... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.27-Linux
 * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

.