Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    BINKD    |    Support for the Internet BinKD mailer    |    8,958 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,924 of 8,958    |
|    Oli to Nick Boel    |
|    I thing I give up    |
|    15 Oct 25 17:08:54    |
   
   REPLY: 1:154/10 68ee4629   
   MSGID: 2:280/464.47@fidonet 68efc716   
   PID: GED+LNX 1.1.5-b20230205   
   CHRS: UTF-8 2   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   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)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 305 153/757   
   SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/0 1 226/30 227/114   
   SEEN-BY: 229/110 200 206 275 300 307 317 426 428 470 664 700 705 240/1120   
   SEEN-BY: 240/5832 263/1 266/512 280/464 5003 5006 5555 291/111 292/789   
   SEEN-BY: 292/854 8125 301/1 310/31 320/219 322/757 335/364 341/66   
   SEEN-BY: 341/234 342/200 396/45 410/9 423/120 460/58 467/888 633/280   
   SEEN-BY: 712/848 770/1 902/26 5001/100 5020/400   
   PATH: 280/464 292/854 229/426   
      
|
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca