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 6,425 of 8,958    |
|    Oli to Tommi Koivula    |
|    Ialternaernaernative transports    |
|    13 Dec 19 22:03:43    |
      REPLY: 2:221/360 5df3da00       MSGID: 2:280/464.47@fidonet 5df4004b       PID: GED+LNX 1.1.5-b20180707       CHRS: UTF-8 4       TZUTC: 0100       TID: CrashMail II/Linux 1.7        TK>> Would you explain this "external command"? How to run it from        TK>> binkd?               TK> Never mind, I got it:               TK> === Cut ===        TK> node 2:221/6 -pipe "openssl s_client -quiet -alpn binkp -connect        TK> news.fidonet.fi:24567" *        TK> === Cut ===              alternatice command is              node 2:221/6 -pipe "ncat --ssl-alpn binkp *H *I" news.fidonet.fi:24567              The alpn stuff is only needed if the server demands it (e.g when running       webserver, xmpp server, binkp on port 443). I use "ncat --ssl-alpn binkp H*       I*", because "ncat --ssl H* I*" invokes ncat with the port number "I*" instead       of the real port number. I guess this is a bug in binkd. Some problem with       parsing the -pipe parameter?              I wonder, if we should directly jump to QUIC instead of implementing TLS over       TCP?               * Origin: kakistocracy (2:280/464.47)       SEEN-BY: 1/123 90/1 103/705 154/10 203/0 221/0 227/114 229/101 200       SEEN-BY: 229/354 426 1014 240/5832 249/307 317 280/464 5003 5555 292/854       SEEN-BY: 310/31 342/200 396/45 423/120 712/848 770/1 2452/250       PATH: 280/464 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca