My friends - Due to some events in the Internet world over the past few days, I am not making a data post today, but do need to mention some items that some of our subscribers may be having to deal with now, or in the near term future. First, many of you are undoubtedly aware that there was a large loss of Internet service as supplied by home.com over the weekend. Depending on the location and "local" carrier of the service, some home.com subscribers were affected, while others were not. In the case of the lists which I host for the JP region, I am currently receiving about 15 bounce messages from home.com addresses. There are about 60 subscribers(total, for all lists)who have home.com addresses, so, at this point, it appears that about 25% were affected. There are various changes being made to try to remedy the situation, especially in the case of those people who were connected to the Internet through the AT&T network. AT&T has been able to switch addresses for many people, which enabled them to get back on-line again. However, this causes problems for those folks who are subbed to mail lists under the old home.com address. I am getting a fair number of requests from subscribers to change e-mail addresses. This can be done by each individual, and here is the process by which it is done: Configure the e-mail program so that the "Reply-to" address is the old address. With that done, send a message to Listname-L-request@rootsweb.com(substituting the actual name of the list for the word Listname, such as KYJacksonPurchase-L-request@rootsweb.com), with nothing in the Subject header and only the word Unsubscribe in the message body area. The word "request" must be in the address string so that the RootsWeb server, which keys in on the Reply-to address, will recognize the message as a command. After that message has been sent, reconfigure the e-mail program to show the new e-mail address as the Reply-to address, and then send another message to the same address as the unsub message was sent, except, in this case, the word Subscribe is placed in the message body. This process will unsub the old address and subscribe the new one. This home.com situation has caused a considerable amount of disruption and has been the topic of much discussion on the lists to which the list hosts subscribe. It causes additional problems, because the bounce message that come back to us do not contain the abbreviated address which is the one under which the subscription was originally set up - the address is expanded to include things like ".....@excite.home.com, which does not register with the RootsWeb server, and therefore the server will not automatically unsub an address after a certain number of bounces - the addresses have to be unsubbed manually by each list host. Some list hosts have unsubbed all home.com addresses, but, because certain parts of the world were not affected by this situation, I have elected to wait until it appears that all of the home.com addresses that are now bouncing are legitimate non-working addresses, and not someone who simply has an over quota inbox or other problem. All of this will be transparent to the lists, but I did want to acknowledge the fact that I am aware of the situation and the problem and will deal with it accordingly. Anyone who is experiencing a problem in this area with the lists which I host can contact me by *private* e-mail(not through the lists, please), and I will try to be of assistance. I can also report, just as an FYI, that the proliferation of the new BadTrans worm seems to have been reversed. I have received only 3 messages today which were infected with this pesky nuisance. It has served as a good reminder to all of us to never open unexpected and unknown attachments, and to always have a good anti-virus program running and to keep it updated. In the world of genealogy as a whole, and as another FYI, RootsWeb/Ancestry has pulled down the on-line vital statistics birth databases for California and Texas, which were accessible through their home site. There has been a considerable uproar in California over the potential for identity theft through the use of such on-line records, and it appears that RootsWeb/Ancestry has decided to wait out the final result of all of that. This is not a topic for discussion on any of our JP based lists, but I did want to mention it in case anyone who may not be aware of the situation attempts to access those databases and find a "Permission Denied" screen appearing. We will resume data posts on the JP List tomorrow. I will complete sending out the Graves County Order Book G page images that have been requested by the end of the day today, and I can then proceed with digitizing the next 25 pages. As I have mentioned before, we are moving along at a much faster clip than I had anticipated, which is good news, since I will get to the pages with the higher numbers(which many of you are apparently awaiting, based on messages I have received)much sooner than I had anticipated. -B =============================================================================