TID: FMail-lnx64 2.3.2.4-B20240523   
   RFC-X-No-Archive: Yes   
   TZUTC: 0200   
   CHRS: CP850 2   
   PID: GED+LNX 1.1.5-b20240604   
   MSGID: 2:280/464 6822f28f   
   REPLY: 52315.syncprog@1:103/705 2c88941c   
   Hi Rob,   
      
   On 2025-05-12 17:26:41, you wrote to Git commit to main/sbbs/master:   
      
    RSoW> Log Message:   
    RSoW> Allow a "max message count" to be specified in AreaMgr "rescan"   
    RSoW> requests   
      
    RSoW> - The -R option (in the subject), can now include a message count   
    RSoW>   i.e. -R=   
    RSoW>   I don't think this follows any existing area manager example usage,   
   but I   
    RSoW>   figured as long as we support a -R option, -R= makes sense.   
    RSoW> - The %RESCAN function (in the body) can now include a message count   
    RSoW>   i.e. %RESCAN [area-tag] [R=]   
    RSoW>   This mimics the Mystic area manager usage, though we don't yet support   
    RSoW>   a "D=days" option.   
      
   There is a FTSC document which describes rescanning options for Area Managers:   
   http://ftsc.org/docs/fsc-0057.003 paragraph 5.   
      
   It's in the reference library (I don't know why it didn't make it as a   
   standard). But I think it would be smart to follow it.   
      
      
   Bye, Wilfred.   
      
   --- FMail-lnx64 2.3.2.4-B20240523   
    * Origin: FMail development HQ (2:280/464)   
   SEEN-BY: 10/0 1 102/401 103/1 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 153/757 7715 154/10 30 110 203/0 214/22 218/0 1 215 700 810   
   SEEN-BY: 221/0 226/30 227/114 229/110 114 206 317 400 426 428 470   
   SEEN-BY: 229/550 700 705 240/1120 5832 263/1 266/512 280/464 5003   
   SEEN-BY: 280/5006 291/111 292/8125 301/1 320/219 322/757 341/66 234   
   SEEN-BY: 342/200 396/45 423/120 460/58 467/888 633/280 712/848 770/1   
   SEEN-BY: 902/26 5020/400 5075/35   
   PATH: 280/464 103/705 218/700 229/426