REPLY: 5043.mbse@1:103/705 23fb55e7   
   MSGID: 1:153/757@fidonet 5f964b77   
   CHRS: UTF-8 2   
   TZUTC: -0700   
   TID: MBSE-FIDO 1.0.7.18 (GNU/Linux-x86_64)   
   Hello Rob,   
      
    RS> The QWK format actually has its own unique line-ending sequence: 227   
    RS> (0xE3). I don't know the history/reason why (ASCII 10, '\n', seems   
    RS> like it would have worked fine). According to one QWK spec, this was   
    RS> to "save space", but that doesn't really make sense. Anyway, MultiMail   
    RS> and (presumably) other QWK readers do not actually wrap text with   
    RS> CRLF, though perhaps they should. :-)   
      
   Multimail does seem to wrap message text with CRLF line endings, or maybe it's    
   the editor that does that. I can seem if I inspect messages in a BW reply    
   packet before uploading.   
      
    >> and I think MBSE does that with messages saved on the BBS also.   
      
    RS> Should be okay if it does. FidoNet messages are supposed to be '\r'   
    RS> terminated paragraphs (line-feeds are ignored), so where FidoNet is   
    RS> concerned, CRLF or CR should work fine.   
      
   I had a look at a message I posted in MBSE inside a .pkt that was waiting in    
   the outbound. It also had CRLF line endings although they may have been put    
   there by the editor also. That's not a problem on an 80x25 screen, it looks    
   good. If you look at that on a wider screen it'll still be wrapped for that 80    
   character wide terminal, unless your terminal can unwrap it for you.   
      
    >> I'm looking at these messages inside of .pkt files. These lines   
    >> start with a CRLF, it's completely out of place there.   
      
    RS> It should be fine. The only case where it would not be fine is control   
    RS> paragraphs (kludge lines) which must begin with a single CR (0x0D)   
    RS> character.   
      
   I'm not sure what a control paragraph should look like so I can't say if it is    
   correct or not.   
      
   Would you mind looking over this packet and tell us what you think? I think    
   you could explain what is happening, if anything better than I can.   
      
   http://trmb.ca/5f0abae3.pkt   
      
   This is a test message I wrote to myself from 757.2 to 757.3 and this is the    
   .pkt that MBSE created for 757.3. This packet contains (I think) uneeded and    
   unwanted CRLF's at the beginning of lines.   
      
   http://trmb.ca/d319271e.pkt   
      
   This is the input .pkt that was sent to 153/757 to forward on to 757.3 if you    
   would like to look. It contain CRLF's as you'd expect.   
      
   --- GoldED+/LNX 1.1.5-b20180707   
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)   
   SEEN-BY: 1/123 18/200 90/1 120/340 123/131 226/30 227/114 229/101   
   SEEN-BY: 229/275 424 426 452 550 664 1016 240/5832 249/206 317 400   
   SEEN-BY: 292/854 317/3 322/757 342/200 633/280   
   PATH: 153/757 221/6 154/10 280/464 229/101 426