Subj : Issue with BinkD and outbound attempts.
To   : mark lewis
From : Oli
Date : Fri Mar 27 2020 14:15:17

 ml>   Re: Issue with BinkD and outbound attempts.
 ml>   By: Oli to Eric Renfro on Fri Mar 27 2020 08:28:47

 Oli>> I might be missing something, but for me this behaviour makes sense.
 Oli>> There is a .flo file in the outbound of fidonet _and_ gatornet (both
 Oli>> domains use the same outbound config) and of course binkd is trying
 Oli>> both networks. What is missing in binkd is a way to map zone numbers
 Oli>> to domains.

 ml> that mapping is done by the domain lines... it generally works well except 
in cases
 ml> where binkd has to be lied to and told that all domains use zone 1 for 
their first
 ml> outbound...

Not really, you can only define the default zone number for a domain not 
multiple zones (like 1, 2, 3, 4 for Fidonet). As long as the default domain is 
the only one with multiple zones it works fine in 5D mode. Appart from the fact 
that Binkd also doesn't create standard conformant outbound dirs as defined in 
fts-5005, e.g. it should look like this

  c:\bink\outbound        (Default Outbound)
  c:\bink\outbound.002    (FidoNet Zone 2)
  c:\bink\outbound.003    (FidoNet Zone 3)
  c:\bink\outbound.004    (FidoNet Zone 4)
  c:\bink\amiganet.027    (Amiganet Zone 39)
  c:\bink\agoranet.02e    (Agoranet Zone 46)
  c:\bink\dbnet.0c9       (Dbnet Zone 201)

but Binkd is omitting the zone number after the dot.

The 4D workaround is mentioned in the official BINKD FAQ, which suggests that 
it should work just fine.



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

.