TID: Mystic BBS 1.12 A43   
   MSGID: 3:770/100 796f667c   
   REPLY: 1:3634/12.73 5cb33009   
   TZUTC: 1200   
   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)   
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)   
   SEEN-BY: 15/2 18/200 57/0 123/1970 153/250 757 154/10 203/0 221/0   
   SEEN-BY: 226/17 229/107 354 426 452 1014 240/5832 249/206 317 400   
   SEEN-BY: 267/800 280/464 5003 310/31 317/2 3 322/757 342/200 393/68   
   SEEN-BY: 396/45 423/120 633/280 712/848 770/0 1 10 100 330 340 772/0   
   SEEN-BY: 772/1 210 500   
   PATH: 770/100 1 280/464 229/426