Subj : I thing I give up
To   : Nick Boel
From : Oli
Date : Wed Oct 15 2025 17:08:54

Good ${greeting_time}, Nick!

14 Oct 25 07:28, you wrote to Joacim Melin:

 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. When
 NB> using this method (4D addressing), it is better to use one outbound
 NB> directory, ie:

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

Only for 4D adressing, but crashmail uses FTSC compliant 5D BSO.

 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

Wrong. With that configuration you don't get proper 5D outbound directories. Crashmail does it correctly. A hex extension for all domains with the exception of the first domain's default zone, e.g:

/fido/outbound
/fido/amiganet.027
/fido/fsxnet.015

 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.

Which is not standard compliant. Unfortunatly binkd's 5D implementation is not correct and everyone seems to believe that it is. The configuration Joacim used is a work around to achieve 5D BSO with binkd:

domain fidonet /fido/outbound 2
domain amiganet /fido/amiganet 2
domain fsxnet /fido/fsxnet 2

See FTS-5005 for the specification of 5D BSO.

 * Origin: kakistocracy (2:280/464.47)

.