From:	CRDGW2::CRDGW2::MRGATE::"SMTP::IBM1.CC.LEHIGH.EDU::LISTSERV" 12-JUN-1989 11:57
To:	MRGATE::"ARISIA::EVERHART"
Subj:	Your subscription to list VIRUS-L

Message-Id:  <8906121513.AA09637@crdgw1.ge.com>
Received: from LEHIIBM1.BITNET by IBM1.CC.Lehigh.Edu (IBM VM SMTP R1.2) with BSMTP id 3303; Sat, 10 Jun 89 07:15:16 EDT
Received: by LEHIIBM1 (Mailer R2.03A) id 3492; Sat, 10 Jun 89 07:15:08 EDT
Date:         Sat, 10 Jun 89 07:15:07 EDT
From: Revised List Processor (1.5o) <LISTSERV@IBM1.CC.Lehigh.Edu>
Subject:      Your subscription to list VIRUS-L
To: Glenn Everhart <EVERHART@ARISIA.decnet>

Dear networker,

  Your subscription to list VIRUS-L (Virus Discussion List) has been accepted.

[ Last modified 29-July-88 - Ken van Wyk ]

Welcome! This  is the monthly  introduction posting for VIRUS-L,  primarily for
the benefit of any newcomers. Apologies  to all subscribers who've already read
this in  the past  (you'll only have  to see it  once a  month and you  can, if
you're quick, press the purge key...:-).

What is VIRUS-L?

It  is  an electronic  mail  discussion  forum  for sharing  information  about
computer viruses.  Discussions should include  (but not necessarily  be limited
to):  current  events  (virus   sightings),  virus  prevention  (practical  and
theoretical),  and  virus  questions/answers.  The list  is  non-moderated  and
non-digested.  That means  that any  message  coming in  goes out  immediately.
Weekly logs of  submissions are kept for those people  who prefer digest format
lists (see below for details on how to get them).

What isn't VIRUS-L?

A place to  spread hype about computer  viruses; we already have  the Press for
that. :-) A place to sell things,  to panhandle, or to flame other subscribers.
If anyone *REALLY* feels the need to flame someone else for something that they
may have said, then the flame should  be sent directly to that person and/or to
the list moderator (that'd be me, <LUKEN@LEHIIBM1.BITNET>).

How do I get on the mailing list?

Well, if  you're reading this, chances  are *real good* that  you're already on
the  list. However,  perhaps this  document was  given to  you by  a friend  or
colleague... So, to get  onto the VIRUS-L mailing list, send  a mail message to
<LISTSERV@LEHIIBM1.BITNET>. In the  body of the message, say  nothing more than
SUB VIRUS-L your name. LISTSERV is a program which automates mailing lists such
as VIRUS-L. As  long as you're either  on BITNET, or any  network accessible to
BITNET via gateway, this  should work. Within a short time,  you will be placed
on the mailing list, and you will get confirmation via e-mail.

How do I get OFF of the list?

If, in  the unlikely event, you  should happen to  want to be removed  from the
VIRUS-L discussion  list, just  send mail to  <LISTSERV@LEHIIBM1.BITNET> saying
SIGNOFF VIRUS-L. People, such as students, whose accounts are going to be close
(like over the summer...) - PLEASE signoff  of the list before you leave. Also,
be  sure to  send your  signoff request  to the  LISTSERV and  not to  the list
itself. Note that the appropriate node name  is LEHIIBM1, not LEHIGH; we have a
node called LEHIGH, but they are *NOT* one and the same.

How do I send a message to the list?

Just   send  electronic   mail   to  <VIRUS-L@LEHIIBM1.BITNET>   and  it   will
automatically be redistributed to everyone on the mailing list. By default, you
will NOT  receive a  copy of your  own letters.  If you wish  to, send  mail to
<LISTSERV@LEHIIBM1.BITNET> saying SET VIRUS-L REPRO

I can't submit anything to the list - what's wrong?

There have been  a few cases where  people found that they were  unable to send
anything  in to  VIRUS-L even  though  they were  registered subscribers  (only
subscribers  can participate).  Let me  try  to explain.  The LISTSERV  program
differentiates lowercase from  UPPERCASE. So, if you've subscribed  to the list
as (for example) OPUS@BLOOM.COUNTY.EDU and your mail is actually coming through
as  Opus@Bloom.County.EDU,  then  the  LISTSERV  will  think  that  you're  not
subscribed  to the  list. BITNET  usernames  and node  names are  automatically
uppercased by the  LISTSERV, but other network addresses are  not. If your site
(or you) should happen to make a change to, say, the system mailer such that it
changes  the case  of  your mail,  there  will be  problems.  If you're  having
problems  submitting (you'll  know  this  because the  LISTSERV  will say  "Not
authorized to  send to VIRUS-L..."),  try unsubscribing and  re-subscribing. If
that doesn't  work, send me mail  (LUKEN@LEHIIBM1.BITNET), and I'll try  to fix
things up.

What does VIRUS-L have to offer?

All  submissions  to VIRUS-L  are  stored  in weekly  log  files  which can  be
downloaded by any user on (or off)  the mailing list; readers who prefer digest
format lists should read only the weekly logs. There is also a small archive of
some  of the  public anti-virus  programs which  are currently  available. This
archive, too, can be accessed by any user. All of this is handled automatically
by the LISTSERV here at Lehigh University (<LISTSERV@LEHIIBM1.BITNET>).

How do I get files from the LISTSERV?

Well, you'll first want to know what files are available on the LISTSERV. To do
this, send mail  to <LISTSERV@LEHIIBM1.BITNET> saying INDEX  VIRUS-L. Note that
filenames/extensions are separated by a space, and not by a period. Once you've
decided which file(s) you want,  send mail to <LISTSERV@LEHIIBM1.BITNET> saying
GET filename  filetype. For  example, GET  VIRUS-L LOG8804  would get  the file
called VIRUS-L  LOG8804 (which happens  to be the  monthly log of  all messages
sent to VIRUS-L during April, 1988). Note that, starting June 6, 1988, the logs
are weekly. The new  file format is VIRUS-L LOGyymmx where yy  is the year (88,
89, etc.), mm is the month, and x  is the week (A, B, etc.). Readers who prefer
digest  format lists  should read  the weekly  logs and  sign off  of the  list
itself. Subsequent submissions to the list should be sent to me for forwarding.

Also available is a LISTSERV at  SCFVM which contains more anti-virus software.
This LISTSERV can  be accessed in the  same manner as outlined  above, with the
exceptions that the address is <LISTSERV@SCFVM.BITNET> and that the commands to
use are INDEX PUBLIC and GET filename filetype PUBLIC.

What is uuencode/uudecode, and why do I need them?

Uuencode and  uudecode are two  programs which  convert binary files  into text
(ASCII) files and back again. This is so binary files can be easily transferred
via electronic mail. Many of the files  on this LISTSERV are binary files which
are stored in uuencoded format (the file  types will be UUE). Both uuencode and
uudecode are available from the LISTSERV. Uudecode is available in BASIC and in
Turbo Pascal here. Uuencode is available in Turbo Pascal. Also, there is a very
good binary-only uuencode/uudecode  package on the LISTSERV which  is stored in
uuencoded format.

Why have posting guidelines?

To  keep the  discussions on-track  with what  the list  is intended  to be;  a
vehicle for virus discussions. This will  keep the network traffic to a minimum
and, hopefully,  the quality of the  content of the  mail to a maximum.  No one
wants to  read personal flames  ad nausium, or  discussions about the  pros and
cons of digest-format mailing lists, etc.

What are the guidelines?

     As already  stated, there will  be no flames  on the list.  Anyone sending
     flames to the entire  list must do so knowing that  he/she will be removed
     from the list immediately.

     Same goes for any commercial plugs or panhandling.

     Submissions should  be directly  or indirectly related  to the  subject of
     computer viruses.

     Responses to queries should be sent to the author of the query, not to the
     entire list. The author should then send a summary of his/her responses to
     the list at a later date.

     "Automatic answering machine" programs (the ones which reply to e-mail for
     you  when you're  gone) should  be  set to  *NOT* reply  to VIRUS-L.  Such
     responses sent  to the entire  list are very rude  and will be  treated as
     such.

     When sending in a  submission, try to see whether or  not someone else may
     have  just  said the  same  thing.  This  is particularly  important  when
     responding to someone else's posting (which  should be sent to that person
     *anyway*). It's very  easy to get multiple messages saying  the exact same
     thing. No one wants this to happen.

Thank-you for  your time and for  your adherance to these  guidelines. Comments
and  suggestions,  as   always,  are  invited.  Please  address   them  to  me,
<LUKEN@LEHIIBM1.BITNET> or <luken@Spot.CC.Lehigh.EDU>.

Ken van Wyk

