Subj : Problem with filenames containing spaces
To   : Paul Hayton
From : Oli
Date : Thu Jan 13 2022 11:13 pm

Paul wrote (2022-01-14):

 PH> On 13 Jan 2022 at 10:15a, Stas Mishchenkov pondered and said...

 PH>>> This is not a properly escaped filename being sent by BinkD as
 PH>>> it doe not follow the BINKP protocol specifications for
 PH>>> filename escaping:

 SM>> http://ftsc.org/docs/fts-1026.001

 PH> Hi Stas

 PH> I am not a developer so am unsure what it is you are saying by posting
 PH> this reply?

Like it's always the same. It's never Mystic's problem, the others are doing it wrong. (Why should the guru read the fucking manual? Why should he ask for advice? He always knows better ...)

As far as I understand it, the quote in your mail was from an older spec and not the most recent FTSC. Mailers must send \x20, but should accept \20 too. Sending \20 is a bug in Mystic, but most mailers would accept it. Not understanding \x20 was a bug in Mystic in previous versions.

---
 * Origin: Birds aren't real (2:280/464.47)

.