From: dsg@mitre.org (David S. Goldberg)
Subject: Re: reading news over telnet
Date: 17 Aug 1999 16:37:38 -0400 [thread overview]
Message-ID: <m1blnba9m99.fsf@blackbird.mitre.org> (raw)
In-Reply-To: Toby Speight's message of "17 Aug 1999 20:22:02 +0100"
David> Whatever your sysadmin told you, your firewall isn't blocking
David> NNTP.
TS> Unless the telnet program he's using has some non-standard magic
TS> compiled into it (e.g. SOCKS support) that Emacs doesn't.
Good point. I haven't seen SOCKS used in so long I hadn't considered
it. If that's what he needs, then he probably can have gnus telnet
directly to the host at port 119 though I don't know exactly what
variables he'd need to set.
--
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org
next prev parent reply other threads:[~1999-08-17 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-17 14:33 Max Froumentin
1999-08-17 14:42 ` Max Froumentin
1999-08-17 15:04 ` Kai Großjohann
1999-08-17 18:14 ` Max Froumentin
1999-08-17 19:11 ` David S. Goldberg
1999-08-17 19:22 ` Toby Speight
1999-08-17 20:37 ` David S. Goldberg [this message]
1999-08-19 15:07 ` Max Froumentin
1999-09-24 18:27 ` Lars Magne Ingebrigtsen
1999-08-17 15:57 ` Sam Falkner
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=m1blnba9m99.fsf@blackbird.mitre.org \
--to=dsg@mitre.org \
/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).