PH> Using BinkD (running Linux) as the mailer.. I noticed some Mystic nodes
PH> polling in were having this issue:
This seems to be related to a long standing issue with BinkD escaping filenames
incorrectly. You'll have to get it fixed in BinkD.
A47 has a workaround for the BinkD bugs but A46 would not.
PH> v1.0.2.26.zip as MyGUI\x20v1.0.2.26.zip (1669424)
This is not a properly escaped filename being sent by BinkD as it does not
follow the BINKP protocol specifications for filename escaping:
5.2 File Name Issues
--------------------
In Mailer-parseable commands that contain a file name, the file name MUST NOT
include a whitespace (ASCII value 20 hex). The file name SHOULD NOT include
symbols other than alphanumeric (A-Z,a-z,0-9) and safe characters as defined
below in BNF. All other symbols are to be considered unsafe and SHOULD be
escaped in the form of two hexadecimal digits preceded by a backslash (e.g. a
whitespace must be transmitted as "\20").
filename = *pchar
pchar = unreserved | escape
unreserved = ALPHA | DIGIT | safe
safe = "@" | "&" | "=" | "+" | "%" | "$" | "-" | "_" |
"." | "!" | "(" | ")" | "#" | "|"
escape = "\" HEX HEX
... Everyone smiles in the same language.
--- Mystic BBS v1.12 A48 2022/01/10 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)
|
