On 2019 May 01 12:51:38, you wrote to Nancy Backus:

 MK> That particular bbs would be substituting 0x0d for 0x8d while the rest are
 MK> stripping the 0x8d

FWIW1: there are two places where 0x8d may be acted on...
  1. the tosser may strip by ignoring completely and skipping
  2. the BBS may strip or convert to 0x0d while displaying the message
     or when packaging it for offline mail

FWIW2: sbbsecho, the FTN tosser for Synchronet BBS, has just added the option
to strip or not 0x8d characters... the default is to leave them alone and
ignore them by not reacting to them at all... they are copied as they are and
applies to both echomail and netmail... this is the good (proper?) form of
ignoring for this situation 

----- snip -----
  http://cvs.synchro.net/commitlog.ssjs#38249

Log Message:
Add option to strip so-called "Soft CRs" (0x8D) from incoming messages.
The default is off (no stripping). Previously, Soft-CRs were always stripped,
but this behavior is now seen as an anachronism as CP437 char 141 is an
important non-English laguage character and used as such in FidoNet msgs.
----- snip -----

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... SystemD would be a good OS but it needs a decent init system.
---
 * Origin:  (1:3634/12.73)