Ol> additional noise and an opportunity for misconfiguration. We know the
 Ol> few mailers that cannot cope with the standard \x##. I believe they all
 Ol> send the M_NUL VER command. Why not auto-detect the broken mailer and
 Ol> switch to the incorrect escape \## automatically?

I don't want to get too far off topic here so I will end with this and show what I ended up doing on the Mystic side to clarify for everyone here...

I agree with you about additional noise and misconfiguration - we seem to share a similar opinion on bloated configurations!  But since I already had it as an option, I went back and added an "Auto" option based on your suggestion.

Auto will be the default moving forward.  If you have any suggestions or feedback on this shoot me a netmail or in MYSTIC echo or something.  I don't want to clutter up BINKD with Mystic stuff...

If BINKD wants to add something similar to help support legacy mailers then great, if not then so be it! :)

 + Mystic's BINKP server now has a default "Escape mode" option which will
   apply to any unknown connections that do not have a configuration in the
   Echomail nodes.  Echomail nodes also have their own individual setting for    this in the node editor.

   This setting determines how Mystic will escape special characters in
   filenames and defaults to the Auto setting.

   When set to Auto, Mystic will automatically try to determine the escape
   mode by using the VERSION frame sent by the mailer.  If no version frame
   is found, Mystic will use FTS standard modern \x## escape mode.

   When set to Legacy, Mystic will use the \## format of file escaping which
   is used in some legacy mailers such as Argus, Internet Rex, and older
   versions of Mystic.

   When set to Modern, Mystic will use the \x## format which is preferred or
   even required by some newer mailers such as BinkD, Radius, and BinkIT.

... Computers are not intelligent. They only think they are.

--- Mystic BBS v1.12 A48 2022/01/19 (Windows/32)