home bbs files messages ]

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,786 of 8,958   
   deon to James Coyle   
   Re: Problem with filenames containing sp   
   15 Jan 22 08:30:53   
   
   TZUTC: 1100   
   MSGID: 1610.fdn_binkd@3:633/509 264727d7   
   REPLY: 1:129/215 3feeec43   
   PID: Synchronet 3.19a-Linux master/8f79438d2 Apr 24 2021 GCC 8.3.0   
   TID: SBBSecho 3.14-Linux master/8f79438d2 Apr 24 2021 GCC 8.3.0   
   COLS: 139   
   BBSID: ALTERANT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.104   
     Re: Re: Problem with filenames containing spaces   
     By: James Coyle to deon on Fri Jan 14 2022 03:34 pm   
      
    >  de> binkd has implemented the procotol as per the standard, whereas james   
   has implemented as per the proposal.   
    >   
    > Just for clarification: Mystic does both.  Or at least it does as of a   
   couple hours after the issue was first brought to my attention   
    > (which was a couple years ago I believe).   
    >   
    > And in the latest version it also allows it to be configured on a per-node   
   basis, so if you have one downlink with a legacy mailer that   
    > won't work with anything but /## and one that only supports /x## you can   
   configure each node accordingly.   
      
   Something for me doesnt add up with your reply, so I'll re-iterate what I   
   think you saying and you can set me straight...   
      
   Are you saying that Mystic's binkp will send a file to a node using an escape   
   sequence of \## or \x## depending on how the sysop has configured that node in   
   Mystic configuration?   
      
   The issue at hand is Mystic's binkp receiving a file, where the sender encodes   
   ASCII < 32 as \x## - Mystic cannot process it. Your reply to this was the   
   sending system shouldnt encode that way (it should be using \##) and thus must   
   be changed.   
      
   Did I get that right?   
      
      
   ...лоеп   
   --- SBBSecho 3.14-Linux   
    * Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)   
   SEEN-BY: 1/123 14/0 15/0 90/1 105/81 106/201 114/709 120/340 123/131   
   SEEN-BY: 129/305 153/7715 226/30 227/114 229/110 200 307 424 426 550   
   SEEN-BY: 229/664 700 240/5832 249/206 317 266/512 282/1038 292/854   
   SEEN-BY: 301/1 317/3 320/219 322/757 342/200 396/45 633/267 280 281   
   SEEN-BY: 633/384 410 412 416 509 640/1384 712/848 770/1   
   PATH: 633/509 280 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca