The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: gtaylor@tnetconsulting.net (Grant Taylor)
Subject: [TUHS] Old Usenet newsreader source code?
Date: Tue, 8 May 2018 15:56:49 -0600	[thread overview]
Message-ID: <fefdad47-8c8b-4f4f-c093-162c31f28100@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20180508200135.47C7B156E510@mail.bitblocks.com>

On 05/08/2018 02:01 PM, Bakul Shah wrote:
> Back in 1989 timeframe I used to get a pretty complete feed via uucp and 
> maintain locally with cnews. Recently I tried using "fetchnews" recently 
> for that purpose (for the groups I want) since eternal-september is a 
> bit slow but something went wrong.

Do you want a UUCP (bag) feed again?

I provided UUCP "bag" feed to one of my peers on the first server I ran. 
  I'd be happy to do so again.

  - UUCP "bag" files pushed / pulled via SCP / SFTP.
     - Could probably be done over email too.
  - UUCP over SSH
  - UUCP over TCP port 540)
  - Secure UUCP TCP port 4031)

Obviously:

  - NNTP over TCP port 119
  - Secure NNTP over TCP port 563

I'm also willing to hear about other creative options too.

  - VPN
     - IPSec
     - SSL / TLS
     - WireGuard
     - OpenVPN



-- 
Grant. . . .
unix || die

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3982 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180508/4ee4af82/attachment-0001.bin>


  reply	other threads:[~2018-05-08 21:56 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 16:25 Seth Morabito
2018-05-08 16:36 ` Larry McVoy
2018-05-08 16:43   ` Warner Losh
2018-05-08 17:06   ` arnold
2018-05-08 17:27     ` Dan Cross
2018-05-08 17:42       ` Andy Kosela
2018-05-08 21:27         ` [TUHS] Old Usenet / local communitites Mike Markowski
2018-05-08 17:53       ` [TUHS] Old Usenet newsreader source code? Seth Morabito
2018-05-08 18:28         ` Grant Taylor
2018-05-08 18:35         ` Arthur Krewat
2018-05-08 18:45           ` Warner Losh
2018-05-08 19:00           ` Lyndon Nerenberg
2018-05-08 19:09             ` Grant Taylor
2018-05-08 19:11             ` Arthur Krewat
2018-05-08 21:50               ` Grant Taylor
2018-05-08 21:54                 ` Larry McVoy
2018-05-08 21:58                   ` Grant Taylor
2018-05-08 22:22               ` Henry Bent
2018-05-08 22:32                 ` Arthur Krewat
2018-05-08 22:59                   ` Henry Bent
2018-05-09  2:01                     ` Michael Parson
2018-05-09  1:55                 ` Michael Parson
2018-05-08 20:01             ` Bakul Shah
2018-05-08 21:56               ` Grant Taylor [this message]
2018-05-08 20:54             ` Lyndon Nerenberg
2018-05-08 19:05           ` Grant Taylor
2018-05-08 19:15             ` Arthur Krewat
2018-05-08 19:35               ` Grant Taylor
2018-05-08 19:23             ` Steve Nickolas
2018-05-08 19:29               ` Grant Taylor
2018-05-09  0:46                 ` Steve Nickolas
2018-05-08 19:26         ` Ron Natalie
2018-05-08 19:48           ` Grant Taylor
2018-05-08 20:54           ` Daniel Camolês
2018-05-08 22:55             ` Grant Taylor
2018-05-08 23:16               ` Lyndon Nerenberg
2018-05-08 23:18                 ` Henry Bent
2018-05-08 23:21                   ` George Michaelson
2018-05-08 23:25                   ` Grant Taylor
2018-05-08 23:22                 ` Grant Taylor
2018-05-08 23:37                   ` Grant Taylor
2018-05-09  0:54                 ` Steve Nickolas
2018-05-08 17:09   ` Clem Cole
2018-05-08 16:53 ` Arthur Krewat
2018-05-08 17:01   ` Seth Morabito
2018-05-08 19:41 ` Dave Horsfall
2018-05-08 21:49 ` Jeremy C. Reed
2018-05-08 23:39 ` John Labovitz
2018-05-09  0:08   ` Jeremy C. Reed
2018-05-09  0:11     ` Jeremy C. Reed
2018-05-09  0:42       ` Warren Toomey
2018-05-09  0:31   ` Bakul Shah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fefdad47-8c8b-4f4f-c093-162c31f28100@spamtrap.tnetconsulting.net \
    --to=gtaylor@tnetconsulting.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).