This is a multi-part message in MIME format. --part0_905197142_boundary Content-ID: <[email protected]_out.mail.aol.com.1> Content-type: text/plain; charset=US-ASCII I sorta agree with Mart, as I belong to genealogy sites, where someone post their answer back and I have found load of answers. I've gotten lots of names, other sites to go to, etc. I understand you have your rules. Sharon --part0_905197142_boundary Content-ID: <[email protected]_out.mail.phoenixat.com.2> Content-type: message/rfc822 Content-transfer-encoding: 7bit Content-disposition: inline Return-Path: <[email protected]> Received: from rly-za03.mx.aol.com (rly-za03.mail.aol.com [172.31.36.99]) by air-za05.mail.aol.com (v49.1) with SMTP; Mon, 07 Sep 1998 07:23:42 2000 Received: from fp-1.rootsweb.com (fp-1.rootsweb.com [207.113.233.233]) by rly-za03.mx.aol.com (8.8.8/8.8.5/AOL-4.0.0) with ESMTP id HAA12098; Mon, 7 Sep 1998 07:23:30 -0400 (EDT) Received: (from [email protected]) by fp-1.rootsweb.com (8.8.5/8.8.5) id EAA16429; Mon, 7 Sep 1998 04:22:56 -0700 (PDT) Resent-Date: Mon, 7 Sep 1998 04:22:56 -0700 (PDT) Message-Id: <[email protected]> From: "mararm" <[email protected]> Old-To: <[email protected]> Subject: Re: PLEASE READ !!!!! IMPORTANT !!!!! FROM THE LISTOWNER Date: Mon, 7 Sep 1998 07:23:48 +0100 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 Resent-Message-ID: <"6VnDV.A.R_D.LI881"@fp-1.rootsweb.com> To: [email protected] Resent-From: [email protected] Reply-To: [email protected] X-Mailing-List: <[email protected]> archive/latest/10940 X-Loop: [email protected] Precedence: list Resent-Sender: [email protected] Mime-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: quoted-printable I thought this list was for information. I for one look forward to seeing the answers in case I could use them. Why do I have to just read questions. Mart ---------- > From: SURNAME-QUERY List Owner <[email protected]> > To: [email protected] > Subject: PLEASE READ !!!!! IMPORTANT !!!!! FROM THE LISTOWNER > Date: Monday, September 07, 1998 6:53 AM > > Once you have established correspondence with another user on this List, > please send your email to that person privately, NOT back to the List. If > someone offers to do lookups, PLEASE send your requests to that person's > personal email address. (You can always find it in the message header i= n > the FROM: line.) > > If you are the person offering lookups, please DO NOT send those look-up= s > back to the List!!!!! > > Tonight, a user sent another user a GEDCOM file which was included in > the body text of the email. It was almost 1 Mb in size !!!!! Fortunately > RootsWeb caught it and didn't deliver it to the List. Instead, I had to wait > 5 minutes for it to download to me since such errors are sent automatically > to the Listowner. > > Again, if your email narrowly applies only to one user, correspond with > that user, and do not keep sending chit-chat email back to the List. > > Thanks, > SgtGeorge > Listowner > > > =3D=3D=3D=3D SURNAME-QUERY Mailing List =3D=3D=3D=3D > Reminder! Please remove as much of the Original Message as possible when > replying to a List Posting. Include only that part of the original message > important to your reply. > > > > =3D=3D=3D=3D SURNAME-QUERY Mailing List =3D=3D=3D=3D APPROPRIATE SUBJECT LINES: In an effort to provide meaningful Subject: lines in posts to the SURNAME-QUERY List, the Listowner asks you to try to adhere to the following format: SURNAME, First MI;dates;places An example would look like this: BROWNING, Arthur C.;1795-1876;PA>VA>OH Users of this SURNAME-QUERY List do not download every day in order to read each of the hundreds of posts. They are looking for certain SURNAMES, on which they are doing research, or are willing to help others with research of said SURNAMES. Therefore, if you do not provide meaningful Subject: lines, chances are good that your posts will be deleted without having been read. Also, the accepted standard in conducting genealogy research via the Internet/Web is to spell all SURNAMES in CAPS. --part0_905197142_boundary--