TZUTC: -0800   
   MSGID: 55233.sync@1:103/705 2d74cd6b   
   REPLY: 55230.sync@1:103/705 2d74c746   
   PID: Synchronet 3.21a-Linux master/d39e01091 Nov 03 2025 GCC 12.2.0   
   TID: SBBSecho 3.31-Linux master/d39e01091 Nov 03 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: Re: NNTP(S) via Thunderbi   
     By: Gamgee to Accession on Fri Nov 07 2025 09:15 pm   
      
    > Yes, understood.  The "put" direction makes good sense to me.  I have a   
    > question about the "get" side though - What causes the BBS to know to   
    > pack up all the new messages into a QWK packet though?  Does just the   
    > act of requesting .qwk cause that to happen?   
      
   Yes, correct.   
      
    > I was thinking I'd   
    > have to somehow "tell" the BBS to create the new QWK packet, and *then*   
    > grab it with wget/ftp.   
      
   No, it happens on demand. The *.qwk file that appears in the FTP directory   
   listing is just a virtual file. A "get" (RETR) of the file actually signals   
   the sbbs event thread to create the packet, on demand, so there is a bit of   
   delay before the file transfer actually starts (which is fine).   
   --    
                                               digital man (rob)   
      
   Synchronet/BBS Terminology Definition #64:   
   POP3 = Post Office Protocol version 3   
   Norco, CA WX: 68.1øF, 71.0% humidity, 2 mph NW wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.31-Linux   
    * 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: 129/14 153/7715 154/110 218/0 1 215 601 610 700 840 860 880   
   SEEN-BY: 226/30 227/114 229/110 112 206 317 400 426 428 470 700 705   
   SEEN-BY: 266/512 280/464 291/111 301/1 320/219 322/757 342/200 396/45   
   SEEN-BY: 460/58 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426