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 7,824 of 8,958    |
|    Oli to Andrew Leary    |
|    Problem with filenames containing spaces    |
|    20 Jan 22 11:18:12    |
      MSGID: 2:280/464.47 61e936e2       REPLY: 1:320/219@fidonet 61e8f821       PID: JamNNTPd/Linux 1       CHRS: LATIN-1 2       TZUTC: 0100       TID: CrashMail II/Linux 1.7       Andrew wrote (2022-01-20):               >>> BinkD (the original implementation of BinkP) has always used \x##        >>> as far as I know.               RS>> BinkD was changed to *accept* '\##' however, back in 2002:        RS>> https://github.com/pgul/binkd/commit/b4e7b17b7f0621abc1b3017307dd1382e        RS>> aa039d9               AL> That explains why when James tested against BinkD it had no issues with        AL> him using \##.              And I think adding that workaround for broken mailers was a mistake that       brought us more incompatibilities. Or should have been only a temporary       workaround and deprecated a few years later.              https://en.wikipedia.org/wiki/Robustness_principle#Criticism       https://datatracker.ietf.org/doc/html/draft-iab-protocol-maintenance               AL> The most compatible way to do things is to accept both on incoming, while        AL> sending using \x##, unless configured otherwise on a per node basis, or        AL> when you detect you are connected to a known mailer that uses \## (Argus        AL> or IRex.)              All the big drama for a single legacy mailer: Irex that hasn't been updated       forever. Argus users can upgrade to Radius or Taurus (both abandonware).       Mystic is actively developed and users should use the latest release.              Let's face it: closed source software that isn't developed anymore has to       become obsolete in a communication network that evolves (even slowly). If you       want to do it the old way, you can still use EMSI over TCP.              And it's only a problem with filenames that contains a whitespace character.              ---        * Origin: Birds aren't real (2:280/464.47)       SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340       SEEN-BY: 123/120 131 124/5016 129/305 330 153/250 757 7715 154/10       SEEN-BY: 203/0 218/840 220/70 221/0 226/17 30 227/114 229/110 200       SEEN-BY: 229/307 317 424 426 550 664 700 240/5832 249/206 250/5 8       SEEN-BY: 266/512 267/800 280/464 5003 5555 282/1038 292/854 8125 298/25       SEEN-BY: 301/1 305/3 310/31 317/3 320/219 322/757 341/234 342/200       SEEN-BY: 396/45 423/120 460/58 633/280 712/848 770/1 100 340 772/210       SEEN-BY: 772/220 230 2452/250       PATH: 280/464 770/1 317/3 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca