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,809 of 8,958    |
|    Oli to Andrew Leary    |
|    Binkd with Fastecho...    |
|    08 Dec 24 17:17:17    |
      MSGID: 2:280/464.47 6755c686       REPLY: 1:320/219@fidonet 675432ee       PID: JamNNTPd/Linux 1       CHRS: LATIN-1 2       TZUTC: 0100       TID: CrashMail II/Linux 1.7       Andrew wrote (2024-12-07):               AL> 5D BSO support uses the hex zone number extension for all but the primary        AL> zone in that domain.              In BSO the hex zone number extension is omitted for the default outbound only,       which is the default zone in the first domain. Every other outbound directory       has a zone extension.              From FTS-5005.003:               For example, if your default outbound is C:\BINK\OUTBOUND        for the outbound holding area (and you are in FidoNet), Amiganet        (zone 39) outbound mail would be held in the C:\BINK\AMIGANET.027        directory instead. Note that outbound areas for domains other than        your primary will ALWAYS have a zone extension, and that zone        extensions are always specified in Hexadecimal, up to .FFF (4095).               The outbound holding areas (for Zone 1 FidoNet) would then be as        follows:               c:\bink\outbound (Default Outbound)        c:\bink\outbound.002 (FidoNet Zone 2)        c:\bink\outbound.003 (FidoNet Zone 3)        c:\bink\outbound.004 (FidoNet Zone 4)        c:\bink\amiganet.027 (Amiganet Zone 39)        c:\bink\agoranet.02e (Agoranet Zone 46)        c:\bink\dbnet.0c9 (Dbnet Zone 201)               AL> binkd is actually flexible enough to work around        AL> many mail packages that do it wrong. FastEcho, for example, always uses        AL> the hex zone number extension for domain directories.              binkd never implemented it correctly. What you call a workaround is a       workaround for a binkd bug. The narrative that all the other mailers do it       wrong and binkd is the one software that does it right is just an alternative       fact. BSO 5D was used before binkd even existed. BinkleyTerm had no problems       with 5D outbound from Fastecho, Squish, Crashmail and other mailers .              ---        * Origin: No REPLY kludge - no reply (2:280/464.47)       SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/305 153/757 7715       SEEN-BY: 154/10 30 203/0 218/700 221/0 1 226/30 227/114 229/110 114       SEEN-BY: 229/200 206 300 307 317 426 428 550 664 700 705 240/1120       SEEN-BY: 240/5832 266/512 280/464 5003 5006 5555 282/1038 291/111       SEEN-BY: 292/789 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