HDTenEightyP/NetNews huggingface dataset:
Newsgroups: bit.listserv.csg-l
Date:         Tue, 29 Sep 1992 10:45:48 +0100
From:         "(Maler)" <maler@VERCORS.IMAG.FR>
Subject:      Change of address

To whom it may or may not concern.

My new address as of 1.9.92 is:

===============================================================
Oded Maler, LGI-IMAG (Campus), B.P. 53x, 38041 Grenoble, France
Phone:  76635846  Fax: 76446675   e-mail: maler@vercors.imag.fr
===============================================================
Home address: 7 chemin de vence, 38700 Corenc, phone: 76880711
===============================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 1 Oct 1992 10:33:18 EDT
Comments:     Converted from PROFS to RFC822 format by PUMP V2.2
From:         "Mignon Erixon-Stanford,
              Academic Systems Head" <IRMSS907@SIVM.BITNET>
Subject:      multiple disks

From:    Mignon Erixon-Stanford, Academic Systems Head


In my local sysvars, I put:   filedisk = 'A5 D5'  in the hopes that I could
write to either the A or D disk, depending upon what was in the list header.
Unfortunately, this does not work.  LISTSERV doesn't complain until I change
the header to write to the D disk.  Any suggestions?  (Obviously all my
lists point to the A disk, now).

=-=-=-=-=-=-=-=-=-=-=-IRMSS907@SIVM-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Research Systems Division     Smithsonian Institution, A&I 2310
Washington, DC 20560          Internet: IRMSS907@SIVM.SI.EDU
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Sat, 3 Oct 1992 14:28:55 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: multiple disks
              1 Oct 1992 10:33:18 EDT from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

For the umpteenth time:

The D-disk is a scratch work disk,  which is erased at startup and cannot
be used to archive files. I know this would be convenient since you would
then not have to ask systems people to make another disk, but this is not
open to discussion.  The reason LISTSERV needs a scratch  disk is that it
needs to be sure  it has a certain amount of  scratch space available for
work files.  If you fill  that reserved  space with arbitrary  amounts of
files, you no longer have a known amount of reserved space. If the amount
is so small that it would be no  problem, there is no reason it cannot go
to the A-disk.

The FILEDISK variable  is described as "the filemode of  the DEFAULT disk
to be  used for  storing files via  the PUT command".  This is  a default
filemode, so what is LISTSERV supposed to do if it has two values, flip a
coin?

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Mon, 28 Sep 1992 16:36:25 EDT
From:         Roger Fajman <RAF@NIHCU.BITNET>
Subject: Re: Announcing LB64.C - a program for non-BITNET list owners

> I haven't  yet figured out exactly  how it can be  used (beyond replacing
> UUENCODE et al). MIME  does not seem to be a  working replacement for FTP
> or the various BITNET file formats. The  only thing that is clear is that
> a file (I  mean a "real" file, with binaries  and non-default file system
> parameter    requirements)   is    to   be    sent   as    "Content-Type:
> application/octet-stream". Yeah, and  you still need the  good old BITNET
> style file  formatter to  encode and  decode the thing,  I'm sorry  but I
> don't call that progress.

I'm not a MIME expert, but I do know that it is extensible.  New application
types can be registered with IANA (Internet Assigned Numbers Authority).  I
don't think that the registration process is intended to be onerous, but
they will want a short RFC decsribing what the new type does.  I hope that
we won't have application/netdata, but rather something simpler and more in
the spirit of MIME.

Roger Fajman                                   Telephone:  +1 301 402 1246
National Institutes of Health                  BITNET:     RAF@NIHCU
Bethesda, Maryland, USA                        Internet:   RAF@CU.NIH.GOV
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Tue, 29 Sep 1992 19:23:56 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: Handling of Jobs w/QuietNo
              29 Sep 1992 14:08:06 EDT from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

On Tue, 29 Sep 1992 14:08:06 EDT "Duane D. Weaver" <WEAVER@OHSTVMA> said:

>Does LISTSERV ORDER the queue to get the oldest job back at the top?
>
>If not, why not?

No, because the network doesn't  generally deliver files in chronological
order. Keeping  track of what  job was held at  what time and  then using
this  information to  put the  queue  back in  the  same order  is a  non
negligible amount  of work,  what with modern  CP's where  spoolid's keep
changing. Most  non-prime-time jobs  are inter-LISTSERV  management jobs,
like  netwide deletes  and  GLOBLIST FILE  updates and  so  on. It  makes
absolutely no difference if they are executed in the "wrong" order.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Sun, 27 Sep 1992 20:37:50 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Announcing LB64.C - a program for non-BITNET list owners
Comments: To: LSTOWN-L@INDYCMS.BITNET

One of the "building blocks" added to  the next version of LISTSERV is an
internal command  called X-B64 which a  future version could use  to pass
binary DISTRIBUTE jobs over mail gateways.  Before you ask, I haven't got
any  serious plan,  schedule or  time  frame for  supporting LISTSERV  on
non-BITNET systems; I am adding this  now because it happened to fit with
what I have  been coding recently and  I know it would take  me twice the
time to add  it in 6 months.  Furthermore it will make  testing easier to
have this feature  already available on a number of  servers when writing
the code for non-BITNET hosts.

I then  realized that  there is  no reason to  restrict this  function to
server-to-server  interactions, since  users without  BITNET connectivity
could greatly benefit from a simple  but robust encoding system for their
list and file management requests. So I made the command public and wrote
a  sample C  program for  unix users.  Currently only  LISTSERV@SEARN has
support for this  format, but the comments in the  program explain how to
reach  any  server  through  one  that supports  X-B64.  The  program  is
available  from LISTSERV@SEARN  via 'GET  LB64.C'. The  LISTSERV code  to
support this format  adds up to 815kb  and a bunch of files  once all the
pre-reqs are included so I don't want  to package it as a FIX file, there
have been  a number  of massive  "global changes"  which have  never been
tested  outside SEARN.  If you  really want  it I  can supply  CARD decks
similar to those used for beta-testing,  and with the same disclaimers as
for beta-testing.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 1 Oct 1992 16:36:44 +0100
Reply-To:     ERIC@SEARN.BITNET
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Where can I find free MIME software?

If you know of free MIME-compliant  user interfaces (things that can both
generate and  decode MIME messages) for  VM, VMS or SunOS  (*without* X),
please let me  know where I can get  it from. I am not  interested in the
audio/graphics stuff, just the "real mail" functions. Note the Reply-To.

Thanks,

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: University at Albany Computing Services
X-Acknowledge-To: <BEC@ALBANY>
Newsgroups: bit.listserv.lstsrv-l
Date:         Tue, 29 Sep 1992 00:36:33 EDT
From:         Ben Chi <BEC@ALBANY.BITNET>
Subject:      Re: Someone is at it again

There's been a bit of fuss on the net about this one alreay.  It happens
now and then.  Just ignore it, resting assured that ample flames will come
from elsewhere.
                                             /b
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Subject: (no subject given)
Newsgroups: bit.listserv.lstsrv-l
Date:         Mon, 28 Sep 1992 22:23:16 EDT
From:         Michael Hillwig <MLH4125@SRU.BITNET>

Can someone tell me how to get detailed information about a specific
list?  I don't need the whole file with detailed information about
all 3000+ lists, just a few.  Can anyone help?
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Resent-Organization: Marist College
Newsgroups: bit.listserv.lstsrv-l
Date:         Thu, 1 Oct 1992 10:58:59 EDT
Reply-To:     "A. Harry Williams" <HARRY@VM.MARIST.EDU>
Comments:     To: ethics-l@uga.cc.uga.edu
Comments:     Resent-From: "A. Harry Williams" <HARRY@VM.MARIST.EDU>
Comments:     Originally-From: GE-ADMIN%GEIS.COM@VM.MARIST.EDU
Comments:     Warning -- original Sender: tag was
              ETHICS-L%MARIST.BITNET@VM.MARIST.EDU
From:         "A. Harry Williams" <HARRY@VM.MARIST.EDU>
Subject:      McElwaine

You may wish to serve off GE-ADMIN@GEIS.COM.

----------------------------Original message----------------------------
Original Msg Id: 51197
GE-ADMIN response to your message

    Subject: McElwaine
    System:  QUIK-COMM
    Date:    Thu  1-Oct-92  9:05

Status: 7   Message picked up by receiving system and not delivered to
            any recipients because of various exception conditions.

Address Delivered To:
   LOONEY.TUNES
Address Status Message:
   *   This address is not permitted to view or send to address LOONEY.TUNES
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Instituto Tecnologico de Monterrey, Campus Queretaro
Newsgroups: bit.listserv.lstsrv-l
Date:         Wed, 30 Sep 1992 16:26:38 CST
From:         "Juan M. Courcoul" <COURCOUL@VMTECQRO.BITNET>
Subject:      BE ON THE LOOKOUT: malformed X-DEL job causes hundreds of files

The following X-DEL job arrived at our server on repeated occasions,
causing over 100 reply mails to be sent back to its origin.
How is it that an invalid job like this gets distributed by the servers
(console error message sez "Empty DD datasets not allowed") ?

--- Attached erroneous job ---------------
//Netwide_Delete JOB Echo=No,Prime=QuietNo, Reply-To="UZR115@DBNRHRZ1",Reply-Vi,
//+ a=MAIL
// X-FOR UZR115@DBNRHRZ1 QUIET DELETE * FWDED=2 DD=Names (  NETWIDE
//Names DD *,EOF
------------------- end of file --------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
From: ERIC@SEARN.BITNET (Eric Thomas)
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: Announcing LB64.C - a program for non-BITNET list owners
Date: 28 Sep 92 10:45:36 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
              28 Sep 1992 00:46:29 CDT from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

On Mon, 28  Sep 1992 00:46:29 CDT "(David  E Boyes)" <dboyes@IS.RICE.EDU>
said:

>Is the output  of this program compatible with the  base64 encoding used
>in the MIME multimedia extensions package for Internet mail?

There does not exist such a thing  as a MIME file transfer encoding. What
MIME describes is  a base64 encoding system which translates  a stream of
binary  characters into  a stream  of printable  characters that  survive
gateways, and LB64/LISTSERV  use exactly that encoding (so  that the code
can be reused to provide support for outgoing MIME mail at a later date).
But  MIME falls  short of  describing the  *contents* of  this stream  of
binaries in enough details  to be usable for what I have  to do. It hints
at the fact  that one should not  forget to encode the  CRLF's when using
base64, but what  if I want to  transfer binary data? What if  I am using
EBCDIC?

>As a futures thing, is LISTSERV support for MIME in the works?

I haven't  yet figured out exactly  how it can be  used (beyond replacing
UUENCODE et al). MIME  does not seem to be a  working replacement for FTP
or the various BITNET file formats. The  only thing that is clear is that
a file (I  mean a "real" file, with binaries  and non-default file system
parameter    requirements)   is    to   be    sent   as    "Content-Type:
application/octet-stream". Yeah, and  you still need the  good old BITNET
style file  formatter to  encode and  decode the thing,  I'm sorry  but I
don't call that progress.

>It'd really be neat  to have the ability to have my  mail reader be able
>to receive files and  text messages in the same message  and not have to
>worry about figuring out what  utility I need to receive/decode/assemble
>various kinds of files.

You mean  RECEIVE actually  asks you  what format the  file is  in before
receiving it, and you didn't report the bug to IBM? :-)

>One of  the PIPES-phreaks  here has written  a replacement  for SENDFILE
>that employs MIME to encapsulate files that might be interesting to look
>at. We've  successfully used  it to  move some  pretty large  text files
>around -- it might be an interesting base to work from.

You said  it - text files.  Not indexed word processor  dictionary files.
MIME supports "files" in the unix/PC sense only - stream of bytes.

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: University at Albany Computing Services
X-Acknowledge-To: <BEC@ALBANY>
Newsgroups: bit.listserv.lstsrv-l
Date:         Tue, 29 Sep 1992 00:39:27 EDT
From:         Ben Chi <BEC@ALBANY.BITNET>
Subject:      Re: Someone is at it again

Sorry, folks.  Last (regarding Gomes mailing) wasn't intended for list.
Apologies for adding to the noise level.
                                             /b
Organization: Penn State University
Date: Tue, 29 Sep 1992 07:11:39 EDT
From: Peter M. Weiss <PMW1@psuvm.psu.edu>
Newsgroups: bit.listserv.lstsrv-l
Subject: List Details (was Re: (no subject given))

In article <LSTSRV-L%92092822263319@UGA.CC.UGA.EDU>, Michael Hillwig
<MLH4125@SRU.BITNET> says:

>Can someone tell me how to get detailed information about a specific
>list?  I don't need the whole file with detailed information about
>all 3000+ lists, just a few.  Can anyone help?

I've GIVEn LISTSOF LISTS from the listserv@ndsuvm1 to Michael.

/Pete
From: dboyes@IS.RICE.EDU ((David E Boyes))
Newsgroups: bit.listserv.lstsrv-l
Subject: Re: Announcing LB64.C - a program for non-BITNET list owners
Date: 28 Sep 92 05:46:29 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.3 PL11]
Comments: To: LSTSRV-L%UGA.BITNET@ricevm1.rice.edu
              92 8:37 pm

> One of the "building blocks" added to  the next version of LISTSERV is an
> internal command  called X-B64 which a  future version could use  to pass
> binary DISTRIBUTE jobs over mail gateways.  Before you ask, I haven't got

Is the output of this program compatible with the base64 encoding
used in the MIME multimedia extensions package for Internet mail?
If not, I'd suggest taking a look at it -- MIME is becoming more
and more popular, and the base64 encoding type is flexible enough
to be a very useful tool without inventing Yet Another File
Encoding Program.

As a futures thing, is LISTSERV support for MIME in the works?
It'd really be neat to have the ability to have my mail reader be
able to receive files and text messages in the same message and
not have to worry about figuring out what utility I need to
receive/decode/assemble various kinds of files. From a trivial
look at what would be required, the list of headers passed
through the header filter for short headers would have to be
expanded to pass the X-MIME-Version header and the loop detector
code would probably have to be able to ignore MIME element
headers in the body of the message.

One of the PIPES-phreaks here has written a replacement for
SENDFILE that employs MIME to encapsulate files that might be
interesting to look at. We've successfully used it to move some
pretty large text files around -- it might be an interesting base
to work from.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Wed, 30 Sep 1992 22:31:33 +0100
From:         Eric Thomas <ERIC@SEARN.BITNET>
Subject:      Re: Announcing LB64.C - a program for non-BITNET list owners
              30 Sep 1992 14:01:50 CST from "Forum on LISTSERV release 1.7"
              <LSTSRV-L@SEARN>

On Wed, 30 Sep 1992 14:01:50 CST Brent Stilley <UCCXBRS@OSUVM1> said:

>I went to  cc:Mail's Interchange last week. They  are supporting RFC1154
>and  MIME in  their  gateways/routers. There  are  currently 2M  cc:Mail
>users. Especially in  the Windows and Mac  environments, attachments are
>very common.  We have committed to  cc:Mail for LAN users,  yet VM, VMS,
>Unix, etc.. will remain very much a  part of our 'picture'. We have many
>cc:Mail users subscribing to lists,  so let's please not invent anything
>new.

Concretely, what is your problem?

  Eric
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.lstsrv-l
Date:         Tue, 29 Sep 1992 14:08:06 EDT
From:         "Duane D. Weaver" <WEAVER@OHSTVMA.BITNET>
Subject:      Handling of Jobs w/QuietNo

Distribute jobs that come in to be processed after Prime time
(Prime=QuietNO) are placed in HOLD status in LISTSERV's reader.

When the next job comes in with Prime=QuietNo, the job is placed
into HOLD.  This job is now ahead of the previously held job.

This processed for each subsequent job that comes in with Prime=QuietNo.

This builds up a queue of jobs to be processed, with the oldest job
at the bottom.

I have not paid attention to how Listserv handles these jobs when
Prime time is over.

Does LISTSERV ORDER the queue to get the oldest job back at the top?

If not, why not?
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Oklahoma State University
Newsgroups: bit.listserv.lstsrv-l
Date:         Wed, 30 Sep 1992 14:01:50 CST
From:         Brent Stilley <UCCXBRS@OSUVM1.BITNET>
Subject:      Re: Announcing LB64.C - a program for non-BITNET list owners

>> One of the "building blocks" added to  the next version of LISTSERV is an
>> internal command  called X-B64 which a  future version could use  to pass
>> binary DISTRIBUTE jobs over mail gateways.  Before you ask, I haven't got
>
>Is the output of this program compatible with the base64 encoding
>used in the MIME multimedia extensions package for Internet mail?
>If not, I'd suggest taking a look at it -- MIME is becoming more
>and more popular, and the base64 encoding type is flexible enough
>to be a very useful tool without inventing Yet Another File
>Encoding Program.

I went to cc:Mail's Interchange last week.  They are supporting RFC1154
and MIME in their gateways/routers.  There are currently 2M cc:Mail
users.  Especially in the Windows and Mac environments, attachments
are very common.  We have committed to cc:Mail for LAN users, yet VM,
VMS, Unix, etc.. will remain very much a part of our 'picture'.  We
have many cc:Mail users subscribing to lists, so let's please not invent
anything new.

Brent Stilley,  Oklahoma State University, 113 Math Sciences, Stillwater, 74078
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.edi-l
Date:         Mon, 5 Oct 1992 10:30:00 LCL
From:         "(DIL)" <DIL.ADMIN@MHS.UNC.EDU>
Subject:      Financial Aid EDI
Comments: To: "(-)" <EDI-L@uccvma.ucop.edu>

To: @EDI-L

I work at University of North Carolina. One of our application departments
is looking at electronically transferring financial aid data to and from a
loan processing company. The EDI transaction sets are currently being
specified and hopefully will be ready in Jan. 1993. Does anyone out there
have any experience or recommnedations for value added networks that would
provide a service to allow us to do the transfer. Also does anyone have any
suggestions for mapping software to map our data to the standard. We are an
IBM shop running MVS, using IDMS for data management and a third party
application product from Information Associates (FAMS) for our financial
aid system.
Thx Dave L (dil.admin@mhs.unc.edu)
Administrative Data Processing
University of North Carolina
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: EDI-L@UCCVMA.BITNET
X-VMS-To: MAILER%"EDI-L@UCCVMA.BITNET"
Newsgroups: bit.listserv.edi-l
Date:         Fri, 2 Oct 1992 08:27:00 EDT
From:         BAUM@HULAW1.BITNET
Subject:      Re: Search for life

The X12 Meeting is ending today in Detroit. I just returned from it.

Perhaps you might be interested to know that there was a shake up in
the Board of Directors and Ken Hutcheson was appointed Chair of the Bd.
Also the dues structure was revoked and all prior dues catagories will
undergo a 20% increase rather than the prior proposed schedule.

Best,
Michael
From: BAUM@HULAW1.BITNET
Newsgroups: bit.listserv.edi-l
Subject: Re: EDI transactions (was Re:
Date: 2 Oct 92 18:39:00 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: EDI-L@UCCVMA.BITNET
X-VMS-To: MAILER%"EDI-L@UCCVMA.BITNET"

"I saw a message talking about edi over the Internet. What are people doing
about transport security over the Internet. What types of encryption
products would be utilized? Anything on the Internet is open to tapping.
Thx Dave L"

Look into Privacy Enhanced Email on the Internet (PEM); also, concerning
end-to-end X12 security, obtain a copy of X12.58 from DISA.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.edi-l
Date:         Tue, 6 Oct 1992 10:31:00 LCL
From:         "(DIL)" <DIL.ADMIN@MHS.UNC.EDU>
Subject:      Financial Aid EDI
Comments: To: "(-)" <EDI-L@uccvma.ucop.edu>

To: @EDI-L

Not sure if this message made it am resending sorry if repeat.

I work at University of North Carolina. One of our application departments
is looking at electronically transferring financial aid data to and from a
loan processing company. The EDI transaction sets are currently being
specified and hopefully will be ready in Jan. 1993. Does anyone out there
have any experience or recommnedations for value added networks that would
provide a service to allow us to do the transfer. Also does anyone have any
suggestions for mapping software to map our data to the standard. We are an
IBM shop running MVS, using IDMS for data management and a third party
application product from Information Associates (FAMS) for our financial
aid system.
Thx Dave L (dil.admin@mhs.unc.edu)
Administrative Data Processing
University of North Carolina
From: reverman@KA.REG.UCI.EDU (Richard Everman)
Newsgroups: bit.listserv.edi-l
Subject: Re: EDI transactions (was Re:
Date: 2 Oct 92 20:50:38 GMT
Reply-To: Richard Everman <reverman@uci.edu>
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Comments: To: EDI-L@uccvma.ucop.edu

In message <9210021800.AA21473@ka.reg.uci.edu> "Electronic Data Interchange
Issues" writes:
> I saw a message talking about edi over the Internet. What are people doing
> about transport security over the Internet. What types of encryption
> products would be utilized? Anything on the Internet is open to tapping.
> Thx Dave L

Dave

Please state why this is so.  I plan to send transcripts over the Internet and I
would not like the transcripts modified!

Thanks

Richard Everman
reverman.ka.reg.uci.edu

Associate Registrar
University of California, Irvine
215 Adm Bldg
Irvine, CA 92717
(714) 856-7901
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: EDI-L@UCCVMA.BITNET
X-VMS-To: MAILER%"EDI-L@UCCVMA.BITNET"
Newsgroups: bit.listserv.edi-l
Date:         Fri, 2 Oct 1992 08:31:00 EDT
From:         BAUM@HULAW1.BITNET
Subject:      Re: EDI transactions (was Re: Search for life)

You might want to email to to Tom Prosch at DISA about the future availability
of the stds. on the Internet, because right now there is some activity
underway to automate things. They use MCI as their carrier/service provider.

Contact: TProsch_+a_X12_+lTom_Prosch+r%X12_DISA@mcimail.com
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU