HDTenEightyP/NetNews huggingface dataset:
From: murphy@ufp.dco.dec.com (Rick Murphy)
Subject: Re: xrn: Changing "Overwrite Confirm" default.
Reply-To: murphy@ufp.dco.dec.com
Organization: Digital Equipment Corporation, Landover MD
Date: Mon, 28 Dec 1992 04:03:17 GMT


The attached context diff will get you what you want - effectively,
edit "save.c" and swap the order of the buttons in the dialog box.
	-Rick
diff -c save.c /tmp/save.c
*** save.c      Tue Sep 29 14:18:31 1992
--- /tmp/save.c Sun Dec 27 23:01:10 1992
***************
*** 356,363 ****
  {
      XEvent ev;
      static struct DialogArg args[] = {
-       {"Overwrite", overwriteHandler, (caddr_t) XRNsave_OVERWRITE},
        {"Append",    overwriteHandler, (caddr_t) XRNsave_APPEND},
        {"Abort",     overwriteHandler, (caddr_t) XRNsave_ABORT},
      };

--- 356,363 ----
  {
      XEvent ev;
      static struct DialogArg args[] = {
        {"Append",    overwriteHandler, (caddr_t) XRNsave_APPEND},
+       {"Overwrite", overwriteHandler, (caddr_t) XRNsave_OVERWRITE},
        {"Abort",     overwriteHandler, (caddr_t) XRNsave_ABORT},
      };


--
Rick Murphy, WA1SPT/4			Washington Open Systems Resource Center
Domain:  murphy@dco.dec.com -or- murphy@burfle.enet.dec.com
Bang:    decwrl!burfle.enet!murphy	"Somewhere between 30 and Death" -
Ding:	 (301) 918-5883				bumper sticker.
Disclaimer: This nonsense came from an AI program written in TECO. Ignore it.
Newsgroups: news.software.readers
From: kpc@pluto.arc.nasa.gov (k p c)
Subject: splitting newsgroups
Originator: kpc@zog.arc.nasa.gov
Reply-To: kpc@ptolemy.arc.nasa.gov
X-Newsgroups: news.groups,gnus.emacs.gnus
Organization: NASA Ames Research Center AI Research and Aero Branches;
	Sterling.
Date: Thu, 24 Dec 1992 10:03:44 GMT

i wrote this as a followup in news.groups but it might be relevant here.

i think "the endless splintering of newsgroups" is a GOOD thing.  the
problem is in news readers.  you should be able to combine small
newsgroups into custom-made virtual groups.

that way people who don't have time for the other splinters can read
the splinters they want to, and you, who want "cross-polination
(sic)", can have that too.  everybody wins since nobody has to comply
with the taxonomy/classification/ontology of others.

note that this allows the newsgroup equivalent of multiple inheritance
(directed acyclic graph instead of tree), and reduces arguments about
what hierarchy or subhierarchy a proposed newsgroup should go in.

the only reader that does anything close to this that i know of is nn.
i have been urging the gnus community to do it for gnus (a gnu emacs
newsreader written in lisp), but so far nobody's bitten yet (except
for one partial attempt called gnus-topic).

but other news readers will get it; it'll happen.  in the meantime, i
think we should split away without feeling guilty, even though it's a
pain sometimes.  change is in the nature of things; it's good for us
to accept that.

comments?
-- 
i'm open to comparing research career notes with other young cogsci people.
Newsgroups: news.software.readers
From: pat@gsfc.nasa.gov (patrick m. ryan)
Subject: tin insists on threading
Organization: Goddard Space Flight Center
X-Newsreader: TIN [version 1.1 PL8]
Date: Mon, 28 Dec 1992 18:15:08 GMT


	Has anyone had the problem with tin that it insists on
threading newsgroups even when the thread_arts attribute is
set to OFF?  For instance:

in ~/.tin/attributes:
newsgroup=rec.humor.funny
thread_arts=OFF

in ~/.tin/unthread
rec.humor.funny

Yet the index file is still showing up after my 'tin -u' job
runs.

	I'm running tin 1.1 PL8 on a Sun SPARC 10 under
SunOS 4.1.3.  I've RTFM'ed to no avail.  Any clues would
be appreciated.

	OBthanks: much thanks to Iain for a great newsreader.
I have now totally weaned myself off xrn.  If I ever get the
time (ha!), I'll tackle Xtin.

pat

--
"I have a cunning plan." -- Baldric
                                                             patrick m. ryan
     nasa / goddard space flight center / oceans and ice branch / hughes stx
                     pat@jaameri.gsfc.nasa.gov / zmpmr@charney.gsfc.nasa.gov
Xref: sparky news.software.readers:2617 news.software.b:3657
From: trsnyder@mcs.drexel.edu (Bob Snyder)
Newsgroups: news.software.readers,news.software.b
Subject: Re: DESIGN DISCUSSION: The reference line is deficient
Date: 31 Dec 92 15:37:53 GMT
Organization: ASCI

In article <1992Dec30.192721.2264@ssc.com> markz@ssc.com (Mark Zenier) writes:

   1) Some people see no use for Reference lines and discard them.
   The moderator of comp.dcom.telecom for one.

comp.dcom.telecom is a gateway for the Telecom Digest, a mailing list.
Reference lines are inappropriate for a mailing list.

   2) A significant portion of the net particpants use gateways to 
   lists or other nets, and other software, that doesn't have a clue 
   about References.

I would probably say a minority, and even fewer as public access unix sites
and shutdown gateways shift people over....

   3) Some people are forced to use strange posting methods that
   will create a new thread, especially if they have to type in
   a new Subject line.

There will always be some articles that just don't fit.  But if you set a
standard, these articles will dimish in numbers.  And once they are a
small minority, you could always set up a newsserver in fascist mode. :-)

Bob
From: Iain.Lea@anl433.uucp
Newsgroups: news.software.readers
Subject: Re: tin flame
Date: 3 Jan 93 15:42:23 GMT
Organization: TIN Support
X-Newsreader: TIN [version 1.1 BETA PL9]

Tim Pierce (twpierce@unix.amherst.edu) wrote:
:
: As to whether I do not adequately prepare my users, I will be more
: than happy to send you PostScript copies of the introductory
: documentation on Unix, Emacs, and tin that we have gone to great
: lengths to make available here.  That is, if you're interested.

Obviously your lengths don't go so far as to send me a copy!
Sweet, real sweet. I have expressly asked before for users docs.

Iain

--
NAMES  Iain Lea    Iain.Lea%anl433.uucp@Germany.EU.net
SNAIL  Siemens AG, ANL A433SZ, Gruendlacher Str. 248, 8510 Fuerth, Germany.
PHONE  +49-911-3089-407 (work) +49-911-331963 (home) +49-911-3089-290 (FAX)
From: Iain.Lea@anl433.uucp
Newsgroups: news.software.readers
Subject: Re: tin posts
Date: 3 Jan 93 15:43:31 GMT
Organization: TIN Support
X-Newsreader: TIN [version 1.1 BETA PL9]

Larry Cannell (cannell@ed8200.ped.pto.ford.com) wrote:
:
: Is there a way to configure tin to confirm that you really want to
: post an article?  I sometimes accidentally hit a 'w' when I really
: want to hit a 'q' and have to wait until it asks the final question
: before quitting out (that's after going into the editor).

Try hitting ESC at the first prompt.

Iain

--
NAMES  Iain Lea    Iain.Lea%anl433.uucp@Germany.EU.net
SNAIL  Siemens AG, ANL A433SZ, Gruendlacher Str. 248, 8510 Fuerth, Germany.
PHONE  +49-911-3089-407 (work) +49-911-331963 (home) +49-911-3089-290 (FAX)  
Newsgroups: nyx.misc,news.software.readers
From: mcochran@nyx.cs.du.edu (Mark A. Cochran)
Subject: Re: threading
X-Disclaimer: Nyx is a public access Unix system run by the University
	of Denver for the Denver community.  The University has neither
	control over nor responsibility for the opinions of users.
Organization: Um, err... I *know* I saw it here a few days ago...
Date: Mon, 28 Dec 92 17:20:48 GMT

In article <1992Dec28.145119.17196@mnemosyne.cs.du.edu> jfurr@nyx.cs.du.edu (JKF) writes:
>In article <1992Dec28.144102.16960@mnemosyne.cs.du.edu> aburt@mnemosyne.cs.du.edu (Andrew Burt) writes:
>>In <1992Dec28.125223.14403@mnemosyne.cs.du.edu> jfurr@nyx.cs.du.edu (JKF) writes:
>>
>>>Every day, the number of messages threaded gets larger.  It's as though
>>>there's a fixed point somewhere a week and some odd days past that gets
>>>used as a reference point and every message that has arrived since then
>>>gets threaded each time you re-enter a newsgroup.  Any day now it's going
>>>to sit there and thread thousands of messages when I go into some of the
>>>heavy-traffic newsgroups.
>>
>>Well, beats me.  I have "mthreads -a all" done twice an hour in crontab.
>
>Embarrassedly, I reply that I have no idea what that does... but what
>should we do next?  Start posting about the problem on news.software.readers
>or news.admin.technical?  What kind of news software does Nyx use?
>
I don't think we need to worry about it. One of the high traffic
groups I follow was up to threading 985 last night, and is back down
to the normal 2-4 today.
I suspect it was, as aburt suggested at once point, related to the
50,000+ messages that UUCP re-sent to us.

--
                  Mark Cochran          merlin@eddie.ee.vt.edu
These are the views of my employer. They also represent the views of
your employer, your government, the Church of your choice, and the
Ghost of Elvis. So there.
From: ci229@cleveland.Freenet.Edu (Andrew Miller)
Newsgroups: news.software.readers
Subject: Looking fo news reader manuals
Date: 21 Dec 1992 22:04:15 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Reply-To: ci229@cleveland.Freenet.Edu (Andrew Miller)
NNTP-Posting-Host: hela.ins.cwru.edu


Greetings,

Can anyone tell me where I can find manuals for the following news readers
(preferably encapsulated postscript):

	tin		rn
	trn		nn
	gnews		xrn

				T.I.A.,

				Andrew
-- 
------------------------------------------------------------
Andrew Miller               amiller@tasc.com
Newsgroups: news.software.readers,news.software.b
From: bruce@blilly.UUCP (Bruce Lilly)
Subject: Re: DESIGN DISCUSSION: The reference line is deficient
Organization: Bruce Lilly
Date: Fri, 1 Jan 93 23:58:27 GMT
Reply-To: lilb@sony.compuserve.com (Bruce Lilly)

In article <1993Jan01.045654.20651@clarinet.com>
(posted to news.software.readers,news.software.b)
brad@clarinet.com (Brad Templeton) wrote:

>The only way I can think of to specify this that doesn't break existing
>software is to define a syntax for message-ids that expands the current one.
>
>That syntax would probably be something like
>
>	<unique@site__CODE>
>
>Where the CODE is a our magic keyword, such as R for root, SR for
>mini-root and so on.

Any proposal that alters message-ids *will* break existing software.

The proposal would violate the RFCs (RFC822 as amended by RFC1123 in particular),
since the messade-id must contain a FQDN to the right of the @, and (e.g.)
clarinet.com_R doesn't meet that requirement since "com_R" isn't a valid
top-level domain (or a well-known, widely used pseudo-domain like bitnet
or uucp).

Fiddling with the local part of the message-id (the part to the
left of the @) would also be unpalatable, since existing software
may find it impossible to locate the article referenced by a modified
message-id, since that modified message-id doesn't match the unadorned
original message-id, which may be the only one known to the software in
question.

In short, I don't believe it is reasonable to tamper with message-ids.

I think that either a new header is needed, or a set of rules for ordering
and modifying the *list* of message-ids in a References header (without
altering the message-ids themselves in any way).  

For example:
(I could find no restriction on the number of References headers in RFC822 or RFC1123)
one might put the root message-id as the first message-id in the first
References header, followed by its children. Subsequent References headers
could be used to identify "mini-roots" (each one the first on its References
header). In other words, each References header identifies a node in a tree
structure (the first message-id), and the children of that node (the
remaining message-ids). The first References header identifies the root of
the tree.

Assuming somebody finds a reason to prevent multiple References headers, use
the References header for the root, and a new header (perhaps
X-Sub-References) for other nodes, and permit multiple instances of the new
header.
-- 
	Bruce Lilly		blilly!bruce@Broadcast.Sony.COM
					...uunet!sonyusa!sonyd1!blilly!bruce
Newsgroups: news.software.readers,news.software.b
From: bruce@blilly.UUCP (Bruce Lilly)
Subject: trn and REPLYTO
Followup-To: news.software.readers
Organization: Bruce Lilly
Date: Sat, 2 Jan 93 00:08:49 GMT
Reply-To: lilb@sony.compuserve.com (Bruce Lilly)

[This might also apply to rn; I'm not sure exactly where the trn-specific
bits of trn are]

Although the man pages and other documentation (e.g. file NEW) mentions that
the environment variable REPLYTO can be used to specify the contents of a
Reply-to header, no Reply-To header is generated when using trn's follow-up
or reply mechanisms (it appears that the stand-alone scripts Rnmail and
Pnews may work).

The solution, if CONDSUB is defined is to alter the definition of MAILHEADER
and/or NEWSHEADER in file common.h, then rebuild respond.o and relink trn.

In case anybody cares, here's what I'm currently using for those definitions
(Newsgroups: and some other news-specific headers are inappropriate for
email replies, IMO):

#	    define MAILHEADER "To: %t\nSubject: Re: %S\n%(%{REPLYTO}=^$?:Reply-To: %{REPLYTO}\n)In-Reply-To: %i\nReferences: %R\nCc: \nBcc: \n\n"
#	define NEWSHEADER "Newsgroups: %(%F=^$?%C:%F)\nSubject: %(%S=^$?%\"\n\nSubject: \":Re: %S)\nSummary: \nExpires: \n%(%R=^$?:References: %R\n)Sender: \nFollowup-To: \n%(%{REPLYTO}=^$?:Reply-To: %{REPLYTO}\n)Distribution: %(%i=^$?%\"Distribution: \":%D)\nOrganization: %o\nKeywords: %[keywords]\n\n"

-- 
	Bruce Lilly		blilly!bruce@Broadcast.Sony.COM
					...uunet!sonyusa!sonyd1!blilly!bruce
From: kpm8447@tesla.njit.edu
Newsgroups: news.software.readers
Subject: News --> PC (offline reader)
Date: 31 Dec 92 00:41:31 GMT
Organization: New Jersey Institute of Technology

I'm sure this is posted in the wrong spot and will get flamed for it.

I've been trying (looking) for a way to read newsgroups offline on a pc.
I'd like to use an equivalent to bbs programs like bluewave.  The idea
is to compress all the unread news into a packet, transfer it to the pc
via modem.  Read and reply offline taking as much time as wanted then
repacking the replies and uploading them to the news.  I'm reading
news on a unix account running "nn" news reader.  Is there a FAQ on how
to do this, I'm no unix guru and know very little of networks and the
way newsgroup data is stored.  Please help me!  I've been searching for over
a year now.
(sorry for the plea and possible misposting)
- thanks in advance

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Kirk Membry                                    "Our Age is the Age of Industry"
                                                - Alexander Rodchenko
kpm8447@tesla.njit.edu                                    kpm8447@teak.njit.edu
kmembry@andromeda.rutgers.edu                            kpm8447@maple.njit.edu
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==
Newsgroups: news.software.readers,news.software.b
From: jbotz@mtholyoke.edu (Jurgen Botz)
Subject: Re: DESIGN DISCUSSION: The reference line is deficient
Organization: Mount Holyoke College
Date: Wed, 30 Dec 1992 15:36:40 GMT

In article <1hro2sINNo54@daisy.ee.und.ac.za> barrett@daisy.ee.und.ac.za (Alan P Barrett) writes:
>Why change the format at all?  The 'R' tells you nothing that you don't
>alread know from the mere fact that it is the first reference on the line.
>You can get the same result by using
>
>     References: <root@id> <old@references> <last@id>
>
>where the <root@id> is always propagated from an article to its followup,
>but some of the <old@references> might be trimmed during a followup.

Yes, that's nice, but in many cases it isn't true. The idea behind the
"R<id>" format is that trn needs to be able to know when it can reliably
identify a particular <id> as being that of the root of the thread.

>Don't change the format.  Encourage authors of posting software to
>ensure that the first reference is always retained.  Lobby for this
>encouragement to be enshrined in the son-of-RFC1036.

I'm all for that myself... but in practice we'll never arrive at a
situation where all posts are generated by conformant readers.
Therefor programs which want to utilize this information need to be
able to tell the difference.

Aha... this suggests a third solution!  If soRFC1036 explicitly stated
that the first <id> in the 'References:' header is to be the root,
then we could add an 'X-soRFC1036-conformat: yes' header to get the
same benefits!  *grin*... Or trn could add an 'X-Newsreader:' header
like tin... one would be able to identify conformant newsreaders from
that.

The "R<id>" solution is attractive in its brevity, but the problem
with it is that it gets us /away/ from conformance with any standards.
So of the solutions outlined by Wayne I would prefer the 'X-Root:'
one.

--
Jurgen Botz, jbotz@mtholyoke.edu
From: harper@convex.csc.FI (Rob Harper)
Newsgroups: news.software.readers
Subject: Re: opposite of a kill file?
Date: 2 Jan 93 10:44:31 GMT
Organization: Finnish Academic and Research Network Project - FUNET

In <1993Jan02.051224.2454@clarinet.com> brad@clarinet.com (Brad Templeton) writes:

>You can use newsclip as your filter mechanism.  It is on ftp.clarinet.com,
>in sources/nc.tar.Z

If you have nn runing then you can use nngrab. This utility will search
ALL of the newsgroups for a keyword appearing on the subject line
and MERGE all the hits into a "supernewsgroup" for easy reading.

RGDS -=ROB=-

--
 ~ Rob Harper                    ~ E-mail:          harper@convex.csc.fi    
 ~ Finnish State Computer Centre ~ Molbio/software: harper@nic.funet.fi
 ~ P.O. Box 40                   ~ Telephone:       +358 0 457 2076
 ~ SF-02101 Espoo Finland        ~ Fax:             +358 0 457 2302
Newsgroups: news.software.readers,news.software.b
From: kankkune@klaava.Helsinki.FI (Risto Kankkunen)
Subject: Re: DESIGN DISCUSSION: The reference line is deficient
Organization: University of Helsinki, Department of Computer Science
Date: Fri, 1 Jan 1993 16:36:08 GMT

>Aha... this suggests a third solution!  If soRFC1036 explicitly stated
>that the first <id> in the 'References:' header is to be the root,
>then we could add an 'X-soRFC1036-conformat: yes' header to get the
>same benefits!  *grin*...

I like this very much! Really, no grin. Whether RFC1036bis explicitly
codifies the special meaning of the first references entry or not, it
definitely should add a version header, like MIME added MIME-version.

So, I think trn (and other readers) should just treat the first
reference as root. If they see a NEWS-version header, they can be pretty
sure the first reference is really the root (if this will be defined in
RFC1036bin), otherwise it's the best guess they can make, anyway. Extra
X-headers aren't nearly as reliable.

But the important thing is for RFC1036bis to specify a NEWS-version
header or something ike that.


-- 
me olemme maailma               tiet{v{tk| ne ett{ on jouluaika ollenkaan
From: tgcpwd@rwc.urc.tue.nl (Wim van Dorst)
Newsgroups: news.software.readers
Subject: Where can I get Tin (latest version) by FTP?
Date: 22 Dec 92 08:52:12 GMT
Organization: Eindhoven University of Technology, The Netherlands

Hello *,

I have some small trouble with my old copy of Tin 1.1.6, which may well
be solved in newer releases. I tried to locate Tin on the most obvious
archives (even used archie) but I couldn't find it.

Where is the latest version (I believe 1.1.8) FTPable from?

Met vriendelijke groeten, Wim `Blue Baron' van Dorst
-- 
---------------------------------------------------------------------
Blue Baron = Wim van Dorst, Voice (+31) 074-443937, (+31) 02152-42319
(-: baron@clifton.hobby.nl  tgcpwd@urc.tue.nl  WvD@Akzo.400net.nl :-)
---------------------------------------------------------------------
Newsgroups: news.software.readers,news.software.b
From: brad@clarinet.com (Brad Templeton)
Subject: Re: DESIGN DISCUSSION: The reference line is deficient
Organization: ClariNet Communications Corp.
Date: Fri, 01 Jan 1993 04:56:54 GMT

I've been discussing the same issue for the new RFC.

The rule in the RFC remains, of course, that nobody should ever delete,
in news software, the root of a References tree.  Mail gateways unfortunately
tend to do this.

However, I wanted to address another problem -- how to identify important
messages that should not be deleted.  Of course software can't tell if
a message is important, so the simple test I made was that if the subject
changes it's a new mini-root.

The only way I can think of to specify this that doesn't break existing
software is to define a syntax for message-ids that expands the current one.

That syntax would probably be something like

	<unique@site__CODE>

Where the CODE is a our magic keyword, such as R for root, SR for
mini-root and so on.  Such codes could also be used as placeholders to say,
"there were too many references here, so I deleted them to save space."
though of course the RFC will state that software is expected to handle
a References line of any size up to memory constraints.

Anyway, old software won't generate the codes, that's always true.

New software could generate them.  It's possible, though unlikely, that
old software on a site ending in _R or something would generate a false
code.  This is not a catastophe, however, and software would be advised
that a false code is possible.

Anything outside <> would be doom for existing software that enforces
message-id syntax.

I view this as more important for spotting mini-roots (which are good
places for pruning) than for spotting the root, since missing roots are
a sign of broken gateways or software, while we currently have no way
to identify mini-roots without having them on file.
-- 
Brad Templeton, ClariNet Communications Corp. -- Sunnyvale, CA 408/296-0366
Newsgroups: news.software.readers
From: gasman1@netcom.com (David A. Silva)
Subject: PICO and TIN
Organization: Netcom - Online Communication Services  (408 241-9760 guest) 
X-Newsreader: TIN [version 1.1 PL8]
Date: Wed, 30 Dec 1992 20:11:45 GMT


Newsgroups: news.software.readers
From: pg@sanitas.stortek.com (Paul Gilmartin)
Subject: Re: Text editing in tin
Organization: Storage Technology Corp.
X-Newsreader: TIN [version 1.1 PL7]
Date: Mon, 28 Dec 1992 05:40:40 GMT

Michael Malloy (mmjjmm@post.its.mcw.edu) wrote:
: 
: What is the easiest text editor to use with the tin newsgroup reader?
: 
The one you know best.
From: bengtl@maths.lth.se (Bengt Larsson)
Newsgroups: news.software.readers
Subject: Re: opposite of a kill file?
Date: 30 Dec 92 19:00:27 GMT
Organization: Lund Institute of Technology, Sweden

In article <luwsm.27.725734959@lehigh.edu> luwsm@lehigh.edu (Wayne S. Mery) writes:
>In article <C02Dv1.x9@news.cso.uiuc.edu> rls@uihepa.hep.uiuc.edu (Ray Swartz (Oh, that guy again)) writes:
>>Subject: opposite of a kill file?
>>Date: 30 Dec 92 08:49:48 GMT
>> I'm a trn beginner so forgive this if it's a simple question.
>
>>        Is there a way in trn to set up a thread that you will always want to
>>read?  There are ways of killing a thread via kill files, but it would be nice
>>to mark a thread as 'interesting', so that you don't always have to remember
>>the name of it when you go into the group every day to read it.
>
>>Raymond L. Swartz Jr. (rls@uihepa.hep.uiuc.edu)

Yes, put a line
  
  /subject/+

in your killfile. 

The + marks those threads for reading when you enter the group. 
When you've read those, you can quickly "X" the others if you want.

Bengt L.
-- 
Bengt Larsson - bengtl@maths.lth.se
Newsgroups: news.software.readers
From: jp@tygra.Michigan.COM (John Palmer)
Subject: Performance Problems with RN 4.4
Organization: CAT-TALK Conferencing System
Date: Thu, 24 Dec 1992 21:06:39 GMT

We now get a full feed and have 2550 groups in our active file. 

RN is now unacceptably slow, especially when adding new groups.
It can take 5 minutes of real time to add 5 new groups to the 
active file. 

Is there some way to tweak the performance of RN? (Ie: Hash table
size selection)??

Palmer
-- 
Its most likely a     | E-MAIL: jp@michigan.com  CAT-TALK IS BACK as a FREE
forgery, so save your | SYSTEM!! 313-882-2209 300-14400 V.32/V.32BIS/TurboPEP
flames for someone    | Anon-UUCP: System: tygra, Login: nuucp, no pw
cares                 | Get file "/cat/pub/filelist" for a list of files.