MSGID: 2:280/464.47 674f33de
REPLY: 3404.binkd@1:154/700 2bb0f217
PID: JamNNTPd/Linux 1
CHRS: LATIN-1 2
TZUTC: 0100
TID: CrashMail II/Linux 1.7
Nick wrote (2024-11-30):


 NB> Don't overthink this. When using 1 for each of the above domains, binkd
 NB> will automatically look in the outbound.xxx directories that Fastecho is
 NB> creating. It will not "put all of the directories together", binkd
 NB> automatically uses the hex value for the directory extensions when you
 NB> use 1 for the zone.

 NB> If Fastecho was /really/ doing 5d, it wouldn't have directory extensions
 NB> (which binkd does correctly when you use the above settings), but it's
 NB> not.

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.

---
 * Origin: No REPLY kludge - no reply (2:280/464.47)
SEEN-BY: 10/0 1 102/401 103/1 705 105/81 106/201 124/5016 128/187
SEEN-BY: 129/305 153/757 7715 154/10 30 203/0 214/22 218/0 1 215 601
SEEN-BY: 218/700 720 840 860 870 880 930 940 221/0 226/30 227/114
SEEN-BY: 229/110 114 200 206 275 300 307 317 426 428 470 550 664 700
SEEN-BY: 229/705 240/1120 5832 266/512 280/464 5003 5006 5555 282/1038
SEEN-BY: 291/111 292/854 8125 301/1 310/31 320/219 322/757 341/66
SEEN-BY: 341/234 342/200 396/45 423/120 460/58 467/888 633/280 712/848
SEEN-BY: 770/1 902/26 5020/400
PATH: 280/464 103/705 218/700 229/426