TZUTC: -0500
MSGID: 1729.binkd@1:2320/105 2bb5c151
REPLY: 3409.binkd@1:154/700 2bb4d50f
PID: Synchronet 3.20a-Linux master/acc19483f Apr 26 202 GCC 12.2.0
TID: SBBSecho 3.20-Linux master/acc19483f Apr 26 2024 23:04 GCC 12.2.0
BBSID: CAPCITY2
CHRS: ASCII 1
> > 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.

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

binkd seems to work fine here with "out" the and "out.(hex)" that sbbsecho
creates.

Now, when using other tossers with other BBS software, I sometimes had to
create symlinks so that binkd would work correctly.  For example, if the
tosser did something like "fsxnet.015" for the othernets.  I would have to
set up a symlink to "out.015" so that binkd would find the mail.


 * SLMR 2.1a * "Excellent...excellent..." - Mr. Burns
--- SBBSecho 3.20-Linux
 * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
SEEN-BY: 10/0 1 102/401 103/1 705 104/119 105/81 106/201 116/17 18
SEEN-BY: 120/302 616 124/5016 128/187 129/215 305 153/757 7715 154/10
SEEN-BY: 154/30 50 700 203/0 214/22 218/0 1 215 601 700 720 840 860
SEEN-BY: 218/870 880 930 940 220/20 90 221/0 6 226/18 30 44 50 227/114
SEEN-BY: 229/110 114 200 206 275 300 307 310 317 426 428 470 550 664
SEEN-BY: 229/700 705 240/1120 5832 266/512 280/464 5003 5006 5555
SEEN-BY: 282/1038 291/111 292/854 8125 301/1 310/31 320/219 322/757
SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 467/888 633/280
SEEN-BY: 712/848 770/1 902/26 2320/0 105 304 401 3634/12 5020/400
PATH: 2320/105 154/10 280/464 103/705 218/700 229/426