TZUTC: -0500   
   MSGID: 74749.sync@723:320/1 2dd4a4d2   
   REPLY: 55705.sync@1:103/705 2dd3b26f   
   PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0   
   TID: SBBSecho 3.34-Linux master/f6746e937 Jan 19 2026 GCC 12.2.0   
   BBSID: CAPCITY2   
   CHRS: CP437 2   
   FORMAT: flowed   
   > Except that messages are imported or sorted by "written date".   
      
   FWIW, sbbsecho seems to do a lot better job keeping messages in such an   
   order where, when read in the order posted, a discussion can be followed vs.   
   some other tossers/tosser-shims I have used in the past.   
      
   I rarely notice ftn messages read in sequence seeming out of order here.   
   Usenet groups are about the only place I might notice it, and I suspect   
   that is something that happens before sbbsecho gets hold of the messages.   
      
      
    * SLMR 2.1a * Only sheep make baaaad puns.   
   ---   
    þ Synchronet þ CAPCITY2 * Capitol City Online   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 129/14 153/757 7715   
   SEEN-BY: 154/10 30 110 203/0 218/700 221/0 226/30 227/114 229/110   
   SEEN-BY: 229/112 134 206 317 400 426 428 470 700 705 240/1120 5832   
   SEEN-BY: 263/1 266/512 280/464 5003 5006 291/111 292/8125 301/1 310/31   
   SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58   
   SEEN-BY: 460/256 1124 633/280 712/848 770/1 902/26 5020/400 8912 5054/30   
   SEEN-BY: 5075/35   
   PATH: 103/705 280/464 460/58 229/426