Path: utzoo!utgpu!NDSUVM1!NETNWS-L Date: Tue, 20 Feb 90 11:52:00 EST Reply-To: NETNWS-L Netnews List Sender: NETNWS-L Netnews List From: Linda Littleton Subject: Re: Unix folks unhappy about bit groups X-To: tower@bu-it.bu.edu X-cc: NETNWS-L@NDSUVM1.BITNET, nntp-managers@ucbarpa.Berkeley.EDU, To: UofToronto LAN redistribution References: tower AT bu-it.bu.edu -- Wed, 14 Feb 90 00:21:01 EST Message-ID: <90Feb21.021830est.57512@ugw.utcs.utoronto.ca> Newsgroups: list.netnws-l Distribution: ut Approved: devnull@gpu.utcs.toronto.edu tower@bu-it.bu.edu (Leonard H. Tower Jr.) wrote: >(about bit.listserv.* groups being gated to Usenet groups) >If the Message-Id:'s are the same in each newsgroup (generally the >case), the traffic is split between the two groups (that is, each >messaeg ends up in only one of the groups). This is very confusing to >users who wonder about the missing messages. >When the Message-Id:'s are not the same in each group, the sites >getting both groups get twice the traffic wasting network bandwidth, >cpu and disk space. >Have the gateways involved cross post once to both the bit.listserv >name and the mainstream name. For example: > Newsgroups: bit.listserv.asm370,comp.lang.asm370 > Followup-To: bit.listserv.asm370,comp.lang.asm370 > (The Followup line is needed to avoid some Followup's being sent to >only one group (some news readers/posters do this). Agreed. This is the way to go. Our software cannot handle this currently, but could be changed. >The people at the nntp managers BOF at USENIX liked this solution, and >ask Erik to contact Bill Verity and work at: > - getting the gateway software modified to do this. Either >ucbvax's or the bitnet or both. I will modify ours. > - arranging who gates which mailing lists. Good idea. Let me know which ones to turn off. >There have recently been almost a dozen new bit.listserv.all groups >created by JIM@AUVM.BITNET. Will psuvax1.cs.psu.edu handle the >forwarding for these properly? Anyone using our software and adding groups has been asked to post the info to bit.listserv.netnws-l. From there, I pick it up and add it to a list here, which eventually goes out in a checkgroups.