TZUTC: -0500
MSGID: 1833.binkd@1:2320/105 2d53979c
REPLY: 1:154/10 68ee4629
PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
TID: SBBSecho 3.28-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
BBSID: CAPCITY2
CHRS: ASCII 1
FORMAT: flowed
> If Crashmail is properly using /fido/Amiganet, /fido/Fsxnet and so on
/without
> the hex extensions, your binkd config may be better off using this as an
> example, where you put the actual zone number of the network instead of your
> default zone (2). This is proper 5D addressing, whereas you seem to be trying
> to use a mixture of 4D and 5D configurations and hoping for the best at the
> moment:

> domain fidonet /fido/outbound 2
> domain fsxnet /fido/fsxnet 21

To expand some on what Nicholas said, I was running some tosser for a while
that was determined not to use the typical "/out.(hex)" directories that
worked well with binkd.  My fix, as I am running on linux, was to create
symlinks to the standard path using the paths the tosser wanted as the
symlink names.

So the tosser could write to whatever non-standard paths it
wanted to, while the binkd config was pointed to the standard named
"out.(hex)" paths.

Thought I would throw that in there as a potential option if his suggestion
didn't quite work.


 * SLMR 2.1a * Excuse my driving ... I'm trying to reload.
--- SBBSecho 3.28-Linux
 * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
SEEN-BY: 19/25 33 38 41 50 105/81 106/201 987 124/5016 128/187 129/14
SEEN-BY: 129/305 130/330 153/7715 154/110 218/700 226/30 227/114 229/110
SEEN-BY: 229/200 206 275 300 307 317 426 428 470 664 700 705 266/512
SEEN-BY: 280/464 291/111 292/854 320/219 322/757 329/219 342/200 387/18
SEEN-BY: 387/25 396/45 633/280 712/848 902/26
PATH: 2320/105 154/10 280/464 396/45 229/426