Subj : Problem with filenames containing spaces
To : James Coyle
From : Andrew Leary
Date : Wed Jan 19 2022 08:52 pm
Hello James!
19 Jan 22 11:14, you wrote to Oli:
JC> 2) Those that escape with \x## but still allow \## from the mailer
JC> side
JC> BinkD (I think MBSE does too)
I just verified in the code that mbcico defaults to sending \x##, but can be
overridden on a per node basis to send \##. Both will be accepted on the
incoming side.
JC> Both MBSE and newer Mystic provides the option to support \## or \x##
JC> escaping per connection as noted. This seems to be what FTS
JC> recommends as a way to handle this mess. It does seem to be a viable
JC> solution but your idea is great too!
I would have to test further to populate the list of mailers that require
setting the WrongEscape option (as it's labeled in the mbcico code.)
JC> Another confusing thing (and is partially responsible for how Mystic
JC> got it wrong originally) is that when you look up BinkP on Wikipedia
JC> it links to the old specifications released by the authors of Argus.
JC> If I remember correctly it was really difficult to even find FTS
JC> documentation when I was first implementing FTN into Mystic so these
JC> kind of links proved to be a pain point.
This is the big reason that the FTSC created the ftsc.org website.
JC> My testbed was Argus, IREX, and BinkD and \## was the only thing that
JC> worked with all of them as I recall, and it matches what Wikipedia
JC> says so thats what Mystic used back then...
If you ever need clarification on anything related to the FTSC, please don't
hesitate to netmail me.
JC> Unfortunately that is wrong as I later found Radius mailers that only
JC> supported \x## and I believe BinkIT falls into this category as well.
I would have to test to be sure.
JC> I think in hindsight it might have been better for FTS to leave it as
JC> \## since legacy mailers used it and could not be updated, but it is
JC> what it is!
BinkD (the original implementation of BinkP) has always used \x## as far as I
know.
