TZUTC: -0600
MSGID: 26609.fido_synchron@1:135/115 2d74ee22
REPLY: 723:1/1 690f4338
PID: Synchronet 3.21a-Linux master/955e50fea Aug 10 2025 GCC 14.2.0
TID: SBBSecho 3.29-Linux master/955e50fea Aug 10 2025 GCC 14.2.0
BBSID: PALANTIR
CHRS: CP437 2
FORMAT: flowed
-=> Accession wrote to Gamgee <=-

 > 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?  I was thinking I'd
 > have to somehow "tell" the BBS to create the new QWK packet, and *then*
 > grab it with wget/ftp.

 Ac> I think either when you connect or when there is a new message(s),
 Ac> Synchronet creates the QWK packet and puts it in that location
 Ac> automatically. I'm not sure on exactly how it works, but it's there
 Ac> every time I grab it, and it's an updated packet each time.

Okay, cool.

 Ac> Rob would have to explain that better, but I'll just call it 'magic'.
 Ac> :)

He did explain it!  Thank you again.




... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.29-Linux
 * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
SEEN-BY: 1/120 18/0 103/705 104/119 105/81 106/201 114/10 116/116
SEEN-BY: 123/0 25 180 525 755 3001 3002 124/5016 128/187 129/14 215
SEEN-BY: 135/0 115 220 230 240 363 366 385 390 391 153/757 7715 154/10
SEEN-BY: 154/30 50 110 700 203/0 218/700 220/6 20 30 90 221/0 6 222/2
SEEN-BY: 226/18 30 44 50 227/114 229/110 112 206 310 317 400 426 428
SEEN-BY: 229/470 700 705 240/1120 5832 250/1 263/1 266/512 275/1000
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 633/267 280 384
SEEN-BY: 633/410 414 418 420 422 2744 712/848 1321 770/1 902/26 2320/105
SEEN-BY: 3634/0 12 24 27 57 58 60 119 5020/400 5075/35
PATH: 135/115 3634/12 154/10 280/464 633/280 229/426