REPLY: 3409.binkd@1:154/700 2bb4d50f
MSGID: 1:320/219@fidonet 675432ee
CHRS: UTF-8 2
TZUTC: -0500
TID: MBSE-FIDO 1.1.0 (Linux-x86_64)
Hello Nick!

03 Dec 24 17:18, you wrote to all:

 >> No, unfortunately binkd is doing it wrong by default. Fastecho
 >> implements 5D BSO correctly according to the FTSC standard. And yes,
 >> using a non-existing zone (e.g. 1) as the default zone for the
 >> domain is a proper workaround.

 NB> I guess it's time for me to re-read the standard, then. I could have
 NB> sworn 4d uses the hex value extensions (ie outbound.001, and 5d didn't
 NB>  (ie outbound).

5D BSO support uses the hex zone number extension for all but the primary zone 
in that domain.  binkd is actually flexible enough to work around many mail 
packages that do it wrong.  FastEcho, for example, always uses the hex zone 
number extension for domain directories.

ie: micronet.26a for Micronet zone 618, even though 618 is the primary zone in 
that domain.

Thus, by lying to binkd that the primary zone for all domains is 1, you can 
force binkd to use the hex zone extension for all of your added domains, which 
is exactly what FastEcho produces.

Andrew

--- GoldED+/LNX 1.1.5-b20240209
 * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
SEEN-BY: 1/19 16/0 19/37 40 105/81 106/201 123/130 128/187 129/305
SEEN-BY: 132/174 142/104 926 153/7715 203/0 218/700 221/0 226/30 227/114
SEEN-BY: 229/110 114 200 206 300 307 317 426 428 550 664 700 705 240/5832
SEEN-BY: 266/512 282/1038 291/111 292/854 320/119 219 319 2119 322/757
SEEN-BY: 322/762 342/200 396/45 633/280 712/848 902/26
PATH: 320/219 229/426