This is a multi-part message in MIME format. --part0_910556813_boundary Content-ID: <0_910556813@inet_out.mail.aol.com.1> Content-type: text/plain; charset=US-ASCII Forwarded to the list. --part0_910556813_boundary Content-ID: <0_910556813@inet_out.mail.aol.com.2> Content-type: message/rfc822 Content-transfer-encoding: 7bit Content-disposition: inline From: NavyDoc@aol.com Return-path: <NavyDoc@aol.com> To: khume@netcomuk.co.uk Subject: Re: [CHASE-L] WWW Site update. Date: Sun, 8 Nov 1998 15:26:00 EST Mime-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Keith, and others, I haven't mailed you a gedcom, but I do mail them via AOL all the time and have not had any problems doing so. Part of the problem may just as easily be the genealogy program used. Assuming the mailer knows how to create a gedcom from their genealogy program (and programs like FamilyTreemaker have an export option in which one may choose to export as an FTW file or several types of gedcoms) the process is as follows: 1) Open a new e-mail message to the individual to whom you would like to send a gedcom (they cannot be sent to a rootsweb listserve group). 2) Fill out the "send to", "subject" and body of the message as per routine 3) Click the "attachments" button (to the left, in AOL 3.0, or at the bottom of the message in AOL 4.0). 4) Locate your gedcom file, double click on it. You will see the name of the file appear below the e-mail message. 5) Click OK 6) Click the "send" button. You should see a box with a blue line come across it indicating the gedcom is uploading to the mail server. When it finishes you should get the message "message sent." Then you are done. Note: If you are getting gedcoms in the body of a message, it can only come from someone trying to drag and drop it into a message or cut and paste it into a message. But that is not how it is done. Hope this helps. Glenn --part0_910556813_boundary--