GABIBB-L Archives

From: Jack Scarborough <>
Subject: [GABIBB-L] E-mail List
Date: Fri, 16 Apr 1999 09:42:49 -0500

>Hello, My name is Jack Scarborough, & I live in Victoria, Tx. We are hoping
>some one can help us with information with these ancestors; Theophilus
Bateman, >and his wife Jemima McDonald. They were married on 15 October 1829
in Bibb Co, >Georgia. These are the folks I'm trying to find out about (&
their familes..).
>
>I have little information on Theophilus and Jemima McDonald-Bateman, as a
>matter of fact this is all I know about them to this point. If you maybe
able >to give us some direction or help as to how we may find more on these
folks and >their families.
>
>I'll give you the information I have on their only known (to me.) daughter.
>My gggrandmother was Nancy Bateman, b.04 September 1830 in Macon County,
>Georgia. She died 21 May 1921 and is buried at Pike County, Alabama,
>Orion Baptist Church Cemetery.
>
>She was the wife of my gggrandfather John Fletcher Harmon, b.11 June
>1826 (1828 according to some recorsd.) in Newton Co, Georgia. He died
>10 August 1897 and is buried at Pike County, Alabama, Orion Baptist
>Church Cemetery. They had eleven children, six girls and five boys.
>Thank you in advance for you time and help in this matter.
>

I was sent this auto reply, even after I had removed my signature block and
sent the message a second time thinking that once I removed the signature
that the message would post which it did not. I am eager to to post this
query and several others because I had several lines of ancestors live in
Bibb County.
Can anyone tell me how to avoid these auto replies and have my queries post?
Thank you.

>Common reasons for receiving the following message:
>
>1. You sent the command "help".
>
>2. You sent a message to <listname>- 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
><listname>- 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 <list-name>- 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 "", then the -request
>address can be inferred from this to be: "".
>
>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:
>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:
>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.
>
>--
>

This thread:

• [GABIBB-L] E-mail List by Jack Scarborough <>