From mboxrd@z Thu Jan  1 00:00:00 1970
From: bakul@bitblocks.com (Bakul Shah)
Date: Wed, 09 May 2018 22:03:34 -0700
Subject: [TUHS] UUCP "bag" files
In-Reply-To: Your message of "Wed, 09 May 2018 22:53:01 -0600."
 <042d9aff-82df-d267-e585-3dfe57b06252@spamtrap.tnetconsulting.net>
References: <04c44cba-fefe-b5c6-d683-618ed3ddb0cb@spamtrap.tnetconsulting.net>
 <9D7839FC-A3EB-4211-887D-BCE67229E1D6@orthanc.ca>
 <042d9aff-82df-d267-e585-3dfe57b06252@spamtrap.tnetconsulting.net>
Message-ID: <20180510050341.64DDC156E510@mail.bitblocks.com>

On Wed, 09 May 2018 22:53:01 -0600 Grant Taylor via TUHS <tuhs at minnie.tuhs.org> wrote:
> 
> On 05/09/2018 09:51 PM, Lyndon Nerenberg wrote:
> > What are they to begin with?  Having run some "major" UUCP hubs in the
> > day, I have no clue what a UUCP "bag" is ...
> 
> I see them in the context of Usenet via UUCP, so rnews.
> 
> The best that I can tell is that they are simply the messages that need
> to be sent written into a single file that is then transferred via some
> mechanism, ftp being a common one.
> 
> It looks like it might be the output of nntpsend or send-nntp.  Or
> perhaps output of downstream / related UUCP commands.
> 
> I often see it mentioned in close proximity of DNews.