TZUTC: 1100   
   MSGID: 50473.dove-syncdisc@12:1/2 2bf3c63c   
   REPLY: 53522.sync@1:103/705 2bf370b8   
   PID: Synchronet 3.20c-Linux master/c0305b87e Jan 19 2025 GCC 10.2.1   
   TID: SBBSecho 3.23-Linux master/c5fa2af29 Jan 19 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: ALTERANT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: imsg on incoming echomail   
     By: Digital Man to deon on Sun Jan 19 2025 01:07 pm   
      
   Howdy,   
      
    > I realize you think you have evidence to the contrary, but I'm skeptical.   
      
   OK, so yesterday I rebuilt sync from commit c03035b87e   
      
   When I started it, I did the same thing, send a message, disconnect from the   
   network, reconnect a few mins later - and there was a notification.   
      
   2025-01-20 08:26:32 Successfully notified recipient (user #1)   
   2025-01-20 08:57:54 Successfully notified recipient (user #1)   
      
   Stumped.   
      
   So this afternoon I did the same thing again (so 7ish hours later), and no   
   notification (one was expected - a Scan all to me showed it.)   
      
   -rw------- 1 root root  82 Jan 20 12:24 msgs/0001.last.msg   
   -rw------- 1 root root  71 Jan 20 09:39 msgs/0001.last.0.msg *   
   -rw------- 1 root root 164 Jan 20 08:40 msgs/0001.last.1.msg   
   -rw------- 1 root root  71 Jan 20 08:29 msgs/0001.last.2.msg *   
   -rw------- 1 root root  71 Jan 20 08:16 msgs/0001.last.3.msg *   
      
   (The files with size 71 are my test messages, the other two are triggered by   
   you sending me messages. The last one .3.msg I didnt have debugging on, so no   
   corresponding sbbsecho.log message.)   
      
   I would have expected the files to be updated as of 14:30:22 which is when the   
   new message came in to me, which should have triggered a notification.   
      
   Here is the sbbsecho run for the incoming message that was to me (another   
   packet arrived at the same time, that didnt have echomail addressed to me.)   
      
   2025-01-20 14:30:22 SBBSecho 3.23-Linux master/c0305b87e Jan 19 2025 GCC   
   10.2.1 (PID 9135) invoked with options: -ce   
   2025-01-20 14:30:22 Configured: 7 archivers, 52 linked-nodes, 13 echolists   
   2025-01-20 14:30:22 NetMail directory: /opt/sbbs/data/netmail/   
   2025-01-20 14:30:22 Secure Inbound directory: /opt/sbbs/fido/inbound/   
   2025-01-20 14:30:22 Non-secure Inbound directory: /opt/sbbs/fido/nonsecure/   
   2025-01-20 14:30:22 Outbound (BSO root) directory: /opt/sbbs/fido/outbound   
   2025-01-20 14:30:22 Read 335 areas from ../data/areas.bbs   
   2025-01-20 14:30:22 Bad-echo area: local-badarea   
   2025-01-20 14:30:22 Read 14 areas from ../data/badareas.lst   
   2025-01-20 14:30:26 Read 395 echo statistics from ../data/echostats.ini   
      
   2025-01-20 14:30:26 Importing /opt/sbbs/fido/inbound/000a20b7.pkt (type 2e,   
   2.1KB) from 3:633/2744 to 3:633/509   
   2025-01-20 14:30:26 ERROR 1 (smb_addmsg duplicate TEXT_BODY: hash found in   
   message #12) line 3792 adding message to fdn_bbs_ads   
   2025-01-20 14:30:26 BBS_ADS Duplicate message from paul lee (1:105/420) to   
   All, subject: 2o fOr beeRS bbS   
   2025-01-20 14:30:26 Deleting /opt/sbbs/fido/inbound/000a20b7.pkt (from line   
   6310)   
      
   2025-01-20 14:30:26 Importing /opt/sbbs/fido/inbound/000a20bc.pkt (type 2e,   
   1.8KB) from 10:1/1 to 10:1/4   
   2025-01-20 14:30:26 Creating outbound packet from 10:1/4 to 10:999/900:   
   /opt/sbbs/temp/sbbsecho/678dc352.pkt   
   2025-01-20 14:30:26 New password-protected packet (type 2.2) created for   
   linked-node: 10:999/900   
   2025-01-20 14:30:26 Adding PVT_TEST message from Clearing Houz (10:1/1) to   
   packet for 10:999/900: /opt/sbbs/temp/sbbsecho/678dc352.pkt   
   2025-01-20 14:30:26 Added PVT_TEST message from Clearing Houz (10:1/1) to   
   packets for 1 links (exceptions: 1 seen)   
   2025-01-20 14:30:26 Deleting /opt/sbbs/fido/inbound/000a20bc.pkt (from line   
   6310)   
   2025-01-20 14:30:26 Imported:     1 msgs                         pvt_test <-   
   PVT_TEST   
   2025-01-20 14:30:26 Duplicate:    1 detected in BBS_ADS   
   2025-01-20 14:30:26 Imported:     1 msgs total   
      
   2025-01-20 14:30:26 Finalizing outbound packet from 10:1/4 to 10:999/900:   
   /opt/sbbs/temp/sbbsecho/678dc352.pkt   
   2025-01-20 14:30:26 Node (10:999/900) successfully locked via: .   
   /fido/outbound.00a/03e70384.bsy   
   2025-01-20 14:30:26 Sending packet (/opt/sbbs/temp/sbbsecho/678dc352.pkt,   
   1.8KB) from 10:1/4 to 10:999/900   
   2025-01-20 14:30:26 Moving packet for 10:999/900: /opt/sbbs/temp   
   sbbsecho/678dc352.pkt to ../fido/outbound.00a/678dc352.pkt   
   2025-01-20 14:30:26 Deleting /opt/sbbs/temp/sbbsecho/678dc352.pkt (from line   
   3009)   
   2025-01-20 14:30:26 File (../fido/outbound.00a/678dc352.pkt, 1.8KB) for   
   10:999/900 added to BSO/FLO file: ../fido/outbound.00a/03e70384.clo   
   2025-01-20 14:30:26 Touching outgoing semfile: ../data/binkout.now   
   2025-01-20 14:30:26 Writing 14 areas to ../data/badareas.lst   
   2025-01-20 14:30:26 Deleting ../fido/outbound.00a/03e70384.bsy (from line 3169)   
   2025-01-20 14:30:26 Deleting /opt/sbbs/ctrl/sbbsecho.bsy (from line 3175)   
   2025-01-20 14:30:26 SBBSecho (PID 9135) exiting with error level 0, Packets(2   
   imported, 1 sent), EchoMail(1 imported, 0 exported)   
      
   I would have expected something from the logging you added right?   
      
      
   ...ëîåï   
      
   ---   
    þ Synchronet þ AnsiTEX bringing back videotex but with ANSI   
    * 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: 153/7715 154/110 218/0 1 215 601 700 840 860 880 226/30 227/114   
   SEEN-BY: 229/110 114 206 317 400 426 428 470 550 700 705 266/512 280/464   
   SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280   
   SEEN-BY: 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426