MSGID: 2:221/242.0@FidoNet 68eec2ef
REPLY: 1:154/10 68ee4629
CHRS: LATIN-1 2
PID: NiKom v2.6.0
TID: CrashMail II/Linux 1.7
 NB> Hey Joacim!

 NB> On Tue, 14 Oct 2025 14:05:46 , you wrote:

 >> So I figured it out, and it's properly silly on my part.

 >> I figured it out.  I think.

 >> In Binkd I named the other networks Amiganet, Fsxnet, and so on.  But
 >> the paths the outgoing stuff was written to was set to /fido/amiganet,
 >> /fido/fsxnet and so on.

 >> Naturally, Binkd was looking in /fido/Fsxnet.xxx and /fido/Amiganet.xxx.

 NB> That's because your binkd config file specifies to look in those
 NB> directories. When using your default zone "2" for every network, it
 NB> will automatically create the hex extensions on your directories.
 NB> When using this method (4D addressing), it is better to use one
 NB> outbound directory, ie:

 NB> domain fidonet /fido/outbound 2
 NB> domain fsxnet /fido/outbound 2
 NB> domain othernet /fido/outbound 2

 NB> This will use 'outbound' as your fidonet outbound (default),
 NB> outbound.015 for fsxnet, etc.

 NB> If Crashmail is properly using /fido/Amiganet, /fido/Fsxnet and so on
 NB> /without/ the hex extensions, your binkd config may be better off
 NB> using this as an example, where you put the actual zone number of the
 NB> network instead of your default zone (2). This is proper 5D
 NB> addressing, whereas you seem to be trying to use a mixture of 4D and
 NB> 5D configurations and hoping for the best at the moment:

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

 NB> .. and the same for every other network you have, with their proper
 NB> zone number. This (I believe) disables the hex extensions and allows
 NB> you to use directory names without them.

 NB> This method only works with Crashmail and a few other tossers that
 NB> support multiple outbound directories. Aside from that, I'm not sure
 NB> where you've specified directories with uppercase letters (maybe
 NB> further into your Crashmail config that you didn't post?) but you
 NB> will have to deal with that separately.

 >> Now I'm taking a backup of all configuration files...

 NB> If it's currently working, back them up. Then maybe look into the
 NB> difference between 4D and 5D addressing so that you understand
 NB> better. From what I can tell, your configuration may currently be
 NB> working, but it is still not correct.

 NB> Hope that helps.


Great explanation! Thanks!   I belive Crashmail grabs the name from here: 

AKA 21:2/130.0
DOMAIN "Fsxnet"

But I'm not sure.  It's the only place in crashmail.prefs or binkd.conf where
it's spelled with a capital 'f'. 


--- NiKom v2.6.0
 * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:221/242.0)
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: 221/242 1 280/464 396/45 229/426