This is a multi-part message in MIME format.
--------------E838E974070F5B2626C43902
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



--------------E838E974070F5B2626C43902
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Received: from mail1.bellsouth.net (mail1.bellsouth.net [205.152.0.6])
	by mail1.lig.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id TAA02278
	for ; Sun, 14 Feb 1999 19:11:09 -0500 (EST)
From: [email protected]
Received: from bl-30.rootsweb.com (bl-30.rootsweb.com [207.113.245.30])
	by mail1.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id TAA18692
	for ; Sun, 14 Feb 1999 19:11:43 -0500 (EST)
Received: (from slist@localhost)
	by bl-30.rootsweb.com (8.8.5/8.8.5) id QAA17620;
	Sun, 14 Feb 1999 16:10:11 -0800 (PST)
Date: Sun, 14 Feb 1999 16:10:11 -0800 (PST)
Message-Id: <[email protected]>
To: [email protected]
Subject: Re: Birth and Death Certificates
References: <[email protected]>
In-Reply-To: <[email protected]>
X-Loop: [email protected]

Common reasons for receiving the following message: 

1. You sent the command "help".

2. You sent a message to [email protected] that didn't look
like a message for a human but that could not be processed as a
computer command.  The most common reasons this happens are:
   - there is something in the message in addition to the command, for 
     instance a signature file or a thank you.  Please don't include anything
     besides the command, or (if this isn't possible because you don't know
     how to send a message without your signature being automatically appended)
     =immediately= =after= your last command, include a line that begins with
     two dashes (not underscores) and has no other characters.  The mail
     server will sometimes ignore everything that follows such a line, and if
     it does so for you, you're set.
   - the command was mistyped or spelled incorrectly: unsubscribe is right, 
     unscribe is wrong, unsuscribe is wrong, etc.  

A copy of your message is appended at the bottom of this message, for 
your review.  If you can't see what's wrong, you may want to send a copy to 
[email protected] and the listowner may be able to help you
identify the problem.  If you're unsuccessfully trying to subscribe or
unsubscribe, you can also send a note to [email protected] and
the listowner will generally take care of it when they next check their
e-mail.  Some of the following may apply:

			General info
			------------
Subcription/unsubscription/info requests should always be sent to the -request
address of a mailinglist.

If a mailinglist for example is called "[email protected]", then the -request
address can be inferred from this to be: "[email protected]".

To subscribe to a mailinglist, simply send a message with the word "subscribe"
in the body of a message to the -request address of that list.

As in:		To: [email protected]
		Subject: 

                subscribe


To unsubscribe from a mailinglist, simply send a message with the word (you
guessed it :-) "unsubscribe" in the body of a message to the -request address
of that list.

As in:		To: [email protected]
		Subject:

                unsubscribe


IMPORTANT DETAIL: signatures confuse SmartList.  If you can, send the commands
with *NO* signature following the body of the message.


In the event of an address change, it would probably be the wisest to first
send an unsubscribe for the old address (this can be done from the new
address), and then a new subscribe to the new address (the order is important).

Most (un)subscription requests are processed automatically without human
intervention.

Do not send multiple (un)subscription or info requests in one mail.  Only one
will be processed per mail.

NOTE: The -request server usually does quite a good job in discriminating
      between (un)subscribe requests and messages intended for the maintainer.
      If you'd like to make sure a human reads your message, make it look
      like a reply (i.e. the first word in the Subject: field should be "Re:",
      without the quotes of course); the -request server does not react to
      replies.


			The archive server
			------------------
Every submission sent to this list is archived.	 The size of the archive
depends on the limits set by the list maintainer (it is very well possible
that only, say, the last two mails sent to the list are still archived, the
rest might have expired).

You can look at the header of every mail coming from this list to see
under what name it has been archived.  The X-Mailing-List: field contains
the mailaddress of the list and the file in which this submission was
archived.

If you want to access this archive, you have to send mails to the -request
address with the word "archive" as the first word of your Subject:.
To get you started try sending a mail to the -request address with
the following line in the body of the message:
		archive help
Again, remember not to attach a signature after the "archive help" command.

--



--------------E838E974070F5B2626C43902--

==== SCROOTS Mailing List ====