TZUTC: -0800   
   MSGID: 53523.sync@1:103/705 2bf37199   
   REPLY: 50466.dove-syncdisc@12:1/2 2bf2ec01   
   PID: Synchronet 3.20c-Linux master/4914fa1d7 Jan 17 2025 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/93c48471e Jan 18 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: imsg on incoming echomail   
     By: deon to Digital Man on Sun Jan 19 2025 11:32 pm   
      
    > When I connected and saw that idle node still logged in, I used ;spy 1 to   
    > check to see if anything was displayed. I didnt expect anything to display   
    > since the 0001.msg file was blank (and nothing was).   
      
   spy only shows *new* text sent to the client on that node however. If the    
   message was already read/displayed (before you started spying), you wouldn't   
   see it.   
      
    > And the fact that no *.msg files changed, means that the message was never   
    > sent nor consumed right?   
      
   Normally, yes, but not if something just read and truncated the .msg file.   
   --    
                                               digital man (rob)   
      
   This Is Spinal Tap quote #10:   
   Dozens of people spontaneously combust each year... just not widely reported.   
   Norco, CA WX: 55.8øF, 70.0% humidity, 3 mph WSW wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 110 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 291/111 292/8125 301/1 310/31 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 256 1124 467/888   
   SEEN-BY: 633/280 712/848 770/1 902/26 5020/400 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426