Subj : Re: Problem with filenames containing spaces
To   : James Coyle
From : deon
Date : Sat Jan 15 2022 08:30 am

  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)

.