On 14 Apr 2019 at 09:05a, mark lewis pondered and said...
 
 ml> that looks fine... it has forced hard-CRs at like 72 character widths if
 ml> i counted properly... t'would be better if they were not forced at all
 ml> but that can be taken care of later ;)

 ml>  PH> @PATH: 770/100 1 280/464 396/45 261/38 3634/12
 ml> 
 ml> the one system we were looking at is not in the above path this time...

OK so I'm using the latest public release of Mystic and sent my original post
via 3:770/1 which we are saying is not doing anything to content. So if I
understand you right you're (and others?) are happy with the way my test post
came across to you - right? :)

But.. we're also wondering about another system (running Mystic right? but
perhaps earlier version?) that may be adding something to the way content is
then displayed after packets pass though it.

Do I have that summarized correctly? Al?

Best, Paul

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)