TZUTC: -0700   
   MSGID: 52171.syncprog@1:103/705 2c68aa32   
   PID: Synchronet 3.21a-Linux master/85dea2614 Apr 11 2025 GCC 12.2.0   
   TID: SBBSecho 3.24-Linux master/a20ba6050 Apr 11 2025 GCC 12.2.0   
   BBSID: VERT   
   CHRS: ASCII 1   
   https://gitlab.synchro.net/main/sbbs/-/commit/42db8f953a79240c649f56aa   
   Modified Files:   
   	src/sbbs3/ftpsrvr.c mailsrvr.c main.cpp mqtt.c mqtt.h services.c websrvr.c   
   Log Message:   
   Store/reuse each server's client highwater mark for MQTT publishing   
      
   Although we always republished "0" as the client highwater mark (e.g. upon   
   server startup and recycle), the internally tracked highwater marked is *not*   
   reset (to zero) upon recycle, so may not have been republished (with a   
   non-zero) value until/unless the internal highwater mark was exceeded.   
      
   So now, the value we publish upon recycle will be same value as the internally   
   tracked client highwater mark.   
      
   This fixes issue #910   
   --- SBBSecho 3.24-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 263/1   
   SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 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