Subj : Re: Problem with filenames containing spaces
To   : deon
From : James Coyle
Date : Mon Jan 17 2022 11:00 am

 de> Are you saying that Mystic's binkp will send a file to a node using an
 de> escape sequence of \## or \x## depending on how the sysop has configured
 de> that node in Mystic configuration?

Yes.

For incoming filenames Mystic handles all variations.

For outbound filenames it uses \## (because any mailer that does \x## will also accept \##, but mailers that accept \## wont accept \x##). Its the most compatible method.  This is how it worked up to A47.

Then in A48 I went further and added in the option in the node configuration so you can choose per-connection just in case there someday is a newer mailer in the future that does \x## but can't do \##...

This A48 addition was as a result of the recommendation that was pointed out to me in FTS-1026.001: http://ftsc.org/docs/fts-1026.001

"In FSP-1011.003 the escape method is specified as two hexadecimal digits preceded with a backslash (e.g. a whitespace is transmitted as "\20").  Some mailers have implemented that method. It is advised to have a setting for specific nodes to sent escaped characters using the incorrect method."

Mystic implements the recommendation made in the last sentence but BINKD does not as far as I know?  So the solution to Paul's problem is to have BINKD follow the FTS recommendation, or for the person to upgrade their software version. I can't help him.

.... Do vegetarians eat animal crackers?

--- Mystic BBS v1.12 A48 2022/01/14 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)

.