TZUTC: -0500   
   MSGID: 73682.sync@723:320/1 2cdb6f75   
   REPLY: 54578.sync@1:103/705 2cda2c1f   
   PID: Synchronet 3.20a-Linux master/acc19483f Apr 26 202 GCC 12.2.0   
   TID: SBBSecho 3.28-Linux master/e2705e616 Jul 05 2025 GCC 12.2.0   
   BBSID: CAPCITY2   
   CHRS: CP437 2   
   FORMAT: flowed   
   -=> Digital Man wrote to Dumas Walker <=-   
      
    > Synchronet BBS for Linux Version 3.20a   
    > Revision a Apr 27 2024 09:49 SMBLIB 3.00 GCC 12.2.0   
      
    DM> I'd upgrade to v3.20d or later.   
      
   Noted.  I upgraded my test system to the latest yesterday to try it out.   
      
    > For some reason your board loses me from time to time. It seems random.   
      
    DM> User's message scan pointers are stored in data/user/.subs,   
    DM> if you want to monitor changes to the user's file, look for any   
    DM> corruption, etc.   
      
   Also noted.   
      
    DM> Also, if the user is logging on to multiple nodes or services (e.g.   
    DM> web, nntp, ftp, mail, and telnet, ssh, or rlogin) concurrently, that   
    DM> can cause race-conditions and user-surprises with message scan   
    DM> pointers. That'd be something to keep an eye on as well.   
      
   FYI a couple of things I have determined since:   
      
   (1) per the logs, both times the user logged on yesterday morning, when   
   they supposedly got the bad packet and when they got the second (*) one,   
   Synchronet reports that it scanned 55 areas.  Based on what it says when I   
   download a packet, and when another user downloads one, I am pretty sure   
   that is the number of areas joined and it was consistent.   
      
   (2) I asked then to describe how they determined there was an issue.   
   Multimail has a feature where you can press "L" and rotate through a   
   listing of All Areas, Active Areas (the ones with messages), and Subscribed   
   Areas.  Not sure if this is a Multimail issue, or maybe just something with   
   the Synchronet packets, but he says the "Subscribed" list is where he sees   
   that there are message areas missing.   
      
   I told him I was not sure that the "Subscribed" feature of Multimail was   
   accurate.  On my packets, for example, that feature doesn't work at all.  I   
   trust the "55 areas" info that Synchronet is reporting in the logs over   
   what Multimail is reporting.   
      
   (*) in the second packet, they had managed to reset their msg pointers so   
   no comparison in packet size would be valid there.   
      
      
      
      
      
   ... Spelling is a sober man's game   
   --- MultiMail/DOS v0.52   
    þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP   
    * 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/206 317 400 426 428 550 700 705 240/1120 5832 263/1 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 8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426