REPLY: 2:280/464.47@fidonet 68efc716   
   MSGID: 1:154/10 68f01874   
   CHRS: UTF-8 4   
   TZUTC: -0500   
   TID: hpt/lnx 1.9 2024-03-02   
   Hey Oli!   
      
   On Wed, 15 Oct 2025 17:08:54 +0100, you wrote:   
      
    > Only for 4D adressing, but crashmail uses FTSC compliant 5D BSO.   
      
   I'm fairly certain I just said that. ;)   
      
    NB>> If Crashmail is properly using /fido/Amiganet, /fido/Fsxnet and so   
    NB>> on /without/ the hex extensions, your binkd config may be better   
    NB>> off using this as an example, where you put the actual zone number   
    NB>> of the 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   
    NB>> and 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   
      
   By reading exactly what he had posted, that didn't seem to be the case... See   
   below.   
      
    > 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.   
      
   I'm just going by what he originally said:   
      
   --- Quote   
   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.   
   --- End Quote   
      
   Notice there were no extensions in the first sentence.   
      
   If his "stuff" was being /written/ to directories /without/ hex extensions,   
   that is NOT binkd's doing, it is Crashmail. If he meant to say "But the paths   
   the outgoing stuff was written to was set to /fido/amiganet.027,   
   /fido/fsxnet.015 and so on," then it was simply a case problem where he   
   defined his domains in binkd with uppercase first letters and lowercase first   
   letters in Crashmail. However, that is NOT what he originally said. I gave him   
   an answer to what he originally said.   
      
   If what he said was wrong, then my answer was wrong, too. One can only go by   
   what is written when trying to help.   
      
   Regards,   
   Nick   
      
   ... Sarcasm: because beating people up is illegal.   
   --- GoldED+/LNX 1.1.5-b20250409   
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)   
   SEEN-BY: 10/0 1 102/401 103/1 705 104/119 105/81 106/201 114/10 120/302   
   SEEN-BY: 120/616 124/5016 128/187 129/14 215 305 153/757 7715 154/10   
   SEEN-BY: 154/30 50 110 700 203/0 214/22 218/0 1 215 601 610 620 700   
   SEEN-BY: 218/840 860 880 220/20 30 90 221/0 6 226/18 30 44 50 227/114   
   SEEN-BY: 229/110 200 206 275 300 307 310 317 426 428 470 664 700 705   
   SEEN-BY: 240/1120 5832 263/1 266/512 280/464 5003 5006 5555 291/111   
   SEEN-BY: 292/854 8125 301/1 310/31 320/219 322/757 341/66 234 342/200   
   SEEN-BY: 396/45 423/120 460/58 467/888 633/280 712/848 770/1 902/26   
   SEEN-BY: 2320/105 3634/12 5020/400   
   PATH: 154/10 280/464 103/705 218/700 229/426