Subj : Re: Binkd with Fastecho..
To : NICK BOEL
From : Mike Powell
Date : Wed Dec 04 2024 11:10 am
> > 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.
