TZUTC: -0500
MSGID: 74320.sync@723:320/1 2d748f96
REPLY: 55214.sync@1:103/705 2d72c99e
PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
TID: SBBSecho 3.31-Linux master/d39e01091 Nov 03 2025 GCC 12.2.0
BBSID: CAPCITY2
CHRS: CP437 2
FORMAT: flowed
>  > If a recipient isn't found, "All" seems like a sensible default. Are
>  > you saying the failure to find a recipient is a bug? Feel free to
>  > play with it and offer up a patch if you have one.

>  ne> I like the Synchronet "You touch it, you own it" model :)

> I thought NNTP didn't have a to: field?

In the early 1990s when I first started using Usenet, IIRC just about every
(if not all) messages ported over to my BBS were "To: All" and responses
from the BBS side, while showing a To: receipient locally, were posted to
usenet as if "To: All."

Now, most of the messages that come across the Usenet gates have a
receipient listed.  Very few replies still come across as "To: All."

Not sure if that answers you question or not.  ;)


 * SLMR 2.1a * Thesaurus: prehistoric reptile with a great vocabulary.
---
 þ Synchronet þ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
 * 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