I'm a subscriber to boards-admin and have received three of your messages in November. There were several responses. Gene At 09:18 AM 12/23/2018, kaesemein--- via LISTOWNERS wrote: >I've sent 4 emails to  <   boards-admins@rootsweb.com > with no response and they haven't shown upin my mailbox either. Is that mailing list working??????   Still trying to give up my boards >Below is the message I keep sending with no response. >Marilyn >*************************************************************** > >I am the board administrator of the following message boards and I want to give them up. > >Message Boards > Localities > North America > United States > States > Ohio > Counties > Allen Message Boards > Localities > North America > United States > States > Ohio > Counties > Clark Message Boards > Localities > North America > United States > States > Ohio > Counties > Fayette Message Boards > Localities > North America > United States > States > Ohio > Counties > FultonMessage Boards > Localities > North America > United States > States > Ohio > Counties > Henry Message Boards > Localities > North America > United States > States > Ohio > Counties > Hocking Message Boards > Localities > North America > United States > States > Ohio > Counties > Madison Message Boards > Localities > North America > United States > States > Ohio > Counties > Medina Message Boards > Localities > North America > United States > States > Ohio > Counties > Meigs Message Boards > Localities > North America > United States > States > Ohio > Counties > Pickaway Message Boards > Localities > North America > United States > States > Ohio > Counties > Portage Message Boards > Localities > North America > United States > States > Ohio > Counties > Preble Message Boards > Localities > North America > United States > States > Ohio > Counties > Wayne Message Boards > Surnames > BertaMessage Boards > Surnames > Borman Message Boards > Surnames > Bormann Message Boards > Surnames > Csiki Message Boards > Surnames > Heitman Message Boards > Surnames > Heitmann > > >After weeks of fishing and questions, I finally received this information.  >"  If you no longer wish to be an administrator, please e-mail the message board staff at messageboards@rootsweb.com and include your username and the name of the board(s) you would no longer wish to administer. " >So my email bounced back with this reply below ! I have tried to contact on 3 or 4 previous occasions at different emailaddresses that I've been given with no luck! >What is going on???Marilyn > >| Your message to messageboards@rootsweb.com couldn't be delivered. > | >| messageboards wasn't found at rootsweb.com. > | >| >| kaesemein | Office 365 | messageboards | >| Action Required | | Recipient | >| >| | | | | | > > | >| Unknown To address | | | > > | >| > >| How to Fix It | >| The address may be misspelled or may not exist. Try one or more of the following: | >| > - Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send. > - Contact the recipient (by phone, for example) to check that the address exists and is correct. > - The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly. > - Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.1 in Office 365, and then send the message again. Retype the entire recipient address before selecting Send. > | >| If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Adminssection below. | > > | >| >Was this helpful? Send feedback to Microsoft. | >| | >| >More Info for Email Admins | >| Status code: 550 5.1.1 > >This error occurs because the sender sent a message to an email address outside of Office 365, but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following: > >The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages. > >Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory. > >Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature. > >Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly. > >For more information and additional tips to fix this issue, see Fix email delivery issues for error code 550 5.1.1 in Office 365. > > | >| Original Message Details | >| >| Created Date: | 11/25/2018 5:28:38 PM | >| Sender Address: | kaesemein@aol.com | >| Recipient Address: | messageboards@rootsweb.com | >| Subject: | Giving up Message Boards | > > | >| >Error Details | >| >| Reported error: | 550 5.1.1 <messageboards@rootsweb.com>: Recipient address rejected: User unknown in local recipient table | >| DSN generated by: | BL0PR16MB2642.namprd16.prod.outlook.com | >| Remote server: | rwlistsmail.rootsweb.com | > > | > > > >| Message Hops | >| HOP | TIME (UTC) | FROM | TO | WITH | RELAY TIME | >| 1 | 11/25/2018 >5:28:43 PM | sonic.gate.mail.ne1.yahoo.com | sonic309.consmr.mail.ne1.yahoo.com | HTTP | 5 sec | >| 2 | 11/25/2018 >5:28:44 PM | sonic309-21.consmr.mail.ne1.yahoo.com | mx0b-002f8e01.pphosted.com | ESMTP | 1 sec | >| 3 | 11/25/2018 >5:28:44 PM | pps.filterd | mx0b-002f8e01.pphosted.com | SMTP | * | >| 4 | 11/25/2018 >5:28:45 PM | mx0a-002f8e01.pphosted.com | CO1NAM05FT031.mail.protection.outlook.com | Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) | 1 sec | >| 5 | 11/25/2018 >5:28:45 PM | CO1NAM05FT031.eop-nam05.prod.protection.outlook.com | CY4PR16CA0040.outlook.office365.com | Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) | * | >| 6 | 11/25/2018 >5:28:45 PM | CY4PR16CA0040.namprd16.prod.outlook.com | BL0PR16MB2642.namprd16.prod.outlook.com | Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) | * | > >Original Message HeadersReceived: from CY4PR16CA0040.namprd16.prod.outlook.com (2603:10b6:910:60::27) > by BL0PR16MB2642.namprd16.prod.outlook.com (2603:10b6:208:30::12) with > Microsoft SMTP Server (version=TLS1_2, > cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1339.28; Sun, 25 Nov > 2018 17:28:45 +0000 >Received: from CO1NAM05FT031.eop-nam05.prod.protection.outlook.com > (2a01:111:f400:7e50::206) by CY4PR16CA0040.outlook.office365.com > (2603:10b6:910:60::27) with Microsoft SMTP Server (version=TLS1_2, > cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1361.15 via Frontend > Transport; Sun, 25 Nov 2018 17:28:45 +0000 >Authentication-Results: spf=softfail (sender IP is 148.163.143.216) > smtp.mailfrom=aol.com; rootsweb.com; dkim=pass (signature was verified) > header.d=aol.com;rootsweb.com; dmarc=pass action=none > header.from=aol.com;compauth=pass reason=100 >Received-SPF: SoftFail (protection.outlook.com: domain of transitioning > aol.com discourages use of 148.163.143.216 as permitted sender) >Received: from mx0a-002f8e01.pphosted.com (148.163.143.216) by > CO1NAM05FT031.mail.protection.outlook.com (10.152.96.143) with Microsoft SMTP > Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id > 15.20.1382.7 via Frontend Transport; Sun, 25 Nov 2018 17:28:45 +0000 >Received: from pps.filterd (m0143794.ppops.net [127.0.0.1]) > by mx0b-002f8e01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id wAPHQtXk019278 > for <messageboards@rootsweb.com>; Sun, 25 Nov 2018 10:28:44 -0700 >Authentication-Results-Original: ppops.net; spf=pass > smtp.mailfrom=kaesemein@aol.com; dkim=pass header.d=aol.com header.s=a2048; > dmarc=pass header.from=aol.com >Received: from sonic309-21.consmr.mail.ne1.yahoo.com (sonic309-21.consmr.mail.ne1.yahoo.com [66.163.184.147]) > by mx0b-002f8e01.pphosted.com with ESMTP id 2ny4nqauc2-1 > (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) > for <messageboards@rootsweb.com>; Sun, 25 Nov 2018 10:28:44 -0700 >DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aol.com; s=a2048; t=1543166923; bh=qnWJKx/A6r1jm48d1ZtQ2b29NNn8/8ERBJaZn2SDZqo=; h=Date:From:To:Subject:References:From:Subject; b=K+nbyHhrvuximperHnjIOW6Nez1+eP9HzwFYNUqZCoVqH7Il1QFCYFsDxukVOudXzvQXTJMQhDUpU4nDuX5xvPtGSr8hbaJR4URnc9MaPg+ybLN0e5SlQ/XB5Q6fsuCuK7dnpRPG3NwYy84ZTaVLRv+vJ89/riqwcaiQhv+gxnv0HoxeueTioriwMzfVLrQlqdVyATmTxFpWdgfsY1GS9Pn6udAQE5VhqmezctLozYSU+p7sU4W+QJOoVG+p2Hm2QHSw/qqkE6zvtKdBcxDJyorgQZD2T1lf4piZFi6IGkpvGM9Eo1tkeec+E/FZS6Lk6TyxwNfWL6nADovPxhXR/Q== >X-YMail-OSG: JaiLTpUVM1ntfiucTv5PrF1cQHItROs997CE_w5KrDGVn26n5xO_PfwkfolkiDk > TDa395HMTeTjRosEkY_Hh.Ujc_7bNgEOuUS2eQiqcQ.NRGyXguN2BWDRrIDK3B1REkJicFXTcntQ > GVr69sucFFtw33JsnTtTe3WVWoEvMKZ8H36VKmaMqNvFoGETxKXMRjEwTXFz2HXfFaDbMo44SnQd > Twmv0YVlnayUwRx2FX47RJawU4j92zWvKGZQoCiss2tA9B1DpsTAMGTjn3Hvd6QEjeCv4BKnbT2M > F4XV4WzOa6o_lHVQXpfEHtmcltQtbPVK1rH.qwGiDT68fOJD7_iEz9As.Z1Gj.R1LV2cDqpFc3h0 > lqrJNc9QR43YNl73AtkCT9S_kK1OZOZbFJU1xIdr0RdFazYyOfpmwrlQNXzqVoRvFJBTir8pC_lI > Md46bCL_EkNdEGkkzX52ml2fP7BO_KhGHHm78ifByI4cj_s7kJsTu8AJBHtiMXI.C6ZYkljHsPR7 > NLbuE.BdEEQsIGngliPWamdvyYYYDbQm32BZtx78FwJ2kMMQQH8CkDaW5sPrgqqsYGXz7XiLOlkg > XkzhTT71jNT8PiTcIaqkmHm_XmB10dQx5uNc07teP5CZboLSxDpbRb6YVyw2d6DBx0zrdtXmAYYk > 8onsQpuHekmco5w2SCF78K3Zg0sfcO4iP0vDs_2qJ6wn3wHFdkL7bRhG47rpzFrZDZvgVadpAP4r > WFU_d6wKFZSD6PuGjPn704vZFCvlsA7JuVZ1pFZ1Y92AtLJIBU89Y8A1aIE06YFdD3IUv6RjWBYh > NtjMvmYwYSpHVCse5jfmV1lFQw_pInuInos0Zj25YA4ngQ7eRV3KILvjbZuuc978ckuLegMRlJuU > RaCCA_SEQM5WoQIHmsr7D5vxbQyV8vsm2q.dw9PIUyDIIfdbrf9_HVueOPdF8x8lcu_CnYXZyv.2 > RcUGsdV4hX8wScPnXkvtn1PJZUBqHGg-- >Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.ne1.yahoo.com with HTTP; Sun, 25 Nov 2018 17:28:43 +0000 >Date: Sun, 25 Nov 2018 17:28:38 +0000 (UTC) >From: <kaesemein@aol.com> >To: messageboards@rootsweb.com >Message-ID: <2111899794.2298688.1543166918078@mail.yahoo.com> >Subject: Giving up Message Boards >MIME-Version: 1.0 >Content-Type: multipart/alternative; > boundary="----=_Part_2298687_2115824924.1543166918075" >References: <2111899794.2298688.1543166918078.ref@mail.yahoo.com> >X-Mailer: WebService/1.1.12729 aolwebmail Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 >X-CLX-Shades: MLX >X-CLX-Response: 1TFkXExoRCkx6FxgfHBEKWU0XZ2ZyEQpZSRcacRoQGncGHRpxHhAadwYYGgY aEQpZXhdsbHkRCklGF0tESU9ZXlhTdUJFWV5PThEKQ04XQW5+TBlOdR5FeU1df09yfGkaa1p4GW 5/QRJhY3JPfUsRClhcFx8EGgQbHx8HHBITG0kcSE4FGxoEGxsaBB4SBBsQGx4aHxoRCl5ZF35nY > 2hEEQpNXBcSEQpMWhdoQ01raxEKRVkXb2trEQpMRhdva2tva2sRCkNaFxwcBBscGQQbEh4EGx4d EQpCXhcbEQpCXBcbEQpeThcbEQpCSxdoeGlAT0F5RRN/WREKQkkXaHhpQE9BeUUTf1kRCkJFF2h BQHhSWRgca1x8EQpCThdoeGlAT0F5RRN/WREKQkwXY25ae2lhcnJQUEwRCkJsF2NuWntpYXJyUF > BMEQpCQBdvZWB9GUxnUGhcSREKQlgXYUtrfAFEBRobb0MRCk1eFxsRClpYFxgRCnBoF3pDGGZDA X5tAWNhEBkaEQpwaBdvZm4FSx4BS1tgbRAZGhEKcGgXbXJETUNETBJDXXgQGRoRCnBoF2VcQlBw T2NBH2NgEBkaEQpwaBdoaGh4QxsbZ2VpZBAZGhEKbX4XGxEKWE0XSxEg >X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-11-25_15:,, > signatures=0 >X-Proofpoint-Spam-Details: rule=inbound_notspam policy=inbound score=0 priorityscore=256 > malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 > clxscore=90 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=559 > adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 > engine=8.0.1-1810050000 definitions=main-1811250092 >Return-Path: kaesemein@aol.com >X-EOPAttributedMessage: 0 >X-EOPTenantAttributedMessage: fcf82d21-fd42-46be-a4f5-537daf908555:0 >X-Forefront-Antispam-Report: > CIP:148.163.143.216;IPV:CAL;SCL:-1;CTRY:US;EFV:NLI;SFV:SKN;SFS:;DIR:INB;SFP:;SCL:-1;SRVR:BL0PR16MB2642;H:mx0a-002f8e01.pphosted.com;FPR:;SPF:None;LANG:en; >X-Microsoft-Exchange-Diagnostics: 1;CO1NAM05FT031;1:DNCso6STi1rTOOPr3zQlXcmJyqkeD5r+IU6ut2zWwdQV5BnQ+ol5/qUuyqh2r+F3WbvNIDvooD7V5LAFROKxKJI+ascymtOKXQQVUgOWGbVbpMAkmee6ChrLvPi0Oyuj >X-MS-PublicTrafficType: Email >X-MS-Office365-Filtering-Correlation-Id: 0a32c808-2f5e-437b-7934-08d652fb73e4 >X-Microsoft-Antispam: > BCL:0;PCL:0;RULEID:(2390098)(7020095)(4652040)(5600074)(711020)(4605076)(4608076)(1401299)(8001031)(1421009)(1402068)(71702078);SRVR:BL0PR16MB2642; >X-Microsoft-Exchange-Diagnostics: > 1;BL0PR16MB2642;3:aP8GrU08AB6SMlgex2Fo9JABRlk1O+wSATy1DK21uzkCuAFrwOcvmSj+ea879/TxF2sMJYF8kXqXNOi+1c/vwCiskoNwoO5WvgUMaHZNQP3ToBaXUWTNTbGjz09lqyztSK0qUBwpCUlSyq4SEepZUaq9Kg07/R2lB9PMI9PF5l0CyION3bC4G5peeV2fUh5tCpuJZY+i+LcUEyNevzvUdY9YSDbvYGBy8MQzmAKcW5HB4Aek2rd5zq/CcSD9j9Ef83nAnermbKTbKNOYpZwNtP+ePq8TdC6YQccFqaXVme7h/51t8xd1ciI2sNcjvCJkHP7bKOvMXhrbUeUQ0I7wQQ8pg36YrFvb/mO2TJ1tfUo=;25:H4f/TtwJguUEh5Ru4BX0+HJxSP7qskg5Q7CHtCufvtYFuf/Z14gLv/ElDPBAE5t5ZvsFvAIIwaCA+HNhnJ2nsUwBWL6G5hat6FHEftv52tJ7LiYPZYZUR+zfFyirWWkfhoUnhTMHuMQvrbqpKrD65SiOizV+KXBe+BOWEDssER+LwKvZVfdth07wGu+DbtGkdWrm3qBdqHr9ciLSQ3ADb+BY5mnIKxwKr5S2VHN6qCZ4Z6E/icOws5SL/15c0ZH6Ojcf59ckq/zuXj7kqAM0zS9YpAlr9Bf4j4hrYlS1czgzIllb/YuPOO0LdhviEBSW26UwbpmDCk/Ic472FRQGhw== >X-MS-TrafficTypeDiagnostic: BL0PR16MB2642: >X-Microsoft-Exchange-Diagnostics: > 1;BL0PR16MB2642;31:gGDOKMEoMz+i8m8j1AlOcz3Jj4A5QfcsWqlpd4gQnXY8Tujbi0nsJ7jEQdindiuSYuI9DXGH4TT8G985SgPw/3eDMpPHX/98cdV6Ui9gyw8UmFJ3Et2nf37QvRqJSlV+iWjDdfVIy7kCGx/oOxVh/Azk3RgtltvR6Jeq1dePKHTVueeUXqLjoU4LzH011s2ltNQm6fOjWPSLaQMknRTJhP0vPbmIvUWdEwGm7DiQ25U=;20:d3Ze6DMcxX/75KnQ7X5WtFCZ6zfrKBzmAEvZ0J7tCgsp89PjrszdS2B4oCKnZDNxPWtd04MkaiDNZMgjJcie49kE6+G2pgtxj3P8QsFK3zHLSESH4VjLF/9ICxDw6BBUtxdXYJuGfd4gnS6ZVEJXbQ1LZmPAQxHJ/yv3QXMOQVpWz6khPtx+uCbqafh3goI/DBYwQubuH74CjrXr4VULU7Kc6YkEtWajoGExvN1AZVYT/CMIrfXlwMA1OTCvtZCAaS3JIikNFMkS8MyES66mmioaiUMJOoUVuLSM2DmhXOtNzTuKwh1dG4Sd6/gKmJoA2CwWzbbhqdTFQbLOiSZxYXzNEL1iDW4BWa7AM//Ze8pwiQpBCyMOJIHbBYY2meLI4w9CeWcBmrrWQh6bcG+m/Y3hbZwL6vc2OE8Y1RrOKqs6uFk4Vl7h4l/L/VqVZEc9Zz3pMZ+3+HfKdYsX0sQHIVbyFCvwpbwWPj6FTx668Fi7abXThgLvHrGjMUTVXCdSAviZIkQggTsPz1Xw7A2WNzkC2w1Z5YZ0LgbXwm91PKQzlnFl0sK/lJWpRXXQe9RD8GQTuAl/hEWwIPSxeaqIgiWocxvdSikvOUhvQmwQpMU= >X-Exchange-Antispam-Report-CFA-Test: > BCL:0;PCL:0;RULEID:(2018062399030)(2018011200283)(2401047)(8121501046)(52410047)(2018011210174)(2018011211064)(2018011212028)(2018011213028)(2018011214028)(2018011215028)(2018011216028)(2018011217028)(2018011218028)(2018011219092)(2018011220252)(2018011221063)(2018011222027)(2018011223027)(2018011224027)(2018011225035)(2018011229035)(2018011232269)(2018011233052)(2018021202149)(98810176)(2018021203149)(98815176)(823300264)(823350442)(823411253)(9101536074)(93006095)(93005095)(10201501046)(3231442)(901025)(902075)(913088)(7045084)(1430557)(1431068)(1432190)(1459058)(1631060)(9311033)(944500087)(944510158)(944921075)(946801078)(946901078)(9300000249)(9301000244)(52103095)(52105112)(52106170)(52408095)(98821027)(98822027)(52401380)(52601095)(52505095)(52406095)(52305095)(52206095)(88860335)(1102011)(3002001)(1610001)(8301001075)(8301003183)(148016)(201708071742011)(7699051)(76991095);SRVR:BL0PR16MB2642;BCL:0;PCL:0;RULEID:;SRVR:BL0PR16MB2642; >X-Microsoft-Exchange-Diagnostics: > 1;BL0PR16MB2642;4:FB9lBOtL83rWvrlReP8JUEtPabYrL+XRcE3w0xN5NqYG7W1V79AjTm4UKhjtEjL6Jp8FYQ72RNLPDm+1oLreyGWPnWMPgjHkAGFYcjp8xclXt83+KR+82Hq73zzR9Tfs8MHUYTbVdGk8bbuWF/XFBNpYiFZHvr1Sq3wFIJk54SmqOUjiD8YwrWoEv7bYWleYUBcJxbDolMbdfSc/kBO8xCEK5LwBDnR9uCB2Fxi8XxWyb6XpIXi4ikrGPEaGyaC3+URyeixeNcSiujK/Kuhgnw==;23:tAETTNZSEw5BvgJOWmtmddoXu66IjZBTDGFsTSD2fYhhfWWrHMcRtwsDA1rn1OlJl2BF7PUfaaP7G56X3Tt0SVHmcyWg2cLCwywUmN+GhG33Z2n/y0JTG7jmmuEPJVH/QSK5TrhM7FFVVGLvpXy5BMb7siMl/xxU7huBjRWyFrflwyXduP0QiFRkM0cMnZ7M >X-Microsoft-Antispam-Message-Info: > =?us-ascii?Q?HT8dYKN/PWXqnRF2Yl4L5a5PpiJ//EON90FtHnSBwqmX/p/hJqJ8fRsVbkVM?= > =?us-ascii?Q?txeAO4sIfr6EXd+WIxetwMRBzoqt2Rcg2J7dIwhGSEdrB+1EmGyKwvBwHlye?= > =?us-ascii?Q?ef73sXRcDl2CX6cex0v+hjTnAr6ZqzsChqvyHBf6dBgSnTs1R+kMj7PKe1tW?= > =?us-ascii?Q?eGMOipL1y8Zn0oNA7GScBDEMJvTmGpj24wZ5eBo/th4V/KlM5QHPLRr/4K3L?= > =?us-ascii?Q?Rx44FF6lGBPnCKWmLogVh9VEqrsLG7etNGNQ+EPCICZu9JGL9eI4AVGPjAWM?= > =?us-ascii?Q?pKuccdOyLLSusKV5fFnhuvgjihXBz6B1pik+sUA4WvqZ7ylqUXhRIeACfxW3?= > =?us-ascii?Q?njI/GEEhIbkl787GgC9ySDy4VDnGlR4Zy/Jm6WOfBKukxjTACtV1HqUe9QND?= > =?us-ascii?Q?3+Ew53DZe9TI32dQTKlMdKL/4K5Ve7z7zX3FxnaWOOU0Jz8IZ+FQhBTawA5p?= > =?us-ascii?Q?JetMrz83z2zFvUxQd8BF+W4OPP5w2RpFsMA1oLoSQQ6zLPLkXpoSccGALQnQ?= > =?us-ascii?Q?ISz2LWWLcQD4mrxKhiUAez8Rj4HwwHmOH+BJkmpn59aYxcrtXp+dewEmEGgc?= > =?us-ascii?Q?zcPtFvGaAKjGZJZqw6/SFRhnWPO/rslchM4/PL4v95XZ9SlktTx/PqMLh0th?= > =?us-ascii?Q?ibbPSGgyG/DFoGg8Z4liuP1DURzNvq58XNrQXGvh7BTE9EbYdvyaPyn3cRI3?= > =?us-ascii?Q?8UlmXO+lbDpHExe5xYZi2f1bATWHmiJiBP9/abQ267hmbtyWs8abkMFEuQqd?= > =?us-ascii?Q?GhNG4su2WvkwF8IjSZwcOS2xxl+xySeH567uvwMVVHCACZzzmkhaGk26y3ks?= > =?us-ascii?Q?DagVZDNMrbZqbhuWxIW2TM7HdXcRwPX/r5vryMj44HpZ+YyQZYcgMR4Lc0IV?= > =?us-ascii?Q?3lMUxSbs5gTl00x6i4g7elPUnOIbaQaqFCP8yq8KK9s1uHif5X0yiLAw6wE0?= > =?us-ascii?Q?76kVsvY8cp2P/GzVMF8cF6VfZyoqrIgGA5gFZXs1M8lwcGABAJWcXl98nbWi?= > =?us-ascii?Q?TLPJPABzFcBhWZzguVtmbkdjqsbH0uJXIwEJ1vTxEvylC8PaODGfdl5gZYO+?= > =?us-ascii?Q?7vpgrbr6BCtWF6Jsy2/MeIjlMS/tNY3Sn7NtJFEK2LZ5rOBP6vfnIWwk3zK4?= > =?us-ascii?Q?f6onT0WsFBXrdsAY5KsQDkzrPgb3mmRasA=3D=3D?= >X-Microsoft-Exchange-Diagnostics: > 1;BL0PR16MB2642;6:kJQVQ1IvVsknp39bP3a8a52m5smpQDJv/7n9HJxkSIacqvAPSGDDXy54BiXIH1b79e4YzgoL2nLC3pCIruC/eFx+t6TrDAjjjuD0KY7W4t4rD5QPncieO8mIb2DmZA/ChXq7Wb+u421ddn9UvZFSZ+E1njT7lV8CGdFriF7QkHQEVbY41U0MR9NWMwuO4SnSSsAEWzoX5JS+TMoqPc2TyIqNHXxUUqGIUt49kW+4yyM/5xbHJgapvKVxCTb8oJpb7qXjAURgPhvxTznsvdhve9nA+fP5Mf3DHWjD6/IGcos3fJ4pLCgfSa9NI9p8yt07bYnzDrWkNjYoQojx8JhGgHEFg3ydcZHYYD+X94kDtO54CZO59WNecsPLu9keoXZ7+mKyuBr8lV31CmV3nDLhCTK8WvZKiw7y1ksleYN0cL6S/SNYHYgYqDZpltzuUJYoJ9VHWGQBfdknx8URt7Me/A==;5:tEBeTeSbI2cm0xVZGv32DuIASl0SfGmUXZHNVIRHQw5R6erLdKpLTKh5c7wY2S5UtatEqtnjSfuGlSajxU4xLB6aQhn2zM1xXnr3KMwPHZ15mDWhRXoSgJUXlSJ2hDiuogaU8YvaNcvC0UpUBsPhRpup+MtGdqUJh1X/rGw84ko=;7:f8nh9qPwllY1LKC7OIHzXu9amvRoZIcdsLFwkJcZTYhFVemtCKpC4frA97xKs2Q3/FkttlCx5F49SA4HfX4O5oMgp9pxUgRHr8sH2X+PzRpvcvvDj6AotWQGV0hKK+3rIfPlGLeLnBP5efj0bkHVYA== >SpamDiagnosticOutput: 1:2 >SpamDiagnosticMetadata: 2d759f38b14c4a58b51c255017c5f971 >X-OriginatorOrg: ancestryonline.onmicrosoft.com >X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Nov 2018 17:28:45.0844 > (UTC) >X-MS-Exchange-CrossTenant-Network-Message-Id: 0a32c808-2f5e-437b-7934-08d652fb73e4 >X-MS-Exchange-CrossTenant-Id: fcf82d21-fd42-46be-a4f5-537daf908555 >X-MS-Exchange-CrossTenant-FromEntityHeader: Internet >X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR16MB2642 >X-OrganizationHeadersPreserved: BL0PR16MB2642.namprd16.prod.outlook.com >X-CrossPremisesHeadersFilteredByDsnGenerator: > BL0PR16MB2642.namprd16.prod.outlook.com >I am the board administrator of the following message boards and I want to give them up. > >Message Boards > Localities > North America > United States > States > Ohio > Counties > Allen Message Boards > Localities > North America > United States > States > Ohio > Counties > Clark Message Boards > Localities > North America > United States > States > Ohio > Counties > Fayette Message Boards > Localities > North America > United States > States > Ohio > Counties > FultonMessage Boards > Localities > North America > United States > States > Ohio > Counties > Henry Message Boards > Localities > North America > United States > States > Ohio > Counties > Hocking Message Boards > Localities > North America > United States > States > Ohio > Counties > Madison Message Boards > Localities > North America > United States > States > Ohio > Counties > Medina Message Boards > Localities > North America > United States > States > Ohio > Counties > Meigs Message Boards > Localities > North America > United States > States > Ohio > Counties > Pickaway Message Boards > Localities > North America > United States > States > Ohio > Counties > Portage Message Boards > Localities > North America > United States > States > Ohio > Counties > Preble Message Boards > Localities > North America > United States > States > Ohio > Counties > Wayne Message Boards > Surnames > BertaMessage Boards > Surnames > Borman Message Boards > Surnames > Bormann Message Boards > Surnames > Csiki Message Boards > Surnames > Heitman Message Boards > Surnames > Heitmann > > > > > > > >_______________________________________________ >Email preferences: http://bit.ly/rootswebpref >Unsubscribe https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com >Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 >Rootsweb Blog: http://rootsweb.blog >RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community > > >--- >This email has been checked for viruses by AVG. >https://www.avg.com
Agree with David 100o/o On Sun, Dec 23, 2018, 11:15 AM W David Samuelsen <dsam52@sampubco.com wrote: > what fiasco? > > 1. Aging Rootsweb servers, requiring moving to new servers > 2. Current management took action to save Rootsweb. Previous management > neglected. > 3. Operating systems were so old, requiring major upgrading > 4. The geek who did Mailman programs for RW lists died, never finished > the upgrading, forcing Ancestry to go full version upgrade. > 5. Not-exploited security flaw discovered in Rootsweb (usernames and > passwords were maintained in a single file anyone could exploit but not > discovered by hackers), requiring total shutdown of RW websites and new > usernames and passwords were reissued. > 6. General Data Protection Regulation (GDPR) went into effect May 2018, > forcing longer shut down of RW websites while the Ancestry IT go through > each site for any living data to remove before reactivate the websites. > (Understood to be over 8,000, so that took them a while to go through > EACH page!) > 7. Admins of Mailing lists vanished without trace. > 8. Facebook, what else is new? > > David Samuelsen > > > On 12/23/2018 8:41 AM, Chris Codrington wrote: > > fiasco at > > RootsWeb/Ancestry this past year > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community >
what fiasco? 1. Aging Rootsweb servers, requiring moving to new servers 2. Current management took action to save Rootsweb. Previous management neglected. 3. Operating systems were so old, requiring major upgrading 4. The geek who did Mailman programs for RW lists died, never finished the upgrading, forcing Ancestry to go full version upgrade. 5. Not-exploited security flaw discovered in Rootsweb (usernames and passwords were maintained in a single file anyone could exploit but not discovered by hackers), requiring total shutdown of RW websites and new usernames and passwords were reissued. 6. General Data Protection Regulation (GDPR) went into effect May 2018, forcing longer shut down of RW websites while the Ancestry IT go through each site for any living data to remove before reactivate the websites. (Understood to be over 8,000, so that took them a while to go through EACH page!) 7. Admins of Mailing lists vanished without trace. 8. Facebook, what else is new? David Samuelsen On 12/23/2018 8:41 AM, Chris Codrington wrote: > fiasco at > RootsWeb/Ancestry this past year
Great question. I wish I could answer it. Hopefully somebody else will. I will also point out that this site: https://mailinglists.rootsweb.com/lists/orphanedLists has said to check back in a couple weeks for a very long time. Mike On 12/23/2018 9:18 AM, kaesemein--- via LISTOWNERS wrote: > I've sent 4 emails to < boards-admins@rootsweb.com > with no response and they haven't shown upin my mailbox either. Is that mailing list working?????? Still trying to give up my boards > Below is the message I keep sending with no response. > Marilyn >
Hello Nivard and others Ive been administering the Carib-Gen List (gatewayed to SocGenWestIndies) since 1997 and have seen it go from being a very dynamic list to utter silence. Any interest held the last four years in the list seems to have been killed by the fiasco at RootsWeb/Ancestry this past year or so. Nivard to your knowledge are there other go-to's serving similar purpose these days via different media such as blogs or FB? Research in the Carib is so darned tricky I would think the group would still be of some use to folks to confer on sources and such but at this stage I cant even get a roll call going. Insights? Chris Codrington Carib-Gen List -----Original Message----- From: Nivard Ovington <ovington.one@gmail.com> Sent: Sunday, December 23, 2018 8:42 AM To: listowners@rootsweb.com Subject: [LO] Re: Inactive Lists Hi Jim If I recall Annes post correctly, those lists with no recent posts were to be made inactive But not removed, the archives were to remain accessible Re gatewayed posts, I think most subscribers were confused by them at best so I don't mourn their passing The boards are still there and accessible Nivard Ovington in Cornwall (UK) On 23/12/2018 12:16, Jim Jackson wrote: > Can someone at some time make request for re-activation of a list > (with compelling arguments) and have it granted? It seems that as > many lists have been marked "Inactive" as are not. Or will the > inactive lists, at some time, be completely removed from the system? > I can see that for those which have no posts, but I am concerned about > those which have posts but have been quiet. Almost all the lists I am > either admin or moderator have been quiet for some time. > > > > I have a personal reason for this concern as Crouch, one of my family > names, is on the "Inactive" roster. > > > > I also disagree with the arguments against continuing forwarding > message board posts to the lists. I have been active with Rootsweb > for 18 years so I have seen a thing or two here. > > > > Jim "Pops" Jackson _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/listown ers@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
I've sent 4 emails to < boards-admins@rootsweb.com > with no response and they haven't shown upin my mailbox either. Is that mailing list working?????? Still trying to give up my boards Below is the message I keep sending with no response. Marilyn *************************************************************** I am the board administrator of the following message boards and I want to give them up. Message Boards > Localities > North America > United States > States > Ohio > Counties > Allen Message Boards > Localities > North America > United States > States > Ohio > Counties > Clark Message Boards > Localities > North America > United States > States > Ohio > Counties > Fayette Message Boards > Localities > North America > United States > States > Ohio > Counties > FultonMessage Boards > Localities > North America > United States > States > Ohio > Counties > Henry Message Boards > Localities > North America > United States > States > Ohio > Counties > Hocking Message Boards > Localities > North America > United States > States > Ohio > Counties > Madison Message Boards > Localities > North America > United States > States > Ohio > Counties > Medina Message Boards > Localities > North America > United States > States > Ohio > Counties > Meigs Message Boards > Localities > North America > United States > States > Ohio > Counties > Pickaway Message Boards > Localities > North America > United States > States > Ohio > Counties > Portage Message Boards > Localities > North America > United States > States > Ohio > Counties > Preble Message Boards > Localities > North America > United States > States > Ohio > Counties > Wayne Message Boards > Surnames > BertaMessage Boards > Surnames > Borman Message Boards > Surnames > Bormann Message Boards > Surnames > Csiki Message Boards > Surnames > Heitman Message Boards > Surnames > Heitmann After weeks of fishing and questions, I finally received this information. " If you no longer wish to be an administrator, please e-mail the message board staff at messageboards@rootsweb.com and include your username and the name of the board(s) you would no longer wish to administer. " So my email bounced back with this reply below ! I have tried to contact on 3 or 4 previous occasions at different emailaddresses that I've been given with no luck! What is going on???Marilyn | Your message to messageboards@rootsweb.com couldn't be delivered. | | messageboards wasn't found at rootsweb.com. | | | kaesemein | Office 365 | messageboards | | Action Required | | Recipient | | | | | | | | | | Unknown To address | | | | | | How to Fix It | | The address may be misspelled or may not exist. Try one or more of the following: | | - Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send. - Contact the recipient (by phone, for example) to check that the address exists and is correct. - The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly. - Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.1 in Office 365, and then send the message again. Retype the entire recipient address before selecting Send. | | If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Adminssection below. | | | Was this helpful? Send feedback to Microsoft. | | | | More Info for Email Admins | | Status code: 550 5.1.1 This error occurs because the sender sent a message to an email address outside of Office 365, but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following: The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages. Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory. Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature. Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly. For more information and additional tips to fix this issue, see Fix email delivery issues for error code 550 5.1.1 in Office 365. | | Original Message Details | | | Created Date: | 11/25/2018 5:28:38 PM | | Sender Address: | kaesemein@aol.com | | Recipient Address: | messageboards@rootsweb.com | | Subject: | Giving up Message Boards | | | Error Details | | | Reported error: | 550 5.1.1 <messageboards@rootsweb.com>: Recipient address rejected: User unknown in local recipient table | | DSN generated by: | BL0PR16MB2642.namprd16.prod.outlook.com | | Remote server: | rwlistsmail.rootsweb.com | | | Message Hops | | HOP | TIME (UTC) | FROM | TO | WITH | RELAY TIME | | 1 | 11/25/2018 5:28:43 PM | sonic.gate.mail.ne1.yahoo.com | sonic309.consmr.mail.ne1.yahoo.com | HTTP | 5 sec | | 2 | 11/25/2018 5:28:44 PM | sonic309-21.consmr.mail.ne1.yahoo.com | mx0b-002f8e01.pphosted.com | ESMTP | 1 sec | | 3 | 11/25/2018 5:28:44 PM | pps.filterd | mx0b-002f8e01.pphosted.com | SMTP | * | | 4 | 11/25/2018 5:28:45 PM | mx0a-002f8e01.pphosted.com | CO1NAM05FT031.mail.protection.outlook.com | Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) | 1 sec | | 5 | 11/25/2018 5:28:45 PM | CO1NAM05FT031.eop-nam05.prod.protection.outlook.com | CY4PR16CA0040.outlook.office365.com | Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) | * | | 6 | 11/25/2018 5:28:45 PM | CY4PR16CA0040.namprd16.prod.outlook.com | BL0PR16MB2642.namprd16.prod.outlook.com | Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) | * | Original Message HeadersReceived: from CY4PR16CA0040.namprd16.prod.outlook.com (2603:10b6:910:60::27) by BL0PR16MB2642.namprd16.prod.outlook.com (2603:10b6:208:30::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1339.28; Sun, 25 Nov 2018 17:28:45 +0000 Received: from CO1NAM05FT031.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e50::206) by CY4PR16CA0040.outlook.office365.com (2603:10b6:910:60::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1361.15 via Frontend Transport; Sun, 25 Nov 2018 17:28:45 +0000 Authentication-Results: spf=softfail (sender IP is 148.163.143.216) smtp.mailfrom=aol.com; rootsweb.com; dkim=pass (signature was verified) header.d=aol.com;rootsweb.com; dmarc=pass action=none header.from=aol.com;compauth=pass reason=100 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning aol.com discourages use of 148.163.143.216 as permitted sender) Received: from mx0a-002f8e01.pphosted.com (148.163.143.216) by CO1NAM05FT031.mail.protection.outlook.com (10.152.96.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1382.7 via Frontend Transport; Sun, 25 Nov 2018 17:28:45 +0000 Received: from pps.filterd (m0143794.ppops.net [127.0.0.1]) by mx0b-002f8e01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id wAPHQtXk019278 for <messageboards@rootsweb.com>; Sun, 25 Nov 2018 10:28:44 -0700 Authentication-Results-Original: ppops.net; spf=pass smtp.mailfrom=kaesemein@aol.com; dkim=pass header.d=aol.com header.s=a2048; dmarc=pass header.from=aol.com Received: from sonic309-21.consmr.mail.ne1.yahoo.com (sonic309-21.consmr.mail.ne1.yahoo.com [66.163.184.147]) by mx0b-002f8e01.pphosted.com with ESMTP id 2ny4nqauc2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <messageboards@rootsweb.com>; Sun, 25 Nov 2018 10:28:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aol.com; s=a2048; t=1543166923; bh=qnWJKx/A6r1jm48d1ZtQ2b29NNn8/8ERBJaZn2SDZqo=; h=Date:From:To:Subject:References:From:Subject; b=K+nbyHhrvuximperHnjIOW6Nez1+eP9HzwFYNUqZCoVqH7Il1QFCYFsDxukVOudXzvQXTJMQhDUpU4nDuX5xvPtGSr8hbaJR4URnc9MaPg+ybLN0e5SlQ/XB5Q6fsuCuK7dnpRPG3NwYy84ZTaVLRv+vJ89/riqwcaiQhv+gxnv0HoxeueTioriwMzfVLrQlqdVyATmTxFpWdgfsY1GS9Pn6udAQE5VhqmezctLozYSU+p7sU4W+QJOoVG+p2Hm2QHSw/qqkE6zvtKdBcxDJyorgQZD2T1lf4piZFi6IGkpvGM9Eo1tkeec+E/FZS6Lk6TyxwNfWL6nADovPxhXR/Q== X-YMail-OSG: JaiLTpUVM1ntfiucTv5PrF1cQHItROs997CE_w5KrDGVn26n5xO_PfwkfolkiDk TDa395HMTeTjRosEkY_Hh.Ujc_7bNgEOuUS2eQiqcQ.NRGyXguN2BWDRrIDK3B1REkJicFXTcntQ GVr69sucFFtw33JsnTtTe3WVWoEvMKZ8H36VKmaMqNvFoGETxKXMRjEwTXFz2HXfFaDbMo44SnQd Twmv0YVlnayUwRx2FX47RJawU4j92zWvKGZQoCiss2tA9B1DpsTAMGTjn3Hvd6QEjeCv4BKnbT2M F4XV4WzOa6o_lHVQXpfEHtmcltQtbPVK1rH.qwGiDT68fOJD7_iEz9As.Z1Gj.R1LV2cDqpFc3h0 lqrJNc9QR43YNl73AtkCT9S_kK1OZOZbFJU1xIdr0RdFazYyOfpmwrlQNXzqVoRvFJBTir8pC_lI Md46bCL_EkNdEGkkzX52ml2fP7BO_KhGHHm78ifByI4cj_s7kJsTu8AJBHtiMXI.C6ZYkljHsPR7 NLbuE.BdEEQsIGngliPWamdvyYYYDbQm32BZtx78FwJ2kMMQQH8CkDaW5sPrgqqsYGXz7XiLOlkg XkzhTT71jNT8PiTcIaqkmHm_XmB10dQx5uNc07teP5CZboLSxDpbRb6YVyw2d6DBx0zrdtXmAYYk 8onsQpuHekmco5w2SCF78K3Zg0sfcO4iP0vDs_2qJ6wn3wHFdkL7bRhG47rpzFrZDZvgVadpAP4r WFU_d6wKFZSD6PuGjPn704vZFCvlsA7JuVZ1pFZ1Y92AtLJIBU89Y8A1aIE06YFdD3IUv6RjWBYh NtjMvmYwYSpHVCse5jfmV1lFQw_pInuInos0Zj25YA4ngQ7eRV3KILvjbZuuc978ckuLegMRlJuU RaCCA_SEQM5WoQIHmsr7D5vxbQyV8vsm2q.dw9PIUyDIIfdbrf9_HVueOPdF8x8lcu_CnYXZyv.2 RcUGsdV4hX8wScPnXkvtn1PJZUBqHGg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.ne1.yahoo.com with HTTP; Sun, 25 Nov 2018 17:28:43 +0000 Date: Sun, 25 Nov 2018 17:28:38 +0000 (UTC) From: <kaesemein@aol.com> To: messageboards@rootsweb.com Message-ID: <2111899794.2298688.1543166918078@mail.yahoo.com> Subject: Giving up Message Boards MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2298687_2115824924.1543166918075" References: <2111899794.2298688.1543166918078.ref@mail.yahoo.com> X-Mailer: WebService/1.1.12729 aolwebmail Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36 X-CLX-Shades: MLX X-CLX-Response: 1TFkXExoRCkx6FxgfHBEKWU0XZ2ZyEQpZSRcacRoQGncGHRpxHhAadwYYGgY aEQpZXhdsbHkRCklGF0tESU9ZXlhTdUJFWV5PThEKQ04XQW5+TBlOdR5FeU1df09yfGkaa1p4GW 5/QRJhY3JPfUsRClhcFx8EGgQbHx8HHBITG0kcSE4FGxoEGxsaBB4SBBsQGx4aHxoRCl5ZF35nY 2hEEQpNXBcSEQpMWhdoQ01raxEKRVkXb2trEQpMRhdva2tva2sRCkNaFxwcBBscGQQbEh4EGx4d EQpCXhcbEQpCXBcbEQpeThcbEQpCSxdoeGlAT0F5RRN/WREKQkkXaHhpQE9BeUUTf1kRCkJFF2h BQHhSWRgca1x8EQpCThdoeGlAT0F5RRN/WREKQkwXY25ae2lhcnJQUEwRCkJsF2NuWntpYXJyUF BMEQpCQBdvZWB9GUxnUGhcSREKQlgXYUtrfAFEBRobb0MRCk1eFxsRClpYFxgRCnBoF3pDGGZDA X5tAWNhEBkaEQpwaBdvZm4FSx4BS1tgbRAZGhEKcGgXbXJETUNETBJDXXgQGRoRCnBoF2VcQlBw T2NBH2NgEBkaEQpwaBdoaGh4QxsbZ2VpZBAZGhEKbX4XGxEKWE0XSxEg X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-11-25_15:,, signatures=0 X-Proofpoint-Spam-Details: rule=inbound_notspam policy=inbound score=0 priorityscore=256 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=90 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=559 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1811250092 Return-Path: kaesemein@aol.com X-EOPAttributedMessage: 0 X-EOPTenantAttributedMessage: fcf82d21-fd42-46be-a4f5-537daf908555:0 X-Forefront-Antispam-Report: CIP:148.163.143.216;IPV:CAL;SCL:-1;CTRY:US;EFV:NLI;SFV:SKN;SFS:;DIR:INB;SFP:;SCL:-1;SRVR:BL0PR16MB2642;H:mx0a-002f8e01.pphosted.com;FPR:;SPF:None;LANG:en; X-Microsoft-Exchange-Diagnostics: 1;CO1NAM05FT031;1:DNCso6STi1rTOOPr3zQlXcmJyqkeD5r+IU6ut2zWwdQV5BnQ+ol5/qUuyqh2r+F3WbvNIDvooD7V5LAFROKxKJI+ascymtOKXQQVUgOWGbVbpMAkmee6ChrLvPi0Oyuj X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 0a32c808-2f5e-437b-7934-08d652fb73e4 X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:(2390098)(7020095)(4652040)(5600074)(711020)(4605076)(4608076)(1401299)(8001031)(1421009)(1402068)(71702078);SRVR:BL0PR16MB2642; X-Microsoft-Exchange-Diagnostics: 1;BL0PR16MB2642;3:aP8GrU08AB6SMlgex2Fo9JABRlk1O+wSATy1DK21uzkCuAFrwOcvmSj+ea879/TxF2sMJYF8kXqXNOi+1c/vwCiskoNwoO5WvgUMaHZNQP3ToBaXUWTNTbGjz09lqyztSK0qUBwpCUlSyq4SEepZUaq9Kg07/R2lB9PMI9PF5l0CyION3bC4G5peeV2fUh5tCpuJZY+i+LcUEyNevzvUdY9YSDbvYGBy8MQzmAKcW5HB4Aek2rd5zq/CcSD9j9Ef83nAnermbKTbKNOYpZwNtP+ePq8TdC6YQccFqaXVme7h/51t8xd1ciI2sNcjvCJkHP7bKOvMXhrbUeUQ0I7wQQ8pg36YrFvb/mO2TJ1tfUo=;25:H4f/TtwJguUEh5Ru4BX0+HJxSP7qskg5Q7CHtCufvtYFuf/Z14gLv/ElDPBAE5t5ZvsFvAIIwaCA+HNhnJ2nsUwBWL6G5hat6FHEftv52tJ7LiYPZYZUR+zfFyirWWkfhoUnhTMHuMQvrbqpKrD65SiOizV+KXBe+BOWEDssER+LwKvZVfdth07wGu+DbtGkdWrm3qBdqHr9ciLSQ3ADb+BY5mnIKxwKr5S2VHN6qCZ4Z6E/icOws5SL/15c0ZH6Ojcf59ckq/zuXj7kqAM0zS9YpAlr9Bf4j4hrYlS1czgzIllb/YuPOO0LdhviEBSW26UwbpmDCk/Ic472FRQGhw== X-MS-TrafficTypeDiagnostic: BL0PR16MB2642: X-Microsoft-Exchange-Diagnostics: 1;BL0PR16MB2642;31:gGDOKMEoMz+i8m8j1AlOcz3Jj4A5QfcsWqlpd4gQnXY8Tujbi0nsJ7jEQdindiuSYuI9DXGH4TT8G985SgPw/3eDMpPHX/98cdV6Ui9gyw8UmFJ3Et2nf37QvRqJSlV+iWjDdfVIy7kCGx/oOxVh/Azk3RgtltvR6Jeq1dePKHTVueeUXqLjoU4LzH011s2ltNQm6fOjWPSLaQMknRTJhP0vPbmIvUWdEwGm7DiQ25U=;20:d3Ze6DMcxX/75KnQ7X5WtFCZ6zfrKBzmAEvZ0J7tCgsp89PjrszdS2B4oCKnZDNxPWtd04MkaiDNZMgjJcie49kE6+G2pgtxj3P8QsFK3zHLSESH4VjLF/9ICxDw6BBUtxdXYJuGfd4gnS6ZVEJXbQ1LZmPAQxHJ/yv3QXMOQVpWz6khPtx+uCbqafh3goI/DBYwQubuH74CjrXr4VULU7Kc6YkEtWajoGExvN1AZVYT/CMIrfXlwMA1OTCvtZCAaS3JIikNFMkS8MyES66mmioaiUMJOoUVuLSM2DmhXOtNzTuKwh1dG4Sd6/gKmJoA2CwWzbbhqdTFQbLOiSZxYXzNEL1iDW4BWa7AM//Ze8pwiQpBCyMOJIHbBYY2meLI4w9CeWcBmrrWQh6bcG+m/Y3hbZwL6vc2OE8Y1RrOKqs6uFk4Vl7h4l/L/VqVZEc9Zz3pMZ+3+HfKdYsX0sQHIVbyFCvwpbwWPj6FTx668Fi7abXThgLvHrGjMUTVXCdSAviZIkQggTsPz1Xw7A2WNzkC2w1Z5YZ0LgbXwm91PKQzlnFl0sK/lJWpRXXQe9RD8GQTuAl/hEWwIPSxeaqIgiWocxvdSikvOUhvQmwQpMU= X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(2018062399030)(2018011200283)(2401047)(8121501046)(52410047)(2018011210174)(2018011211064)(2018011212028)(2018011213028)(2018011214028)(2018011215028)(2018011216028)(2018011217028)(2018011218028)(2018011219092)(2018011220252)(2018011221063)(2018011222027)(2018011223027)(2018011224027)(2018011225035)(2018011229035)(2018011232269)(2018011233052)(2018021202149)(98810176)(2018021203149)(98815176)(823300264)(823350442)(823411253)(9101536074)(93006095)(93005095)(10201501046)(3231442)(901025)(902075)(913088)(7045084)(1430557)(1431068)(1432190)(1459058)(1631060)(9311033)(944500087)(944510158)(944921075)(946801078)(946901078)(9300000249)(9301000244)(52103095)(52105112)(52106170)(52408095)(98821027)(98822027)(52401380)(52601095)(52505095)(52406095)(52305095)(52206095)(88860335)(1102011)(3002001)(1610001)(8301001075)(8301003183)(148016)(201708071742011)(7699051)(76991095);SRVR:BL0PR16MB2642;BCL:0;PCL:0;RULEID:;SRVR:BL0PR16MB2642; X-Microsoft-Exchange-Diagnostics: 1;BL0PR16MB2642;4:FB9lBOtL83rWvrlReP8JUEtPabYrL+XRcE3w0xN5NqYG7W1V79AjTm4UKhjtEjL6Jp8FYQ72RNLPDm+1oLreyGWPnWMPgjHkAGFYcjp8xclXt83+KR+82Hq73zzR9Tfs8MHUYTbVdGk8bbuWF/XFBNpYiFZHvr1Sq3wFIJk54SmqOUjiD8YwrWoEv7bYWleYUBcJxbDolMbdfSc/kBO8xCEK5LwBDnR9uCB2Fxi8XxWyb6XpIXi4ikrGPEaGyaC3+URyeixeNcSiujK/Kuhgnw==;23:tAETTNZSEw5BvgJOWmtmddoXu66IjZBTDGFsTSD2fYhhfWWrHMcRtwsDA1rn1OlJl2BF7PUfaaP7G56X3Tt0SVHmcyWg2cLCwywUmN+GhG33Z2n/y0JTG7jmmuEPJVH/QSK5TrhM7FFVVGLvpXy5BMb7siMl/xxU7huBjRWyFrflwyXduP0QiFRkM0cMnZ7M X-Microsoft-Antispam-Message-Info: =?us-ascii?Q?HT8dYKN/PWXqnRF2Yl4L5a5PpiJ//EON90FtHnSBwqmX/p/hJqJ8fRsVbkVM?= =?us-ascii?Q?txeAO4sIfr6EXd+WIxetwMRBzoqt2Rcg2J7dIwhGSEdrB+1EmGyKwvBwHlye?= =?us-ascii?Q?ef73sXRcDl2CX6cex0v+hjTnAr6ZqzsChqvyHBf6dBgSnTs1R+kMj7PKe1tW?= =?us-ascii?Q?eGMOipL1y8Zn0oNA7GScBDEMJvTmGpj24wZ5eBo/th4V/KlM5QHPLRr/4K3L?= =?us-ascii?Q?Rx44FF6lGBPnCKWmLogVh9VEqrsLG7etNGNQ+EPCICZu9JGL9eI4AVGPjAWM?= =?us-ascii?Q?pKuccdOyLLSusKV5fFnhuvgjihXBz6B1pik+sUA4WvqZ7ylqUXhRIeACfxW3?= =?us-ascii?Q?njI/GEEhIbkl787GgC9ySDy4VDnGlR4Zy/Jm6WOfBKukxjTACtV1HqUe9QND?= =?us-ascii?Q?3+Ew53DZe9TI32dQTKlMdKL/4K5Ve7z7zX3FxnaWOOU0Jz8IZ+FQhBTawA5p?= =?us-ascii?Q?JetMrz83z2zFvUxQd8BF+W4OPP5w2RpFsMA1oLoSQQ6zLPLkXpoSccGALQnQ?= =?us-ascii?Q?ISz2LWWLcQD4mrxKhiUAez8Rj4HwwHmOH+BJkmpn59aYxcrtXp+dewEmEGgc?= =?us-ascii?Q?zcPtFvGaAKjGZJZqw6/SFRhnWPO/rslchM4/PL4v95XZ9SlktTx/PqMLh0th?= =?us-ascii?Q?ibbPSGgyG/DFoGg8Z4liuP1DURzNvq58XNrQXGvh7BTE9EbYdvyaPyn3cRI3?= =?us-ascii?Q?8UlmXO+lbDpHExe5xYZi2f1bATWHmiJiBP9/abQ267hmbtyWs8abkMFEuQqd?= =?us-ascii?Q?GhNG4su2WvkwF8IjSZwcOS2xxl+xySeH567uvwMVVHCACZzzmkhaGk26y3ks?= =?us-ascii?Q?DagVZDNMrbZqbhuWxIW2TM7HdXcRwPX/r5vryMj44HpZ+YyQZYcgMR4Lc0IV?= =?us-ascii?Q?3lMUxSbs5gTl00x6i4g7elPUnOIbaQaqFCP8yq8KK9s1uHif5X0yiLAw6wE0?= =?us-ascii?Q?76kVsvY8cp2P/GzVMF8cF6VfZyoqrIgGA5gFZXs1M8lwcGABAJWcXl98nbWi?= =?us-ascii?Q?TLPJPABzFcBhWZzguVtmbkdjqsbH0uJXIwEJ1vTxEvylC8PaODGfdl5gZYO+?= =?us-ascii?Q?7vpgrbr6BCtWF6Jsy2/MeIjlMS/tNY3Sn7NtJFEK2LZ5rOBP6vfnIWwk3zK4?= =?us-ascii?Q?f6onT0WsFBXrdsAY5KsQDkzrPgb3mmRasA=3D=3D?= X-Microsoft-Exchange-Diagnostics: 1;BL0PR16MB2642;6:kJQVQ1IvVsknp39bP3a8a52m5smpQDJv/7n9HJxkSIacqvAPSGDDXy54BiXIH1b79e4YzgoL2nLC3pCIruC/eFx+t6TrDAjjjuD0KY7W4t4rD5QPncieO8mIb2DmZA/ChXq7Wb+u421ddn9UvZFSZ+E1njT7lV8CGdFriF7QkHQEVbY41U0MR9NWMwuO4SnSSsAEWzoX5JS+TMoqPc2TyIqNHXxUUqGIUt49kW+4yyM/5xbHJgapvKVxCTb8oJpb7qXjAURgPhvxTznsvdhve9nA+fP5Mf3DHWjD6/IGcos3fJ4pLCgfSa9NI9p8yt07bYnzDrWkNjYoQojx8JhGgHEFg3ydcZHYYD+X94kDtO54CZO59WNecsPLu9keoXZ7+mKyuBr8lV31CmV3nDLhCTK8WvZKiw7y1ksleYN0cL6S/SNYHYgYqDZpltzuUJYoJ9VHWGQBfdknx8URt7Me/A==;5:tEBeTeSbI2cm0xVZGv32DuIASl0SfGmUXZHNVIRHQw5R6erLdKpLTKh5c7wY2S5UtatEqtnjSfuGlSajxU4xLB6aQhn2zM1xXnr3KMwPHZ15mDWhRXoSgJUXlSJ2hDiuogaU8YvaNcvC0UpUBsPhRpup+MtGdqUJh1X/rGw84ko=;7:f8nh9qPwllY1LKC7OIHzXu9amvRoZIcdsLFwkJcZTYhFVemtCKpC4frA97xKs2Q3/FkttlCx5F49SA4HfX4O5oMgp9pxUgRHr8sH2X+PzRpvcvvDj6AotWQGV0hKK+3rIfPlGLeLnBP5efj0bkHVYA== SpamDiagnosticOutput: 1:2 SpamDiagnosticMetadata: 2d759f38b14c4a58b51c255017c5f971 X-OriginatorOrg: ancestryonline.onmicrosoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 25 Nov 2018 17:28:45.0844 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 0a32c808-2f5e-437b-7934-08d652fb73e4 X-MS-Exchange-CrossTenant-Id: fcf82d21-fd42-46be-a4f5-537daf908555 X-MS-Exchange-CrossTenant-FromEntityHeader: Internet X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR16MB2642 X-OrganizationHeadersPreserved: BL0PR16MB2642.namprd16.prod.outlook.com X-CrossPremisesHeadersFilteredByDsnGenerator: BL0PR16MB2642.namprd16.prod.outlook.com I am the board administrator of the following message boards and I want to give them up. Message Boards > Localities > North America > United States > States > Ohio > Counties > Allen Message Boards > Localities > North America > United States > States > Ohio > Counties > Clark Message Boards > Localities > North America > United States > States > Ohio > Counties > Fayette Message Boards > Localities > North America > United States > States > Ohio > Counties > FultonMessage Boards > Localities > North America > United States > States > Ohio > Counties > Henry Message Boards > Localities > North America > United States > States > Ohio > Counties > Hocking Message Boards > Localities > North America > United States > States > Ohio > Counties > Madison Message Boards > Localities > North America > United States > States > Ohio > Counties > Medina Message Boards > Localities > North America > United States > States > Ohio > Counties > Meigs Message Boards > Localities > North America > United States > States > Ohio > Counties > Pickaway Message Boards > Localities > North America > United States > States > Ohio > Counties > Portage Message Boards > Localities > North America > United States > States > Ohio > Counties > Preble Message Boards > Localities > North America > United States > States > Ohio > Counties > Wayne Message Boards > Surnames > BertaMessage Boards > Surnames > Borman Message Boards > Surnames > Bormann Message Boards > Surnames > Csiki Message Boards > Surnames > Heitman Message Boards > Surnames > Heitmann
I agree with you Mary. I've given up all my mailing lists and have been trying to give up about 30 message boards butnever get a response so I'm still stuck with them for now. Marilyn -----Original Message----- From: Mary Russell <maryiola@windstream.net> To: Listowners list for Rootsweb list admins and moderators <listowners@rootsweb.com> Sent: Sun, Dec 23, 2018 10:01 am Subject: [LO] Re: Inactive Lists All 28 or more of my surname lists are inactive. Mainly because I think of the confusion on rootsweb, the times we are living in and maybe the list members aging and slowing down like ME, and no doubt many other reasons., I have found over 84 years and 50 of them doing genealogy that most “ improvements” seem to be a step back into confusion. I will admit that most of the subjects you speak of on this list go right over my head. It is sad for me that the friendships and sharing of the past we had on Rootsweb are over. I think if my lists go inactive that I too am finished. It is sad. Mary
Hi Jim If no one has posted to the inactive list in such a long time, it would seem your argument to re-open the list would have to be extremely compelling. What is the point of opening a list if there's no traffic? As far as the message boards, it is a terrible shame that the gateways have been closed. Sending the matching list a synopsis of recent posts (I just send the subject lines and the date range) keeps your listers up to date. Unfortunately, I've gotten out of the habit of updating listers about the message boards because the boards have been as quiet as the lists. Lynne PS Merry Christmas and best wishes for a peaceful, healthy, and happy new year to all! Jim Jackson <listsitter@charter.net> wrote: > >Can someone at some time make request for re-activation of a list (with >compelling arguments) and have it granted? It seems that as many lists have >been marked "Inactive" as are not. Or will the inactive lists, at some >time, be completely removed from the system? I can see that for those which >have no posts, but I am concerned about those which have posts but have been >quiet. Almost all the lists I am either admin or moderator have been quiet >for some time. > > > >I have a personal reason for this concern as Crouch, one of my family names, >is on the "Inactive" roster. > > > >I also disagree with the arguments against continuing forwarding message >board posts to the lists. I have been active with Rootsweb for 18 years so >I have seen a thing or two here.
All 28 or more of my surname lists are inactive. Mainly because I think of the confusion on rootsweb, the times we are living in and maybe the list members aging and slowing down like ME, and no doubt many other reasons., I have found over 84 years and 50 of them doing genealogy that most “ improvements” seem to be a step back into confusion. I will admit that most of the subjects you speak of on this list go right over my head. It is sad for me that the friendships and sharing of the past we had on Rootsweb are over. I think if my lists go inactive that I too am finished. It is sad. Mary From: Nivard Ovington Sent: Sunday, December 23, 2018 7:41 AM To: listowners@rootsweb.com Subject: [LO] Re: Inactive Lists Hi Jim If I recall Annes post correctly, those lists with no recent posts were to be made inactive But not removed, the archives were to remain accessible Re gatewayed posts, I think most subscribers were confused by them at best so I don't mourn their passing The boards are still there and accessible Nivard Ovington in Cornwall (UK) On 23/12/2018 12:16, Jim Jackson wrote: > Can someone at some time make request for re-activation of a list (with > compelling arguments) and have it granted? It seems that as many lists have > been marked "Inactive" as are not. Or will the inactive lists, at some > time, be completely removed from the system? I can see that for those which > have no posts, but I am concerned about those which have posts but have been > quiet. Almost all the lists I am either admin or moderator have been quiet > for some time. > > > > I have a personal reason for this concern as Crouch, one of my family names, > is on the "Inactive" roster. > > > > I also disagree with the arguments against continuing forwarding message > board posts to the lists. I have been active with Rootsweb for 18 years so > I have seen a thing or two here. > > > > Jim "Pops" Jackson _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
I agree totally with you. I still feel abandoned by the present ownership/management. Rootsweb was once a fun and friendly place but has changed since then. Jim Jackson - Smyrna, GA -----Original Message----- From: Jim Barrett [mailto:parino@flash.net] Sent: Sunday, December 23, 2018 8:58 AM To: Listowners list for Rootsweb list admins and moderators Subject: [LO] Re: Inactive Lists - Gatewayed List From a different Jim. Yes, many subscriber were confused by these messages. A real shame as RootsWeb/Ancestry could have made it CLEAR that the message was being gatewayed and even told from which message board. Jim Barrett - Timpson, TX
From a different Jim. Yes, many subscriber were confused by these messages. A real shame as RootsWeb/Ancestry could have made it CLEAR that the message was being gatewayed and even told from which message board. Jim Barrett - Timpson, TX On Sunday, December 23, 2018, 7:42:01 AM CST, Nivard Ovington <ovington.one@gmail.com> wrote: Hi Jim If I recall Annes post correctly, those lists with no recent posts were to be made inactive But not removed, the archives were to remain accessible Re gatewayed posts, I think most subscribers were confused by them at best so I don't mourn their passing The boards are still there and accessible Nivard Ovington in Cornwall (UK) On 23/12/2018 12:16, Jim Jackson wrote: > Can someone at some time make request for re-activation of a list (with > compelling arguments) and have it granted? It seems that as many lists have > been marked "Inactive" as are not. Or will the inactive lists, at some > time, be completely removed from the system? I can see that for those which > have no posts, but I am concerned about those which have posts but have been > quiet. Almost all the lists I am either admin or moderator have been quiet > for some time. > > > > I have a personal reason for this concern as Crouch, one of my family names, > is on the "Inactive" roster. > > > > I also disagree with the arguments against continuing forwarding message > board posts to the lists. I have been active with Rootsweb for 18 years so > I have seen a thing or two here. > > > > Jim "Pops" Jackson _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
Hi Jim If I recall Annes post correctly, those lists with no recent posts were to be made inactive But not removed, the archives were to remain accessible Re gatewayed posts, I think most subscribers were confused by them at best so I don't mourn their passing The boards are still there and accessible Nivard Ovington in Cornwall (UK) On 23/12/2018 12:16, Jim Jackson wrote: > Can someone at some time make request for re-activation of a list (with > compelling arguments) and have it granted? It seems that as many lists have > been marked "Inactive" as are not. Or will the inactive lists, at some > time, be completely removed from the system? I can see that for those which > have no posts, but I am concerned about those which have posts but have been > quiet. Almost all the lists I am either admin or moderator have been quiet > for some time. > > > > I have a personal reason for this concern as Crouch, one of my family names, > is on the "Inactive" roster. > > > > I also disagree with the arguments against continuing forwarding message > board posts to the lists. I have been active with Rootsweb for 18 years so > I have seen a thing or two here. > > > > Jim "Pops" Jackson
Can someone at some time make request for re-activation of a list (with compelling arguments) and have it granted? It seems that as many lists have been marked "Inactive" as are not. Or will the inactive lists, at some time, be completely removed from the system? I can see that for those which have no posts, but I am concerned about those which have posts but have been quiet. Almost all the lists I am either admin or moderator have been quiet for some time. I have a personal reason for this concern as Crouch, one of my family names, is on the "Inactive" roster. I also disagree with the arguments against continuing forwarding message board posts to the lists. I have been active with Rootsweb for 18 years so I have seen a thing or two here. Jim "Pops" Jackson
I have also found old subscription requests in the subscription request tab, and wondered why I didn't know about them sooner. It doesn't happen often, but it has happened. Mike On 12/17/2018 10:51 AM, Anne Mitchell wrote: > Mike, > > That is correct most of the time. I have found that when people don't > receive and respond to the confirmation email, the request remains in the > Subscription Request queue. > Anne > > On Fri, Dec 14, 2018 at 8:47 AM Mike Flannigan <mikeflan@att.net> wrote: > >> Note that under Settings - Subscription Policy, these >> are the options: >> >> Open: Subscriptions are added automatically >> Confirm: Subscribers need to confirm the subscription using an email >> sent to them >> Moderate: Moderators will have to authorize each subscription manually. >> Confirm then Moderate: First subscribers have to confirm, then a >> moderator needs to authorize. >> >> If you are not set to Moderate or Confirm then Moderate, >> then no subscription requests should show up in the >> Subscription Requests tab. >> >> Correct me if I am wrong. >> >> >> Mike >> >>
The "Help" desk told me to subscribe to get help with a problem I was having. I did a few months ago. The problem was resolved and I request was approved about a week ago. Jim Barrett - Timpson, TX On Monday, December 17, 2018, 10:51:49 AM CST, Anne Mitchell <annerootsweb@gmail.com> wrote: Mike, That is correct most of the time. I have found that when people don't receive and respond to the confirmation email, the request remains in the Subscription Request queue. Anne On Fri, Dec 14, 2018 at 8:47 AM Mike Flannigan <mikeflan@att.net> wrote: > > Note that under Settings - Subscription Policy, these > are the options: > > Open: Subscriptions are added automatically > Confirm: Subscribers need to confirm the subscription using an email > sent to them > Moderate: Moderators will have to authorize each subscription manually. > Confirm then Moderate: First subscribers have to confirm, then a > moderator needs to authorize. > > If you are not set to Moderate or Confirm then Moderate, > then no subscription requests should show up in the > Subscription Requests tab. > > Correct me if I am wrong. > > > Mike > > > > On 12/14/2018 8:17 AM, Lynne wrote: > > Uh oh! I knew the subscription request page was there because I've had > to go there to approve subscriptions, but because of this recent thread, > out of curiosity I took a look at the subscription requests for a few of my > lists. Three out of the first five I checked had subscription requests > pending for which I've never received notification. Then I checked all my > lists and found about 20 more subscription requests. All of those lists > were set for Confirm under the subscription policy. I've approved all of > the subscription requests (who knows how long they've been sitting there!) > and changed all of the lists' subscription policy to Open. > > > > Might be a good idea for all of us to check for subscription requests. > > > > Lynne > > > > > > Joan Young <jyoung6180@aol.com> wrote: > >> Thank you thank you! I have to admit <blush> I never knew that page was > THERE. It worked...and I see other requests there also but I have no idea > how old they may be ... so for now I'm leaving them alone. > >> > >> > >> Joan Young > >> jyoung6180@aol.com<mailto:jyoung6180@aol.com> > >> > > > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community > _______________________________________________ Email preferences: http://bit.ly/rootswebpref Unsubscribe https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: https://ancstry.me/2HDBym9 Rootsweb Blog: http://rootsweb.blog RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb community
Mike, That is correct most of the time. I have found that when people don't receive and respond to the confirmation email, the request remains in the Subscription Request queue. Anne On Fri, Dec 14, 2018 at 8:47 AM Mike Flannigan <mikeflan@att.net> wrote: > > Note that under Settings - Subscription Policy, these > are the options: > > Open: Subscriptions are added automatically > Confirm: Subscribers need to confirm the subscription using an email > sent to them > Moderate: Moderators will have to authorize each subscription manually. > Confirm then Moderate: First subscribers have to confirm, then a > moderator needs to authorize. > > If you are not set to Moderate or Confirm then Moderate, > then no subscription requests should show up in the > Subscription Requests tab. > > Correct me if I am wrong. > > > Mike > > > > On 12/14/2018 8:17 AM, Lynne wrote: > > Uh oh! I knew the subscription request page was there because I've had > to go there to approve subscriptions, but because of this recent thread, > out of curiosity I took a look at the subscription requests for a few of my > lists. Three out of the first five I checked had subscription requests > pending for which I've never received notification. Then I checked all my > lists and found about 20 more subscription requests. All of those lists > were set for Confirm under the subscription policy. I've approved all of > the subscription requests (who knows how long they've been sitting there!) > and changed all of the lists' subscription policy to Open. > > > > Might be a good idea for all of us to check for subscription requests. > > > > Lynne > > > > > > Joan Young <jyoung6180@aol.com> wrote: > >> Thank you thank you! I have to admit <blush> I never knew that page was > THERE. It worked...and I see other requests there also but I have no idea > how old they may be ... so for now I'm leaving them alone. > >> > >> > >> Joan Young > >> jyoung6180@aol.com<mailto:jyoung6180@aol.com> > >> > > > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community >
Nivard, Showing my age, perhaps. It was in 1970 that I encountered my first computer, an IBM S/360 mainframe. I complained about something not working correctly, and was admonished: "It's not a bug, it's a feature." Keith On Sat, Dec 15, 2018 at 12:02 PM Nivard Ovington <ovington.one@gmail.com> wrote: > Hi Keith > > No I would disagree, its the only lists archives I have found with the > problem > > It says private if I am not signed in to Rootsweb, but opens as usual if > I am > > And I get the same message of private in other browsers, so its neither > a cookie or plug in or browser for that matter > > As there is no setting for this I suspect its a glitch in the software > > Mailman can be configured in various ways for different uses, but not > all options are for us mere admins ;-) > > Nivard Ovington in Cornwall (UK) > > On 15/12/2018 15:19, Keith Meintjes wrote: > > Lynne, Nivard, > > > > I am running out of fingers to point at likely suspects. And, I still > have > > ten of them. > > > >>From what Nivard says, I would suspect a cookie or a browser plugin. > Either > > way, that is on the user side (which does not at all absolve RW, if that > is > > the way they have decided to do it). Or. simply, lack of support for a > > browser. > > > > I will do the best I can to support the South-Africa list. However, I did > > not expect such a level of IT technical smarts was needed when I signed > up. > > > > I greatly appreciate the store of knowledge that is in the Rootsweb > > archives, and will do everything I can to help preserve it. > > > > Keith > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community > -- +1.248.891.6434 Michigan, USA (Eastern Time)
Hi Keith No I would disagree, its the only lists archives I have found with the problem It says private if I am not signed in to Rootsweb, but opens as usual if I am And I get the same message of private in other browsers, so its neither a cookie or plug in or browser for that matter As there is no setting for this I suspect its a glitch in the software Mailman can be configured in various ways for different uses, but not all options are for us mere admins ;-) Nivard Ovington in Cornwall (UK) On 15/12/2018 15:19, Keith Meintjes wrote: > Lynne, Nivard, > > I am running out of fingers to point at likely suspects. And, I still have > ten of them. > >>From what Nivard says, I would suspect a cookie or a browser plugin. Either > way, that is on the user side (which does not at all absolve RW, if that is > the way they have decided to do it). Or. simply, lack of support for a > browser. > > I will do the best I can to support the South-Africa list. However, I did > not expect such a level of IT technical smarts was needed when I signed up. > > I greatly appreciate the store of knowledge that is in the Rootsweb > archives, and will do everything I can to help preserve it. > > Keith
Lynne, Nivard, I am running out of fingers to point at likely suspects. And, I still have ten of them. From what Nivard says, I would suspect a cookie or a browser plugin. Either way, that is on the user side (which does not at all absolve RW, if that is the way they have decided to do it). Or. simply, lack of support for a browser. I will do the best I can to support the South-Africa list. However, I did not expect such a level of IT technical smarts was needed when I signed up. I greatly appreciate the store of knowledge that is in the Rootsweb archives, and will do everything I can to help preserve it. Keith On Sat, Dec 15, 2018 at 10:07 AM Lynne <lklein@mindspring.com> wrote: > Good idea to test all of our list's archives, Nivard. Just tested > LancsGen, which seems to work okay. Search All Lists appears to work okay, > but how would we know? > > The Eng-Surrey list admin thought that her list's archives were made > private as part of the "new and improved" RootsWeb. There may be other > admins out there that think the same thing. Judging by participation on > this list, there seem to be few admins that are subscribed to it so many > admins might not have a clue about some of the problems we've been > experiencing. > > Lynne > > > > Nivard Ovington <ovington.one@gmail.com> wrote: > > > >Thats an odd one isn't it > > > >I tried with my usual browser which I use for Rootsweb, and as I am a > >subscriber to Eng-Surrey it let me view the archives > > > >Tried a different browser and got the message you reported > > > >So in that browser I tried another two lists, one I am not subscribed to > >and both let me view the archives, so it appears to be just Eng-Surrey > > > >Unless others I haven't tried are also "private" > > > >Nivard Ovington in Cornwall (UK) > > > > > _______________________________________________ > Email preferences: http://bit.ly/rootswebpref > Unsubscribe > https://lists.rootsweb.com/postorius/lists/listowners@rootsweb.com > Privacy Statement: https://ancstry.me/2JWBOdY Terms and Conditions: > https://ancstry.me/2HDBym9 > Rootsweb Blog: http://rootsweb.blog > RootsWeb is funded and supported by Ancestry.com and our loyal RootsWeb > community > -- +1.248.891.6434 Michigan, USA (Eastern Time)
I would say you are probably right there that a lot of admins aren't on this list and are unaware of the changes and effects Baffles me why some are admins at all to be honest Nivard Ovington in Cornwall (UK) On 15/12/2018 15:07, Lynne wrote: > Good idea to test all of our list's archives, Nivard. Just tested LancsGen, which seems to work okay. Search All Lists appears to work okay, but how would we know? > > The Eng-Surrey list admin thought that her list's archives were made private as part of the "new and improved" RootsWeb. There may be other admins out there that think the same thing. Judging by participation on this list, there seem to be few admins that are subscribed to it so many admins might not have a clue about some of the problems we've been experiencing. > > Lynne