Subj : Issue with BinkD and outbound attempts.
To   : Tony Langdon
From : Oli
Date : Sat Mar 28 2020 12:54:59

 Ol>>> but Binkd is omitting the zone number after the dot.

 TL>> Unless you use the same default zone (for most people, your Fidonet zone)
 TL>> for all domain entries.

 Ol>> But it's a workaround with side effects. Why do we have a default zone
 Ol>> number in the first place, when the only way to get standard conformat
 Ol>> 5D BSO directories is by deliberately putting wrong zone numbers in the
 Ol>> config?

 TL> Side effects?

You are right, it doesn't make any difference in my setup. This works fine:

domain fidonet  /srv/ftn/outbound/fidonet  2
domain fsxnet   /srv/ftn/outbound/fsxnet   2
domain amiganet /srv/ftn/outbound/amiganet 2

I thought binkd wouldn't be able to figure out which zone number maps to which 
domain, but it doesn't seem to be a problem.

$ poll 39:15/0
  12:59 [16912] BEGIN, binkd/1.1a-101/Linux -p -P 39:15/0 
/srv/ftn/binkd/binkd.cfg
  12:59 [16912] creating a poll for 39:15/0@amiganet (`d' flavour)

 TL> And I note that the FTSC document you referenced only talks
 TL> about "the default zone", but doesn't qualify it as being for a domain 
(which
 TL> you would expect).  So there's assumptions there.

If binkd's <default-zone> parameter is intented to have the same meaning as 
"the default zone" in FTS-5005 than using the same zone number for all "domain" 
lines is the right configuration (and not a workaround). It is counterintuitive 
though and the example binkd.cfg files suggests you should use the zone number 
of the network.

--- GoldED+/LNX 1.1.5-b20180707
 * Origin: kakistocracy (2:280/464.47)

.