Beginning March 2nd, 2020 the Mailing Lists functionality on RootsWeb will be discontinued. Users will no longer be able to send outgoing emails or accept incoming emails. Additionally, administration tools will no longer be available to list administrators and mailing lists will be put into an archival state.
Administrators may save the emails in their list prior to March 2nd. After that, mailing list archives will remain available and searchable on RootsWeb
Does anyone have a Clarence Emerson Case from Cleveland, Ohio??????he was
born 05July1852......probably in Conn.....married 06 Oct.1860 to Helen
McGregor. He was the son of George Huron Case..and Ann Eliza Packard....and
older brother of my grandmother, Violetta Anna Case.We are also having
difficulty finding information on Ann Eliza Packard Case......
Bethel
Your last odd day...
Wednesday was November 17th, 1999.
The numerical format for it was 11-17-1999. All of the digits are odd.
The next Odd Day is today, 11-19-1999.
The next Odd Day after today will be 1-1-3111 - which is well over a
thousand years away.
Days such as 4-13-89 have both even and odd digits, so are neither odd
nor
even.
The next even day will be 2-2-2000 - the first one since 8-28-888.
So, now you have a reason to celebrate! It's your last odd day on
Earth!!!!!!
Have a nice odd day!
Allen Weissinger wrote:
> I have run into a death certificate that gave the man's dead brother as
> his father. Can't even take official documents as last word! The only
> way I found out it was wrong was through a cousin of his!
Which brings up the point that the information given on any official document is
"only as good as the knowledge of the person that gave the info"
When I gave the death certificate info for my father I had to give his origin. He
was a fourth generation Canadian (sorce: Canadian census records but maybe they
fibbed). Canadian is not a good answer it must be English, Irish, German etc.
So I said English and darn well wish I knew for sure. If I ever find out for
positive changing what I have said will not be easy.
So does anyone know where my Harrison CASE b 1812 was born. He later married
Lodemia, they both died 4 April 1891 at Beechville, Ontario, Canada. I will follow
any lead!!!
Caution is a good word in geneology!
Roberta Case
> If you know the facts are wrong on a Death Certificate, will the Vital
> Records Department correct the mistake? I have run into this same
> situation, where the man's brother was given as his father.
No, they won't correct one. But, I think they attach a proof document
that you send them to the certificate.
Lori
This is what I've learned. Death certificate info is only as good as the
person furnishing the info. That's why in FL , for FL pioneer certificate,
they don't accept death certificates as proof of parentage.
Anne
If you know the facts are wrong on a Death Certificate, will the Vital
Records Department correct the mistake? I have run into this same
situation, where the man's brother was given as his father.
Carole
Carole S. Walker in Catawba, South Carolina
mott(a)cetlink.net
AOL INSTANT MESSAGE ADDRESS: walkerc36
ICQ# 22149680
----- Original Message -----
From: Lori <lori(a)myself.com>
To: <Case-Family-L(a)rootsweb.com>
Sent: Wednesday, November 17, 1999 7:10 PM
Subject: Re: On the other Hand . . .
> > I have run into a death certificate that gave the man's dead brother as
> > his father. Can't even take official documents as last word! The only
> > way I found out it was wrong was through a cousin of his!
>
> I believe I read somewhere, that death certificates can have a note
> placed on them, with actual supporting facts.
>
> I suppose the place to find out if this is correct would be the health
> department in the county the certficate was issued out of.
>
> Lori
>
>
> ==== Case-Family Mailing List ====
> To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
> case-family-d-request(a)rootsweb.com (Digest mode)
> In the text body type unsubscribe
>
> I have run into a death certificate that gave the man's dead brother as
> his father. Can't even take official documents as last word! The only
> way I found out it was wrong was through a cousin of his!
I believe I read somewhere, that death certificates can have a note
placed on them, with actual supporting facts.
I suppose the place to find out if this is correct would be the health
department in the county the certficate was issued out of.
Lori
I have run into a death certificate that gave the man's dead brother as
his father. Can't even take official documents as last word! The only
way I found out it was wrong was through a cousin of his!
SedonaBlue(a)aol.com wrote:
>
> On the other Hand . . .
> Ms. Cook's article does take on the superior nature of someone that feels
> part of a club and fears that it's exclusivity will be tainted by newcomers.
> I get the feeling that she would like for all of us to remain under a rock
> until the day that we can proudly proclaim ourselves seasoned researchers. I
> will admit to frustration with postings that are naive and imply that only
> one person, in one place, has ever existed with the name about which the
> poster is inquiring. I have been know to tighten my jaw when someone doesn't
> provide dates, locations, etc., in their posts. However, I don't think that
> we need to be relinquished to the library for the next twenty years before
> coming out with our questions. If that were my avenue, I would probably have
> died before getting my data to where it is now. Ms. Cook gives some examples
> of postings and asks why the person didn't look at this record or write for
> that record. I hate to think of the time I might have wasted if that were
> all that I had ever done. In one of my postings, I was concerned about the
> accuracy of birth dates and spellings for two of my great-grandparents. I
> was amazed to be put in touch with a cousin that had many personal records
> for these relations, including a driver's license that ended the debate on
> the birth date. The driver's license belonged to my great-grandfather that
> died 46 years ago. I am still amazed that someone had such a record, but it
> was out there. Yes, I could have done research the old fashioned way, but I
> could have never found that level of detail in library records, and I was
> convinced by the documents that she had in hand that my new information was
> accurate. Ms. Cook says "Get on your soapbox for the sake of good genealogy
> on the internet." I don't think that this is what she had in mind, so I will
> get off of my soapbox for now.
> Diana Case
>
> ==== Case-Family Mailing List ====
> To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
> case-family-d-request(a)rootsweb.com (Digest mode)
> In the text body type unsubscribe
Amen!!!
----- Original Message -----
From: <SedonaBlue(a)aol.com>
To: <Case-Family-L(a)rootsweb.com>
Sent: Wednesday, November 17, 1999 2:26 PM
Subject: Re: Check out http://www.rootsweb.com/~vaaugust/cook.htm
> I have to agree with posting a caveat to the LDS CDs (Although, I do plan
to
> find a local church that will be showing the training film.) Bad
information
> from the LDS site has turned my database into something that I am not sure
I
> am proud of. I was only able to begin doing genealogy about two years
before
> my family began an internet service, and, of course, progress was slow.
> After getting online (five years ago) and finding the boards and data
sites
> like Ancestory.com, I became an internet / genealogy junky. I will admit
to
> being naive about all of this (still a beginner after all of these years).
> It took me a while to realize that the information on those sites was not
> necessarily well documented, and I am paying the price. It wasn't until
> about three months after the LDS site came online that I started to figure
it
> out -- after getting as many as five birthdates for the same individual.
I
> am ashamed to say that I, initially changed some dates based on someone
elses
> "research," because I assumed that that everyone else was better at this
than
> I am. (Of course, we all know what they say about assuming things.) I
> think that the biggest problem with these sites is that bad information,
> published often enough, begins to be taken as gospel. Isn't that what
> happens? People sort out the information that applies to their family on
> these sites, and then upload it as research. The same bad information
ends
> up on one site numerous times. I recently read several posts from a
distant
> cousin. He claimed to have extensive information on one of my lines, and
he
> was correcting other postings with a real air of authority. I think that
> many of us on the board were excited that we were about to receive a gold
> mine of information. Later he posted a genealogy report that had his
source
> information in parenthesis. Every source was a number from the LDS site.
I
> was deflated. I couldn't believe that he had us all going that way.
Didn't
> it occur to him that any of us could have gone to the LDS site and plugged
in
> names, just as he had done? I have not been willing to send my
information
> to the Ancestry site, because I don't feel that it is documented well
enough,
> but it's tough to ignore their constant prompts. Maybe its those pleads
for
> uploads that are partly responsible for the enourmous amount of bad data.
If
> I could ever figure out how to segregate portions of my database that I
feel
> sure of, I might send something in. As it is, everything is in one
database.
> I know which portions are researched well and which ones aren't, but I
> couldn't convey that if it were posted for all of the world to see.
Anyway,
> I hope that this keeps someone else from making the same mistakes that I
have
> made.
>
> Diana Case
>
>
>
>
> If I could ever figure out how to segregate the portions of my database
that
> are well researched from those that aren't, I might be willing to send
> something in, but, for now, there is too much there that has been taken
from
> these online sites. I think that the biggest problem with these sites
is
> th.at bad information published often enough is taken as gospel.
>
>
> ==== Case-Family Mailing List ====
> To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
> case-family-d-request(a)rootsweb.com (Digest mode)
> In the text body type unsubscribe
>
Hi Diana,
I never take anything I get off the net as proven. I hope most people
don't. I always use it as a reference to do my own research. Many people
will give you citations which are easy to check.
The LDS has an enormous amount of records of all sorts..actual parish,
census, tax rolls, genealogies, vital stats, cemetary records...you name
it and they have it on microfilm or fiche. You can order that in for the
amount of postage.Easily check out info individuals ..many of whom are
not LDS members, have submitted to the Ancestral File or IGI.
I enjoy the fun of research first hand..digging through town clerk's
records or old newspapers, tromping through cemetaries, going to various
historical societies, etc. (~: But many leads have came from online
info.
S.K. Garrett
Genealogists never die they just lose their census.
In a message dated 11/17/1999 6:56:01 PM Eastern Standard Time,
allenw(a)ptsi.net writes:
<< I have run into a death certificate that gave the man's dead brother as
his father. Can't even take official documents as last word! >>
Death certificate information is given by a family menber just after the
death. Many times that family member is quite upset and not thinking as
clearly as they would be under normal circumstances. I have seen it on death
certificates in my own family. The mind goes blank and they speak the first
name that pops into their head. It's excusable under the circumstance, but
it creates a headache for the researcher....Lois
On the other Hand . . .
Ms. Cook's article does take on the superior nature of someone that feels
part of a club and fears that it's exclusivity will be tainted by newcomers.
I get the feeling that she would like for all of us to remain under a rock
until the day that we can proudly proclaim ourselves seasoned researchers. I
will admit to frustration with postings that are naive and imply that only
one person, in one place, has ever existed with the name about which the
poster is inquiring. I have been know to tighten my jaw when someone doesn't
provide dates, locations, etc., in their posts. However, I don't think that
we need to be relinquished to the library for the next twenty years before
coming out with our questions. If that were my avenue, I would probably have
died before getting my data to where it is now. Ms. Cook gives some examples
of postings and asks why the person didn't look at this record or write for
that record. I hate to think of the time I might have wasted if that were
all that I had ever done. In one of my postings, I was concerned about the
accuracy of birth dates and spellings for two of my great-grandparents. I
was amazed to be put in touch with a cousin that had many personal records
for these relations, including a driver's license that ended the debate on
the birth date. The driver's license belonged to my great-grandfather that
died 46 years ago. I am still amazed that someone had such a record, but it
was out there. Yes, I could have done research the old fashioned way, but I
could have never found that level of detail in library records, and I was
convinced by the documents that she had in hand that my new information was
accurate. Ms. Cook says "Get on your soapbox for the sake of good genealogy
on the internet." I don't think that this is what she had in mind, so I will
get off of my soapbox for now.
Diana Case
I have to agree with posting a caveat to the LDS CDs (Although, I do plan to
find a local church that will be showing the training film.) Bad information
from the LDS site has turned my database into something that I am not sure I
am proud of. I was only able to begin doing genealogy about two years before
my family began an internet service, and, of course, progress was slow.
After getting online (five years ago) and finding the boards and data sites
like Ancestory.com, I became an internet / genealogy junky. I will admit to
being naive about all of this (still a beginner after all of these years).
It took me a while to realize that the information on those sites was not
necessarily well documented, and I am paying the price. It wasn't until
about three months after the LDS site came online that I started to figure it
out -- after getting as many as five birthdates for the same individual. I
am ashamed to say that I, initially changed some dates based on someone elses
"research," because I assumed that that everyone else was better at this than
I am. (Of course, we all know what they say about assuming things.) I
think that the biggest problem with these sites is that bad information,
published often enough, begins to be taken as gospel. Isn't that what
happens? People sort out the information that applies to their family on
these sites, and then upload it as research. The same bad information ends
up on one site numerous times. I recently read several posts from a distant
cousin. He claimed to have extensive information on one of my lines, and he
was correcting other postings with a real air of authority. I think that
many of us on the board were excited that we were about to receive a gold
mine of information. Later he posted a genealogy report that had his source
information in parenthesis. Every source was a number from the LDS site. I
was deflated. I couldn't believe that he had us all going that way. Didn't
it occur to him that any of us could have gone to the LDS site and plugged in
names, just as he had done? I have not been willing to send my information
to the Ancestry site, because I don't feel that it is documented well enough,
but it's tough to ignore their constant prompts. Maybe its those pleads for
uploads that are partly responsible for the enourmous amount of bad data. If
I could ever figure out how to segregate portions of my database that I feel
sure of, I might send something in. As it is, everything is in one database.
I know which portions are researched well and which ones aren't, but I
couldn't convey that if it were posted for all of the world to see. Anyway,
I hope that this keeps someone else from making the same mistakes that I have
made.
Diana Case
If I could ever figure out how to segregate the portions of my database that
are well researched from those that aren't, I might be willing to send
something in, but, for now, there is too much there that has been taken from
these online sites. I think that the biggest problem with these sites is
th.at bad information published often enough is taken as gospel.
<A HREF="http://www.rootsweb.com/~vaaugust/cook.htm">Click here:
http://www.rootsweb.com/~vaaugust/cook.htm</A>
http://www.rootsweb.com/~vaaugust/cook.htm
Yesterday I sent information on the LDS offering 5 CD's for sale. A fellow
on line researcher and I were discussing the validity of information to be
found on the CD's, as well as other information gleaned from the net. If you
are a beginner at researching your ancestry, or, perhaps have been at it for
years, you would do well to read the page you will find at the above address.
And thanks A.R. for sharing the page with me..... Lois
For any one interested in familysearch from the LDS chuch... thought I would
share this with all of you... Any one is welcome to go to the nearest LDS
chuch on Thursday night and watch this broadcast..you don't have to be LDS
to go.
FAMILY SEARCH BROADCAST ON THURSDAY
The Church has announced a genealogy training program that will be
broadcast via the Church's satellite. The program will describe how
resources provided online via "familysearch.com" can assist members with
their family history activities. All interested members are invited to
attend. The broadcast will be sent to Church buildings equipped with
satellite receivers in North America on Thursday, November 18 at 6:10pm
MST and again at 8:10pm MST; it will be repeated to the Western Europe
receivers on Sunday, November 21, 1999 at times corresponding to 11:10am
MST.
=====
PEDIGREE RESOURCE FILE DATABASE RELEASED
See http://www.desnews.com/cgi-bin/libstory_reg?dn99&9911150026
<A HREF="http://www.desnews.com/cgi-bin/libstory_reg?dn99&9911150026">Link</
A>
The Church has announced a new 5-CD set of information that provides even
more help to genealogists. The "Pedigree Resource File" contains the
personal family history records submitted through the "Preserve" function
of the popular FamilySearch Internet Genealogy Service. The important
difference between this information and previous compilations is that the
information includes the submitter's name and research notes, and no
attempt is made to combine submissions from different people. A user of
this product will be able to see the information compiled by others, be
able to note and resolve discrepancies, and contact the submitters.
Wilma Fleming Haynes
gencon(a)harborside.com
The only thing I know for sure is that I come from a long line of dead
people.
Can a first cousin, once removed, return?
Cemetery: (n) A marble orchard not to be taken for granite.
Crazy.... is a relative term in MY family.
Genealogy: Chasing your own tale!
Genealogy: It's all relative in the end anyway.
Genealogy: Tracing yourself back to better people.
I trace my family history so I will know who to blame.
It's hard to be humble with ancestors like mine!
Life takes it's toll. Have exact change ready!
Searching for lost relatives? Win the Lottery!
That's strange; half my ancestors are WOMEN!
Do I even WANT ancestors? Some I found I wish I could lose.
Every family tree has some sap in it.
FLOOR: (n) The place for storing your priceless genealogy records.
Friends come and go, but relatives tend to accumulate.
Genealogists do it in the library.
Genealogists live in the past lane.
Genealogists never die, they just lose their roots.
Genealogy: A hay stack full of needles. It's the threads I need.
Genealogy: Collecting dead relatives and sometimes a live cousin!
Genealogy: Where you confuse the dead and irritate the living.
Heredity: Everyone believes in it until their children act like fools!
I looked at my family tree...there were two dogs using it.
I think my family tree is a few branches short of full bloom.
Life is lived forwards, but understood backwards.
My ancestors are hiding in a witness protection program.
My family tree is a few branches short!
Research: What I'm doing, when I don't know what I'm doing.
Take nothing but ancestors, leave nothing but records.
Theory of relativity: If you go back far enough, we're all related.
Sorry that my message sounded rude. Just wanted a little clarification.
Thank you.
----- Original Message -----
From: <Confedtrvl(a)aol.com>
To: <Case-Family-L(a)rootsweb.com>
Sent: Thursday, November 11, 1999 7:17 PM
Subject: Fwd: Veterans Day
>
> --part1_0.9b16a0e0.255ce0d2_boundary
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
>
> In a message dated 11/11/99 5:38:17 PM Pacific Standard Time,
cecerdr(a)gte.net
> writes:
>
> <<
>
>
> > Manon Case of Ohio
> > PFC BTRY A 181 FLD ARTY BN WORLD WAR 11
> > BR. Jan 11, 1919 died Dec. 26, 1870
> > James Case of Mo. CSA died in a Union Prison -Rock Island Ill. 1864.
> > >>
>
> It was supposed to say he died Dec. 26, 1970 instaed of 1870--a
mistake--made
> by me hitting the wrongkey-----OK?
> Peggy Case Aldhizer
>
> --part1_0.9b16a0e0.255ce0d2_boundary
> Content-Type: message/rfc822
> Content-Disposition: inline
>
> Return-Path: <Case-Family-L-request(a)rootsweb.com>
> Received: from rly-zc01.mx.aol.com (rly-zc01.mail.aol.com [172.31.33.1])
by
> air-zc04.mail.aol.com (v62.15) with ESMTP; Thu, 11 Nov 1999 20:38:17
> -0500
> Received: from bl-14.rootsweb.com (bl-14.rootsweb.com [204.212.38.30]) by
> rly-zc01.mx.aol.com (v63.6) with ESMTP; Thu, 11 Nov 1999 20:38:01
> -0500
> Received: (from slist@localhost)
> by bl-14.rootsweb.com (8.9.3/8.9.3) id RAA14477;
> Thu, 11 Nov 1999 17:36:55 -0800 (PST)
> Resent-Date: Thu, 11 Nov 1999 17:36:55 -0800 (PST)
> Message-ID: <005701bf2cad$2a8fe160$91a61c3f@oemcomputer>
> From: "Ce ce" <cecerdr(a)gte.net>
> Old-To: <Case-Family-L(a)rootsweb.com>
> References: <0.bbca6b3f.255c297d(a)aol.com>
> Subject: Re: Veterans Day
> Date: Thu, 11 Nov 1999 17:28:00 -0800
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
> X-Priority: 3
> X-MSMail-Priority: Normal
> X-Mailer: Microsoft Outlook Express 5.00.2314.1300
> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
> Resent-Message-ID: <JYUZUB.A.EiD.382K4(a)bl-14.rootsweb.com>
> To: Case-Family-L(a)rootsweb.com
> Resent-From: Case-Family-L(a)rootsweb.com
> Reply-To: Case-Family-L(a)rootsweb.com
> X-Mailing-List: <Case-Family-L(a)rootsweb.com> archive/latest/1605
> X-Loop: Case-Family-L(a)rootsweb.com
> Precedence: list
> Resent-Sender: Case-Family-L-request(a)rootsweb.com
>
> What is this supposed to say? It looks like he died before he was born.
> ----- Original Message -----
> From: <Confedtrvl(a)aol.com>
> To: <Case-Family-L(a)rootsweb.com>
> Sent: Thursday, November 11, 1999 6:15 AM
> Subject: Veterans Day
>
>
> > Manon Case of Ohio
> > PFC BTRY A 181 FLD ARTY BN WORLD WAR 11
> > BR. Jan 11, 1919 died Dec. 26, 1870
> > James Case of Mo. CSA died in a Union Prison -Rock Island Ill. 1864.
> >
> >
> > ==== Case-Family Mailing List ====
> > To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
> > case-family-d-request(a)rootsweb.com (Digest mode)
> > In the text body type unsubscribe
> >
> >
>
>
> ==== Case-Family Mailing List ====
> To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
> case-family-d-request(a)rootsweb.com (Digest mode)
> In the text body type unsubscribe
>
>
> --part1_0.9b16a0e0.255ce0d2_boundary--
>
>
> ==== Case-Family Mailing List ====
> To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
> case-family-d-request(a)rootsweb.com (Digest mode)
> In the text body type unsubscribe
>
Looks like to me they got the two Wars mixed up. Write them!
Carole
Carole S. Walker in Catawba, South Carolina
mott(a)cetlink.net
AOL INSTANT MESSAGE ADDRESS: walkerc36
ICQ# 22149680
----- Original Message -----
From: Ce ce <cecerdr(a)gte.net>
To: <Case-Family-L(a)rootsweb.com>
Sent: Thursday, November 11, 1999 8:28 PM
Subject: Re: Veterans Day
> What is this supposed to say? It looks like he died before he was born.
> ----- Original Message -----
> From: <Confedtrvl(a)aol.com>
> To: <Case-Family-L(a)rootsweb.com>
> Sent: Thursday, November 11, 1999 6:15 AM
> Subject: Veterans Day
>
>
> > Manon Case of Ohio
> > PFC BTRY A 181 FLD ARTY BN WORLD WAR 11
> > BR. Jan 11, 1919 died Dec. 26, 1870
> > James Case of Mo. CSA died in a Union Prison -Rock Island Ill. 1864.
> >
> >
> > ==== Case-Family Mailing List ====
> > To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
> > case-family-d-request(a)rootsweb.com (Digest mode)
> > In the text body type unsubscribe
> >
> >
>
>
> ==== Case-Family Mailing List ====
> To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
> case-family-d-request(a)rootsweb.com (Digest mode)
> In the text body type unsubscribe
>
What is this supposed to say? It looks like he died before he was born.
----- Original Message -----
From: <Confedtrvl(a)aol.com>
To: <Case-Family-L(a)rootsweb.com>
Sent: Thursday, November 11, 1999 6:15 AM
Subject: Veterans Day
> Manon Case of Ohio
> PFC BTRY A 181 FLD ARTY BN WORLD WAR 11
> BR. Jan 11, 1919 died Dec. 26, 1870
> James Case of Mo. CSA died in a Union Prison -Rock Island Ill. 1864.
>
>
> ==== Case-Family Mailing List ====
> To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
> case-family-d-request(a)rootsweb.com (Digest mode)
> In the text body type unsubscribe
>
>
--part1_0.9b16a0e0.255ce0d2_boundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In a message dated 11/11/99 5:38:17 PM Pacific Standard Time, cecerdr(a)gte.net
writes:
<<
> Manon Case of Ohio
> PFC BTRY A 181 FLD ARTY BN WORLD WAR 11
> BR. Jan 11, 1919 died Dec. 26, 1870
> James Case of Mo. CSA died in a Union Prison -Rock Island Ill. 1864.
> >>
It was supposed to say he died Dec. 26, 1970 instaed of 1870--a mistake--made
by me hitting the wrongkey-----OK?
Peggy Case Aldhizer
--part1_0.9b16a0e0.255ce0d2_boundary
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <Case-Family-L-request(a)rootsweb.com>
Received: from rly-zc01.mx.aol.com (rly-zc01.mail.aol.com [172.31.33.1]) by
air-zc04.mail.aol.com (v62.15) with ESMTP; Thu, 11 Nov 1999 20:38:17
-0500
Received: from bl-14.rootsweb.com (bl-14.rootsweb.com [204.212.38.30]) by
rly-zc01.mx.aol.com (v63.6) with ESMTP; Thu, 11 Nov 1999 20:38:01
-0500
Received: (from slist@localhost)
by bl-14.rootsweb.com (8.9.3/8.9.3) id RAA14477;
Thu, 11 Nov 1999 17:36:55 -0800 (PST)
Resent-Date: Thu, 11 Nov 1999 17:36:55 -0800 (PST)
Message-ID: <005701bf2cad$2a8fe160$91a61c3f@oemcomputer>
From: "Ce ce" <cecerdr(a)gte.net>
Old-To: <Case-Family-L(a)rootsweb.com>
References: <0.bbca6b3f.255c297d(a)aol.com>
Subject: Re: Veterans Day
Date: Thu, 11 Nov 1999 17:28:00 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Resent-Message-ID: <JYUZUB.A.EiD.382K4(a)bl-14.rootsweb.com>
To: Case-Family-L(a)rootsweb.com
Resent-From: Case-Family-L(a)rootsweb.com
Reply-To: Case-Family-L(a)rootsweb.com
X-Mailing-List: <Case-Family-L(a)rootsweb.com> archive/latest/1605
X-Loop: Case-Family-L(a)rootsweb.com
Precedence: list
Resent-Sender: Case-Family-L-request(a)rootsweb.com
What is this supposed to say? It looks like he died before he was born.
----- Original Message -----
From: <Confedtrvl(a)aol.com>
To: <Case-Family-L(a)rootsweb.com>
Sent: Thursday, November 11, 1999 6:15 AM
Subject: Veterans Day
> Manon Case of Ohio
> PFC BTRY A 181 FLD ARTY BN WORLD WAR 11
> BR. Jan 11, 1919 died Dec. 26, 1870
> James Case of Mo. CSA died in a Union Prison -Rock Island Ill. 1864.
>
>
> ==== Case-Family Mailing List ====
> To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
> case-family-d-request(a)rootsweb.com (Digest mode)
> In the text body type unsubscribe
>
>
==== Case-Family Mailing List ====
To UNSUBSCRIBE send email to: case-family-l-request(a)rootsweb.com or
case-family-d-request(a)rootsweb.com (Digest mode)
In the text body type unsubscribe
--part1_0.9b16a0e0.255ce0d2_boundary--