TZUTC: -0800   
   MSGID: 55701.sync@1:103/705 2dd39375   
   REPLY: 55699.sync@1:103/705 2dd36659   
   PID: Synchronet 3.21b-Linux master/9af0a2196 Jan 17 2026 GCC 12.2.0   
   TID: SBBSecho 3.34-Linux master/9af0a2196 Jan 17 2026 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: Message Base Question   
     By: Mortar to Digital Man on Sun Jan 18 2026 03:52 pm   
      
    >   Re: Message Base Question   
    >   By: Digital Man to Tom Moore on Sat Jan 17 2026 19:28:34   
    >   
    >  > The date/time stamps on messages aren't very accurate (especially   
    >  > considering different timezones).   
    >   
    > Funny this comes up.  I have my msg. pointers set to see msgs. for just the   
    > last six months.  I was reading a bunch of msgs. yesterday and amongst the   
    > 2026 msgs. came several 2020 msgs, then back to the present.  Weird.   
      
   Message pointers determine what message you'll see in a new-scan based on   
   their *import* date/time, not the date/time they were supposedly written   
   (which is the date/time shown in the message header to users). So, not weird   
   really. Someone just dumped some old messages into a network, it happens a lot.   
   --    
                                               digital man (rob)   
      
   This Is Spinal Tap quote #12:   
   Nigel Tufnel: Well, I don't know - wh-wh-... what're the hours?   
   Norco, CA WX: 72.2øF, 36.0% humidity, 5 mph WSW wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.34-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 129/14 153/7715 154/110 218/0 1 215 601 700 840 860 880 226/30   
   SEEN-BY: 227/114 229/110 112 134 206 317 400 426 428 470 700 705 266/512   
   SEEN-BY: 280/464 291/111 301/1 320/219 322/757 342/200 396/45 460/58   
   SEEN-BY: 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426