Subj : Re: Second Network Configuration
To   : Al
From : Vk3jed
Date : Mon Aug 10 2020 16:36:00

-=> On 08-09-20 04:07, Al wrote to Vk3jed <=-

 Al> If your getting .015 added to your outbound directory then you would
 Al> need to use the same default zone number.

The tossers I've used add the hex extension on all othernet directories.  The
only one without an extension is the default director of my primary AKA, which
happens to be Fidonet, and corresponds to Fidonet Z3, so in all of my domain
entries in binkd.conf, I have to use 3 as the default zone for all domains. 
That way, binkd looks for files and mail in the othernet.NNN, where NNN is the
hex extension.

 Al> I always thought that a 5D outbound would need the actual zone number
 Al> and not get the .015 added to the outbound for that zone but I have
 Al> never had a fully 5D tosser to play with.

I'm not sure what tossers support full 5D.  I know SBBSEcho, for example, can't
handle the same zone in 2 different domains, which should be possible in a true
5D environment.  That's because SBBSEcho actually maps zones to domains in its
"5D" configuration.  I don't know if Mystic'd mutil is a true 5D tosser, would
have to create a dummy domain with a zone number that conflicts with something
else that I have to test.

 Al> Mystic seems to create outbound directories per net, but also has the
 Al> .015 zone in hex appended to the outbound. Is that a fully 5D outbound
 Al> structure?

I'm led to believe that BinkleyTerm behaves like binkd, and BT is supposed to
be the "reference" 5D implementation.

 Al> There can be other cases to like Blue White who needs to use the actaul
 Al> zone number with binkleyterm along with squish.

Interesting.  I've never used Squish.  Anyway, there seems to be different
interpretations of 5D BSO, but at least binkd can cope with the permutations.


.... Trilogy (n). Series of three books, sometimes more.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

.