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

-=> On 03-27-20 14:15, Oli wrote to mark lewis <=-


 Ol> in cases
 ml> where binkd has to be lied to and told that all domains use zone 1 for
 Ol> their first
 ml> outbound...

That's what I do, except that my default zone is zone 3, rather than 1.  So all
of my domains in binkd have 3 as the default zone in binkd.conf.

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

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

That's what my outbound tree looks like, except for the details - my domains
are largely different, and I'm on Linux, but the structure is broadly the same,
as you'd expect.

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

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


.... Spelling is a sober man's game
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

.