TZUTC: -0400
MSGID: 589.fido-binkd@1:3634/12 22e4b973
REPLY: 2:280/464.47@fidonet 5e7f3fdd
PID: Synchronet 3.17c-Linux Mar 23 2020 GCC 7.5.0
TID: SBBSecho 3.10-Linux r3.152 Mar 23 2020 GCC 7.5.0
CHRS: ASCII 1
NOTE: FSEditor.js v1.103
Re: Issue with BinkD and outbound attempts.
By: Oli to Tony Langdon on Sat Mar 28 2020 12:54:59
Oli> If binkd's parameter is intented to have the same
Oli> meaning as "the default zone" in FTS-5005 than using the same
Oli> zone number for all "domain" lines is the right configuration
Oli> (and not a workaround).
don't get confused by the chicken and the egg syndrome... binkd came first and
the FTSC documents came after ;)
Oli> It is counterintuitive though and the example binkd.cfg files
Oli> suggests you should use the zone number of the network.
exactly why using the same default zone for all domains is a workaround which
also leads to all domain directories having the hex zone extension on them...
i had several discussions with a few of the binkd devs in here some years back
when i was working on my 4DOS/4OS2 BSO scripts... i was told that for proper
5D, only the first directory for each FTN domain's outbound directory has no
hex zone extension on it... all the others do...
then there's this from the binkd FAQ... this quote is from one i saved back in
2017 so the question number may be off but anyway, it is #22 here...
----->8 snip 8<-----
22. Different FTN Domains in binkd And a Tosser Without 5D Support
Suppose there are two domains (with different zone numbers though it
does not matter). Mail can be successfully sent to the first domain but
not to the second one. This situation may arise if the tosser, the tracker
and the other your FTN programs do not support 5D BSO.
This is a typical binkd configuration for two FTN domains and 5D
outbound:
domain fidonet c:\\ftn\\outbound\\fidonet 2
domain omeganet c:\\ftn\\outbound\\omeganet 11
address 2:5070/222@fidonet 11:58/6@omeganet
One must configure not the zone of your own address for 'domain'
keyword as one might think but the zone that should not be appended to the
outbound name (i.e. the outbound subdirectory extensions are not processed
for the zone denoted in the 'domain' line).
If your tosser would create bundles for omeganet in the omeganet
directory then you should write as indicated above. But since it does not
work with 5D and it creates the bundles in fidonet.00b then you should
write this way:
domain fidonet c:\\ftn\\outbound\\fidonet 2
domain omeganet c:\\ftn\\outbound\\fidonet 2
address 2:5070/222@fidonet 11:58/6@omeganet
It is obligatory to configure all your addresses with domains. The
outbound directory and the path should be the same everywhere (4D tosser
considers all addresses to belong to one domain).
----->8 snip 8<-----
i did (finally) find the text of a message where stas replied to me in
reference to my questions about 5D while working on my 4DOS/4OS2 scripts... i
think this was back in about 2011 going by the version of his golded...
unfortulately i cannot currently get to the actual header of his message...
----->8 snip 8<-----
Hello mark.
25 Jul 12 17:04, you wrote to me:
ml> eg:
ml> domain fidonet x:\\bink\\outbound\\fidonet 1
ml> domain quartz x:\\bink\\outbound\\quartz 123
ml> X:\BINK\OUTBOUND\FIDONET
ml> X:\BINK\OUTBOUND\FIDONET .002
ml> X:\BINK\OUTBOUND\FIDONET .003
ml> X:\BINK\OUTBOUND\FIDONET .004
ml> X:\BINK\OUTBOUND\FIDONET .005
ml> X:\BINK\OUTBOUND\FIDONET .006
OK
ml> X:\BINK\OUTBOUND\QUARTZ .07B
Invalid, should be:
X:\BINK\OUTBOUND\QUARTZ
ml> X:\BINK\OUTBOUND\QUARTZ .07C
ml> X:\BINK\OUTBOUND\QUARTZ .07D
OK
ml> the above indicates fidonet is zones 1,2,3,4,5,6 and quartz is
ml> 123,124,125??
Zone 123 specified as "default for the domain quartz" and outbound directory
for 123:*@quartz should be without number in suffix.
ml> and if i have foobar net with zone 124 (duplicate zone, different
ml> domain) then...
ml> domain fidonet x:\\bink\\outbound\\fidonet 1
ml> domain quartz x:\\bink\\outbound\\quartz 123
ml> domain foobar x:\\bink\\outbound\\foobar 124
ml> X:\BINK\OUTBOUND\FIDONET
ml> X:\BINK\OUTBOUND\FIDONET .002
ml> X:\BINK\OUTBOUND\FIDONET .003
ml> X:\BINK\OUTBOUND\FIDONET .004
ml> X:\BINK\OUTBOUND\FIDONET .005
ml> X:\BINK\OUTBOUND\FIDONET .006
OK
ml> X:\BINK\OUTBOUND\FOOBAR .07C
ml> X:\BINK\OUTBOUND\QUARTZ .07B
Invalid, should be:
X:\BINK\OUTBOUND\FOOBAR
X:\BINK\OUTBOUND\QUARTZ
ml> X:\BINK\OUTBOUND\QUARTZ .07C
ml> X:\BINK\OUTBOUND\QUARTZ .07D
OK
ml> the above indicates fidonet is zones 1,2,3,4,5,6... foobar is 124...
ml> quartz is 123,124,125???
Stas
Jabber-ID: grumbler@grumbler.org
GPG key 0x72186DB9 (keyserver: hkp://wwwkeys.eu.pgp.net)
.!. Golded+, Husky & RNTrack maintainer, Binkd developer&webmaster
-!- GoldED+/LNX 1.1.5-b20110302
! Origin: Grumbler at home (2:5080/102.1)
----->8 snip 8<-----
i've taken and used the above as the definitive format for a proper 5D
outbound directory layout ever since... specifically, the *default outbound
for each domain has no hex zone extension* on it while all the others do...
)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
SEEN-BY: 1/120 123 14/6 18/0 19/10 90/1 103/705 116/116 123/0 25 50
SEEN-BY: 123/115 150 170 755 135/300 153/7715 154/10 203/0 221/0 1
SEEN-BY: 221/6 242 360 226/30 227/114 229/101 200 426 1014 230/0 240/5832
SEEN-BY: 249/109 307 317 261/38 280/464 5003 5555 288/100 292/854
SEEN-BY: 300/4 310/31 320/219 342/200 396/45 423/81 120 633/280 640/1138
SEEN-BY: 640/1321 1384 712/848 770/1 2452/250 3634/0 12 15 27 50 119
PATH: 3634/12 640/1384 221/1 280/464 229/426
|
