At 05:38 PM 1/5/2019, Nivard Ovington wrote: >I can only repeat > >I see no need to look at the headers, it should not be necessary and >is certainly outside the remit for being a list admin > >And way outside the vast majority of list owners experience > >So we should not be trying to advise list owners or potential >subscribers with something they don't understand and falls outside >the standard commands as laid out in the subscribe / unsubscribe >found on the lists home page Nivard, https://mailinglists.rootsweb.com/listindexes/details?list_name=listowners says (un)subscribe requests should be send to listowners-(un)subscribe NOT listowners-request. listname-request has not been a valid address for (un)subscribe requests since the lists were brought back on line some 9 months ago. Insofar as listowners learning to read headers, you are correct that it is not required. And I also agree that most listowners don't have to know very much about them -- until or unless they are trying to solve an otherwise inexplicable subscriber problem. OTOH, understanding them on a minimal level makes you a better (more helpful) list admin for your subscribers. As always, investment by list admins comes down to personal choice. Pat Asher P.S. The full, expanded headers for your post (quoted above) to which I am replying, follow below. Not only td they include the sub/unsub instructions I quoted from a previous post, but dkim, dmarc, and spam scores, all of which affect your subscribers ability to post to your list. X-Persona: <eNet> Return-Path: <listowners-bounces@rootsweb.com> X-Original-To: pasher@ee.net Delivered-To: pasher@ee.net Received: from in3f.electric.net (in3f.electric.net [72.35.12.46]) by mail.ee.net (Postfix) with ESMTP id 640326B760 for <pasher@ee.net>; Sat, 5 Jan 2019 17:38:40 -0500 (EST) Received: from 1gfuaV-0008Xl-5E by in3f.electric.net with hostsite:1383212 (Exim 4.90_1) (envelope-from <listowners-bounces@rootsweb.com>) id 1gfuaW-0008dy-41 for pasher@ee.net; Sat, 05 Jan 2019 14:38:40 -0800 Received: by emcmailer; Sat, 05 Jan 2019 14:38:40 -0800 Received-SPF: pass (in3f.electric.net: domain of rootsweb.com designates 35.172.205.187 as permitted sender) client-ip=35.172.205.187; envelope-from=listowners-bounces@rootsweb.com; helo=rwlistsmail.rootsweb.com; Received: from rwlistsmail.rootsweb.com ([35.172.205.187]) by in3f.electric.net with esmtp (Exim 4.90_1) (envelope-from <listowners-bounces@rootsweb.com>) id 1gfuaV-0008Xl-5E for pasher@ee.net; Sat, 05 Jan 2019 14:38:39 -0800 Received: from mmlive.rootsweb.com (localhost [127.0.0.1]) by rwlistsmail.rootsweb.com (Postfix) with ESMTP id 46F25912B5 for <pasher@ee.net>; Sat, 5 Jan 2019 15:38:32 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rootsweb.com; s=rw; t=1546727912; bh=BqdWvEmbs8OXS/35Ytx03B5VyVABFLsBMHMk87wT94M=; h=To:References:From:Date:In-Reply-To:Reply-To:Subject:List-Id: List-Archive:List-Help:List-Post:List-Subscribe:List-Unsubscribe: From; b=L9HvrMLYG2hYBe8HKbdIYb3mSl/h71dtghyd6y8RCE2QQSIEDkX1lCszn00eTQCGl vNqd78DxrM/7Y0XCj06Zi9iHlhEKucLHWSPA4Tfd+0RQq0DxYPdp3R3sB2b8s/ipdV c/Bi+Lx5I+ukRYUVxvw1HSCB8X4kjYB0QBZD1w+U= Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01lp2059.outbound.protection.outlook.com [104.47.34.59]) by rwlistsmail.rootsweb.com (Postfix) with ESMTPS id 41E2B9B358 for <listowners@rootsweb.com>; Sat, 5 Jan 2019 15:38:28 -0700 (MST) Received: from SN6PR16CA0057.namprd16.prod.outlook.com (2603:10b6:805:ca::34) by SN6PR16MB2653.namprd16.prod.outlook.com (2603:10b6:805:d8::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1495.7; Sat, 5 Jan 2019 22:38:26 +0000 Received: from DM3NAM05FT048.eop-nam05.prod.protection.outlook.com (2a01:111:f400:7e51::206) by SN6PR16CA0057.outlook.office365.com (2603:10b6:805:ca::34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1495.7 via Frontend Transport; Sat, 5 Jan 2019 22:38:26 +0000 Authentication-Results: spf=softfail (sender IP is 148.163.143.216) smtp.mailfrom=gmail.com; rootsweb.com; dkim=pass (signature was verified) header.d=gmail.com;rootsweb.com; dmarc=pass action=none header.from=gmail.com;compauth=pass reason=100 Received-SPF: SoftFail (protection.outlook.com: domain of transitioning gmail.com discourages use of 148.163.143.216 as permitted sender) Received: from mx0a-002f8e01.pphosted.com (148.163.143.216) by DM3NAM05FT048.mail.protection.outlook.com (10.152.98.162) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1471.7 via Frontend Transport; Sat, 5 Jan 2019 22:38:26 +0000 Received: from pps.filterd (m0143794.ppops.net [127.0.0.1]) by mx0b-002f8e01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x05MakcF032334 for <listowners@rootsweb.com>; Sat, 5 Jan 2019 15:38:25 -0700 Authentication-Results-Original: ppops.net; spf=pass smtp.mailfrom=ovington.one@gmail.com; dkim=pass header.d=gmail.com header.s=20161025; dmarc=pass header.from=gmail.com Received: from mail-wr1-f47.google.com (mail-wr1-f47.google.com [209.85.221.47]) by mx0b-002f8e01.pphosted.com with ESMTP id 2pttkp1r81-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for <listowners@rootsweb.com>; Sat, 05 Jan 2019 15:38:25 -0700 Received: by mail-wr1-f47.google.com with SMTP id s12so39653774wrt.4 for <listowners@rootsweb.com>; Sat, 05 Jan 2019 14:38:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=oiFp0PeoyqHv9dT6tUpgWFh0pJeVEyIxrlQjSWkvLtw=; b=AMs4BJHLOICXBTN4/x9SwuxTrq32Otmo2xVtdqx1ry2tPtoWkFIJ5y1r+qgcSRNnp4 c+rvzLcoznsGhM82eHCNOFLbaFbbBGXgsl7/i5o8d4a3uddKLMS5I+Ulttd7silSo4ec gq66Sg5MmupGML/DDgfkxUfU2WullNbco7z2wWO1UFWHLGly4pO1DfofMptJFAsc8GZl duN/cQjHR3dzSoTIMcCvdQ0lRGxSxiQ/zrLF1hL89Xcb0QF5N3i0WVv4fvi0U/Dk7vvp qq+M5F2tX0QbXCsz+haP7F+LMV6kmLatL5C2QdFNEf+IDTb68Il6heS8VSGzwrCTOw1M SCWw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=oiFp0PeoyqHv9dT6tUpgWFh0pJeVEyIxrlQjSWkvLtw=; b=jpmcl65eY9PYvGPU7Gp6jxD3Va4HoZMS6By6omxSm7jwYZVFfCaTPmYeD21PJtYh6d 2Vq1Lrp5k8SfoIcQAJQ/NnZBf7WibINPaqgv0hrM/DHMvx7aWrccJN28WIn8mX3RyfM0 8jEXgvj4uMedEJUidCkqGFam3yvZecaKcEtYoipKNSc7zQCjX2IfAMDcVh4YDgn7USzZ egTj1hy038qFkSQ1P9hG/HJLmWG0UEpRRQnGQizzTLU/W45Iaeao0HsuspLRH8ZmFkX/ dGcfNNlB930KbGZwfHYOfav3nj5hJON0dYSHvvLU+vaWnasTqAVjOE9+4mK/D4EIAvOE Fm6g== X-Gm-Message-State: AJcUukfvtK/VuLTxn0CDx76dqmLnH2oRolkJxoH867hqggivnxtk1rjY dbF589dOMs+a8FS2ZjXReaM= X-Google-Smtp-Source: ALg8bN7xuUOV2E1JwTrUjj3VFD+LN/nBJQzfuGhOIod0cqZ6EuJ2eMUzrDu88xybqUvlDJH1KltpNg== X-Received: by 2002:adf:9123:: with SMTP id j32mr50685475wrj.122.1546727903896; Sat, 05 Jan 2019 14:38:23 -0800 (PST) Received: from ?IPv6:::1? ([2a00:23c5:5278:0:504d:2814:77c0:e524]) by smtp.googlemail.com with ESMTPSA id 60sm66695411wrb.81.2019.01.05.14.38.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Jan 2019 14:38:22 -0800 (PST) To: listowners@rootsweb.com References: <1B43B23B86E84D2089EE7C560EECD97C@DESKTOP1DDSC57> <7fc39b92-5108-ff2c-f3cf-11b20870d4d8@gmail.com> <a96c2854-7219-ea7e-43bf-a564aa390c58@gmail.com> <173344b6-b2ea-5e0d-ca39-e51e77ac6336@gmail.com> <63423fbe-6916-5cd3-40df-eb1e20e672db@gmail.com> <2pttkp1qey-1@m0143794.ppops.net> From: Nivard Ovington <ovington.one@gmail.com> Message-ID: <570251d3-8d34-2e86-eef8-3f38167a46f4@gmail.com> Date: Sat, 5 Jan 2019 22:38:21 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <2pttkp1qey-1@m0143794.ppops.net> Content-Language: en-GB X-Antivirus: Avast (VPS 190105-4, 05/01/2019), Outbound message X-Antivirus-Status: Clean X-CLX-Shades: MLX X-CLX-Response: 1TFkXGxMbEQpMehcZHxMRCllNF2dmchEKWUkXGnEaEBp3BhsdG3EfGhAadwY YGgYaEQpZXhdsbHkRCklGF0tESU9ZXlhTdUJFWV5PThEKQ04XRBNue2lnX34bRnVbaUFTSU9JRG V5GmhLeGZYTG5yWUkRClhcFx8EGgQbHx0HHhxLSRtMSBwFGxoEGxsaBB4SBBIcEBseGh8aEQpeW Rd+cF5wEhEKTVwXGBkfEQpMWhdpTU17EQpMRhdvb2trbGtrEQpDWhcYGhMEEh8EGBgbBB4dEQpC XhcbEQpCRhdlRnlnY0hkcnl5eBEKQlwXGxEKXk4XGxEKQksXY1Nja3sTWH4aX14RCkJJF2NTY2t 7E1h+Gl9eEQpCRRdoZVxQZmlzAVByQREKQk4XY1Nja3sTWH4aX14RCkJMF2x6Y3tsZEB8bX0YEQ pCbBdgb2dsEltuf2hcaREKQkAXb0BYQhhdAUlJekMRCkJYF2dOcF55cHleR0t5EQpNXhcbEQpaW BcYEQpwaBdvXkxuGm5JSWJTbRAaEQpwaBdjb2cBAVhtRkRjHhAaEQpwaBdsTBxhH2h+SWN+WxAa EQpwaBdvXkFiGmx4YnxFQRAaEQpwaBdiXkh5R2FdSxNrfhAaEQpwbBdiQE0baGIZSERpThAeEhE KbX4XGxEKWE0XSxEg X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-01-05_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=inbound_notspam policy=inbound score=0 priorityscore=359 malwarescore=0 suspectscore=4 phishscore=0 bulkscore=0 spamscore=0 clxscore=191 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=492 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1901050199 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:SN6PR16MB2653;H:mx0a-002f8e01.pphosted.com;FPR:;SPF:None;LANG:en; X-Microsoft-Exchange-Diagnostics: 1;DM3NAM05FT048;1:6jF61G3FaZDvykaCVNSXdMwHhywH3fI1+V95QHxr4ajU9FGJxQAJsSBNVI5iDYMKfk9ScEWg+y0t8tQmaqv0jjOBH7ylic9rNBul4gSsIMLTbOLjb/3V9hfXB1fA+ZCY X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 2f2432dd-44b2-43fc-f6fe-08d6735e81ec X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:(2390118)(7020095)(4652040)(5600109)(711020)(4605076)(4608076)(4709027)(1401299)(8001031)(1421009)(1402068)(71702078);SRVR:SN6PR16MB2653; X-Microsoft-Exchange-Diagnostics: 1;SN6PR16MB2653;3:142d8PqU4VsveOcyLd+vGfUBEZuQ9/3GXGA804sNDhRpHDW/EcjQHqWJogK0aAXOkmqA96ccnJNuMlV7gboNQq54PWGiJW4tOWANM8XpujwkclyZLjUavRVTy01xHImOvWQqAWkoehudT20yMrtaTX06470JOVoztdWKaBeu0vxtw8uXcONh8QJwqLez3FyMx9xLGkxpBvGzpkjn0JHhMI4qEDju0OQXYe3+qw53xc2S8nLimYdFGfmlXSGWloi+ArYmZfGjcYAQMBOnlOdGcvkpMDp/8lJADAOh6CbS8yrd7pNUJrAF0WpfDI1hx5Ka7UmLkIla65uD4CZr1az21UWLjJyprKAsl70urpMVFoHwVO5omBVSQyU6dz2uivxU;25:fJsjUyomX98+w9vppqnV206hq6JJHOudJNfjs6UdSEEysN6IMKRBLlwzYP+r/qj4f+P0f3WVFA6BMk2RuvComUqGh15Us3D5y5jAjwI0fj88Pvx3YPPccBSlamv99bdxOXxrq8XrUD0E4Tm268CmFC8E44QCF3Y93Y624Ea1qxKo22gLgD/X1PtIZR2UkYnN/QR24HNRdFleCDgzRrYhUeFvgwBV2CKQ/n+P0R34kodZT/CgPXKAIBbTorU3MF2C7DF2s7Kc1+ItwfQCZZnjG7fF0uGiBrbCqew6G8wlku9/W4/1XhXh3Ae4l7J3tOexjCrlGCknRQtPoLYx4YIvvg== X-MS-TrafficTypeDiagnostic: SN6PR16MB2653: X-Microsoft-Exchange-Diagnostics: 1;SN6PR16MB2653;31:zJc08MQXZq+Wlxoi6aeTjBTVWQdJ50iaJqnxJuMNcLbyta49YIMYfsHaw7tQaii7fhtFIu3PRj19urwcgZ+ts+E4OyZnFOznKJnhKEFo5sged2y////jcnFxYGU+P/yeUgCvqiBKUGiFLj8ojjKxTRGVNvIoTvGfarFPwRGaasn5Pl0kg6vuhEKEiaFPxK1uSA6v0SpLvdZkSImKVvcxFA+I/1POWzdpe1YQbXXURSw=;20:lR3dcny0Sz/eowVnaQfjbtsReTkxkTf7Xw3pK+cDpmmYqoXbyTp9y+MoI2+ObtXnKFR9JBaJbmNnodOqDgGhH5XbEQMeV2cH93zavJWQxg58BAFUi6cnE9B7yuL9n/HsMzpJ/nUiouYUF2FgWVMCoxLzHXgqhfj75dnedVww+Pf+wHwBmQpdbK4IJUO5iNa4TAEOyEVPytPvSRlhkp6RKk8aHq+uR4ACDdfx7Vc8Ksy9jxLBhPuzsm8jBGFukuU8rmlchzjiYlLbykDIMqgSh2j7V399EyWPtHnOQxewE1lXwjEWh9lZLapIzql+yxcDraa2xq9GMWlMlMUTtjE3BmRjCX5QJsgNCbFnJq6r1DMw9vPfW73k/m1AQBdLuJeHzxvFLn7bVKlv+ooeaXYdStO7Ebl9DHloy2ayVQ53ic+hHb2LaNnhYHNOx65bEEP9atyl65595zSirltQgnqU5zzZwxOlEagSGCfb++ONo7FEWgGqIsZb1n8RMjas1uI+bWDFUC/VeHmlr0cxNhvHsaw4PpPTpt4KVZKvV/evUUCYtwugW8ctdXCPLpNmHhd7mRAN23E1Ztjvew8X91OhO4OI0Q+7fnKb4aGaabhtyBk= X-Exchange-Antispam-Report-CFA-Test: BCL:0;PCL:0;RULEID:(3230021)(901025)(902075)(908002)(999002)(7045084)(1310107)(8220060)(2401047)(8121501046)(823300264)(823336107)(823350565)(823411253)(9101536074)(10201501046)(3231475)(1430567)(1431068)(1432190)(1459058)(1630084)(1551064)(9311033)(944510241)(944921075)(946801078)(946901078)(947130094)(9300010083)(9301036083)(9300000332)(9301000244)(52103095)(52105112)(52106170)(52411095)(1250107)(1251107)(1252095)(98823107)(52408095)(98809176)(98816176)(52401380)(52601095)(52505095)(52406095)(52305095)(52206115)(88860335)(1102011)(3002001)(93006095)(93005095)(201708071742011)(7699051)(76991095);SRVR:SN6PR16MB2653;BCL:0;PCL:0;RULEID:;SRVR:SN6PR16MB2653; X-Microsoft-Exchange-Diagnostics: 1;SN6PR16MB2653;4:dI9WZTZPwnnbT0ckI+anRlpIOPCLJOwiqHZZgQITTRuPcZjsXm7+3b5aR+7ZERxWRUpeais2dfUJMLZnipfrezUx25QnFuoo9PzqhaJ6uPosJqAImEf24vAfS8HI5n2rYnc0/MgxV4xTZGLTTp8QGuF7eMOs4ai9PNw5vcV9SSS+RSV7y3Jgx8BiXj0SCiJJGT8kykAhmf5zNMRzFjlP7oPvwTU9aHW+5e+/2vFfuh9o1gQpMc0Cb8cSRMqlm6TqAOzzTai9JwXzraMwJQlZEmwJh9nJVpMTWXxSRC54aOI=;23:HU21Y/bay8X76QpTH7NHs/ioOPAZZ4LJOYaTtq3yx6GCBlew75qL60vS8121TXA6wRQ1jClUJSZy/MubgspjunL6N0jqZuBFbuqstXdNUd/BlPRTxslnC4GKq6tqfXXso+VUIl3lBftG2QMKocVw0/Z3ehH5kt+xzD4fXanWbD0= X-Microsoft-Antispam-Message-Info: 2R16AkdF7Vj3oAWaLKK69PpZI5F6BckWkOb6VBxVsrGOhAON9munoZdsZRvapHhd7awkQrnJS+rd+TTKccB9CmuMDtnKffTR4pg5UdSp0FWuJx0u5UnixyDp08tC0FU6yB/joLTe3WArpbvoSr7mwzICgN1Tel1pCnqCohlPXOEclTFnGvMrMrwu4rzIw/7+DjL8ZzciRc/Hc7M5GmqVLuQLkkLnvW42giUdD8ezUeygS+o41MJb60SrR3BeTEppr5SY2hBWNtIUlKJw36HBKFsQiKSClFHuDiZ6xSfSiSKTD6rToIQWkr1um+UsVWUxAfTDYlLFB0tYuKb72s3JWJHJ8tVKcOSLrMTbhkCWnw6FtZyn5Upo787pG0UASJiX133fUaQLyO8Rob0os1u1R85YxLIVR4UPGpV26njL1EMVzPPfKZicRpmzmrS2RmSxKgkgf6aYeTfwqxFx5AxFaefFck7vv+sQwSatndhq+JD5km5PogzKJe/txOFeyvzbkIKkCFFxY7+yZMXH10Vm7sK5SmZX/hUuGxML03nrzwmDhaTsFopNt0+/snhRymh1pbr5hy4OmsL5mPOqREnC0NbSHjp+oUnsV8/eMW5cA4t0jxqMaHjcEvurhHp5Nm7BnVlziXBAsdKW6Bmg7yG/2lsYcM79O7oRXigiX1mSrO3ogusZyTEr6+hwI5Z2eHD0KAegG8wWfugs+5W7sl83bpKe0EpEKOHELDJ+v+5d68hk3WSC+OsRSUmTzdiB5n7oqio5GsFzBoI0l0fOBLBDIvEHoG/+FTkL8CRIAAd9rODQk9OaOHDQhH+KukVDjTevLR/Gp4bHH2KycahShGdSOd1eNvJrDKzt/ioVs+nTUwMIyH6BGmP5t8n14I+kl7XZ2asWMiKhfnC3g7DvKzXkRFcjjZcAZR4uR8IuYkQuPAXYj4KtRprV3xS0QfiPQZ8D X-Microsoft-Exchange-Diagnostics: 1;SN6PR16MB2653;6:t+iI0fOfy0P/ZaodKcxUKSEvyOfYxmfznQB6Z1otT36t+Ue5KZLAnpiXT0CC9XEyjcOzUxuH5h2Xr+tnHca/KfftCu8rzdsKbx26rZDA9xCzvqR1BYPwVgvxrqK0/DT/G1AjkVJcoQ8czSO2dSkNOzJyzmwQqJslYbAYJXl/lvumo3J3jZxmog9GLvwok+b9j6RdNtrW3ftehRAH19bOyJ5w+7PbCGhRqb8XPzhsXJ3W+QNfEeNzm6TmTeLg5MtZaJHN0JNt5gKEsHv6/gYwF0NVhH9AE5i9hzH+jBTcqsTWJDpI2C/Ujevc8j3LUnYQfPpWGen0+Qvgm1IJZ8e4kooZRVuoBC/6GpkTLe7+wujICWYmbK2FASkiOieiFP8McFGlHKs43g69ltgzspgnk0MrNlmf3CUHmuYzACiTFb0aVysRSPTjfp2QVRIf3aHR3meJgKfF779bcz/x+xkfTw==;5:I3kpWCJ7hvubs9/ndibcGYvmj/dL7J4N7BZwHANDI2/mUHie+X4CPcZ0+Uwt9r71iAsFXED+Nu5SCQmfRChzw6m/dvZVip1wzUwCdBgMKcBXTTkZIp1Rd3Uy8w4jj54VITDdtrUjpf7+UEzICWqbcEy8iyx0yfkK8zFlqLUjKhWDnFpTnLcrtuoNb0PXOecn/NoSCRMlycdDKTPY2CnuDA==;7:k0GGQsA79I8QMsjTbGwKuxe/eZ6NAPbAkdgRmjcuWhGMZEDvi+GQ4sgW8Fb5Ys0XyPJz8xsehXtCYSpGJwsqSMe2Wxpm8Lz7ppX+zfLSTwf2Fnqe5nE7PQUj7o9Ve+JakqQ11AMzMjpI4ELXIjWgew== SpamDiagnosticOutput: 1:2 SpamDiagnosticMetadata: 2d759f38b14c4a58b51c255017c5f971 X-OriginatorOrg: ancestryonline.onmicrosoft.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 05 Jan 2019 22:38:26.0758 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 2f2432dd-44b2-43fc-f6fe-08d6735e81ec X-MS-Exchange-CrossTenant-Id: fcf82d21-fd42-46be-a4f5-537daf908555 X-MS-Exchange-CrossTenant-FromEntityHeader: Internet X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR16MB2653 X-MS-Exchange-CrossPremises-OriginalClientIPAddress: 148.163.143.216 X-MS-Exchange-CrossPremises-SCL: -1 X-MS-Exchange-CrossPremises-AuthSource: DM3NAM05FT048.eop-nam05.prod.protection.outlook.com X-MS-Exchange-CrossPremises-AuthAs: Anonymous X-MS-Exchange-CrossPremises-TransportTrafficType: Email X-MS-Exchange-CrossPremises-TransportTrafficSubType: X-MS-Exchange-CrossPremises-Antispam-ScanContext: DIR:Incoming;SFV:SKN;SKIP:0; X-MS-Exchange-CrossPremises-Processed-By-Journaling: Journal Agent X-OrganizationHeadersPreserved: SN6PR16MB2653.namprd16.prod.outlook.com Message-ID-Hash: AWDWVJLZPHM346CDLTBBVG2PGLBVXZX7 X-Message-ID-Hash: AWDWVJLZPHM346CDLTBBVG2PGLBVXZX7 X-MailFrom: ovington.one@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; approved; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; no-subject; suspicious-header X-Mailman-Version: 3.1.0 Precedence: list Reply-To: Listowners list for Rootsweb list admins and moderators <listowners@rootsweb.com> Subject: [LO] Re: Failure to subscribe properly? List-Id: Listowners list for Rootsweb list admins and moderators <listowners.rootsweb.com> Archived-At: <https://Rootsweb.com/hyperkitty/list/listowners@rootsweb.com/thread/AWDWVJLZPHM346CDLTBBVG2PGLBVXZX7/> List-Archive: <https://Rootsweb.com/hyperkitty/list/listowners@rootsweb.com/> List-Help: <mailto:listowners-request@rootsweb.com?subject=help> List-Post: <mailto:listowners@rootsweb.com> List-Subscribe: <mailto:listowners-join@rootsweb.com> List-Unsubscribe: <mailto:listowners-leave@rootsweb.com> Content-Type: text/plain; charset="us-ascii"; format="flowed" Content-Transfer-Encoding: 7bit X-FM-OS: Linux 2.2.x-3.x X-FM-GeoIP: US X-Proto: esmtp X-Revdns: rwlistsmail.rootsweb.com X-HELO: rwlistsmail.rootsweb.com X-TLS: X-Authenticated_ID: X-Origin-IP: 35.172.205.187 X-Env-From: listowners-bounces@rootsweb.com X-DKIM: pass:fail X-Virus-Status: Scanned by VirusSMART (c) X-Virus-Status: Scanned by VirusSMART (s) X-PolicySMART: 10129202 X-SPAM-Status: NO, ALLOW RULE=rootsweb.com:UAD X-Brightmail-Tracker: AAAAATOdRMc= X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrFqMTGxcIABLrsJoYxBt2tshb7DnxncWD0OP7iPVMAYxSHX36JQnBBYm4CR0bP7gtsBQwVIKqBkWEVo1xuablhcUZicUliYlFxUk5pakFRfopuWa4BCBhuYoSavYNx+0WZU4ySUuK8fEaGMUICxUDzMkrzSlKL4otKc1KLXzGKczAqCfM+AcnyZOaVFGemw2QkOJiURHjb+AxihHiBFiGkpBoYQ1rkThbISbDYZ3uyqDzZ7s6x+/aZPeZL41oNK4V6521demrp1/lzPlp8OdJw6/nTiFrzS5PmKF5YrdlbcSxxss1fhsBFZisWxN79c2bzJot/qTzG3yZtd/vvdMPU717e7jXzGS9c8TL3lGl79fbJnHMxDzVfVAl8S/DdKRt8/1Lb42WfhX+dUFJiAfreUIu5qDgRAGefc9tNAQAA

I can only repeat I see no need to look at the headers, it should not be necessary and is certainly outside the remit for being a list admin And way outside the vast majority of list owners experience So we should not be trying to advise list owners or potential subscribers with something they don't understand and falls outside the standard commands as laid out in the subscribe / unsubscribe found on the lists home page Nivard Ovington in Cornwall (UK) On 05/01/2019 22:29, Pat Asher wrote: > Email headers contain a wealth of information that is not always > necessary to know day to day, but can help a lot when there is a > question or problem. > > The Mailman software for RootsWeb in its current configuration will > recognize either listname-join or listname-subscribe as a legitimate > subscription request, assuming the sender has put SUBSCRIBE in the > message subject and body. > > For UNSUBSCRIBES, both listname-leave and listname-unsubscribe are valid. > > Pat Asher

Email headers contain a wealth of information that is not always necessary to know day to day, but can help a lot when there is a question or problem. The Mailman software for RootsWeb in its current configuration will recognize either listname-join or listname-subscribe as a legitimate subscription request, assuming the sender has put SUBSCRIBE in the message subject and body. For UNSUBSCRIBES, both listname-leave and listname-unsubscribe are valid. Pat Asher At 05:14 PM 1/5/2019, Nivard Ovington wrote: >Hi Mary > >I neither expand or even look at the headers > >Neither should we need to > >I would still ask where does the "join" or "leave" come into it? > >Its not a command in anything I can find > >The command is subscribe or unsubscribe

From the full expanded headers of posts made to this (or any other list) Subject: [LO] Re: Failure to subscribe properly? List-Id: Listowners list for Rootsweb list admins and moderators <listowners.rootsweb.com> Archived-At: <https://Rootsweb.com/hyperkitty/list/listowners@rootsweb.com/thread/RGXSPX7OYML4TOO2OWMGN3YFVLOV74LF/> List-Archive: <https://Rootsweb.com/hyperkitty/list/listowners@rootsweb.com/> List-Help: <mailto:listowners-request@rootsweb.com?subject=help> List-Post: <mailto:listowners@rootsweb.com> List-Subscribe: <mailto:listowners-join@rootsweb.com> List-Unsubscribe: <mailto:listowners-leave@rootsweb.com> Both listname-join/leave or listname-(un)subscribe will work. Mails sent to listname-request now get a "help" reply, which does tell them how to sub or unsub, but will not process a sub or unsub request. This has been in effect since the lists came back on line last year. Pat Asher At 02:43 PM 1/5/2019, Nivard Ovington wrote: >Where does "join" come from? > >Not seen that before, if you follow the subscribing link it gives "subscribe" > >As in listname-subscribe@rootsweb.com > >Or listname-unsubscribe@rootsweb.com > >Nivard Ovington in Cornwall (UK) > >On 05/01/2019 19:24, Mary D. Taffet wrote: >>Mary, >>Try sending them the correct address to use for >>subscribing. Where you show -request below, >>change that to -join. So >>LISTNAME-join@rootsweb.com instead of what you provided the first time. >>-- Mary _______________________________________________

Hi Mary I neither expand or even look at the headers Neither should we need to I would still ask where does the "join" or "leave" come into it? Its not a command in anything I can find The command is subscribe or unsubscribe Nivard Ovington in Cornwall (UK) On 05/01/2019 22:09, Mary D. Taffet wrote: > Nivard, > > If you expand the headers of a message to this mailing list, you will > see the following headers: > > List-Subscribe: <mailto:listowners-join@rootsweb.com> > List-Unsubscribe: <mailto:listowners-leave@rootsweb.com> > > I assumed the same structure for any other mailing list. > > -- Mary > > > On 1/5/19 2:43 PM, Nivard Ovington wrote: >> Where does "join" come from? >> >> Not seen that before, if you follow the subscribing link it gives >> "subscribe" >> >> As in listname-subscribe@rootsweb.com >> >> Or listname-unsubscribe@rootsweb.com >> >> Nivard Ovington in Cornwall (UK) >> >> On 05/01/2019 19:24, Mary D. Taffet wrote: >>> Mary, >>> >>> Try sending them the correct address to use for subscribing. Where >>> you show -request below, change that to -join.  So >>> LISTNAME-join@rootsweb.com instead of what you provided the first time. >>> >>> -- Mary

Nivard, If you expand the headers of a message to this mailing list, you will see the following headers: List-Subscribe: <mailto:listowners-join@rootsweb.com> List-Unsubscribe: <mailto:listowners-leave@rootsweb.com> I assumed the same structure for any other mailing list. -- Mary On 1/5/19 2:43 PM, Nivard Ovington wrote: > Where does "join" come from? > > Not seen that before, if you follow the subscribing link it gives > "subscribe" > > As in listname-subscribe@rootsweb.com > > Or listname-unsubscribe@rootsweb.com > > Nivard Ovington in Cornwall (UK) > > On 05/01/2019 19:24, Mary D. Taffet wrote: >> Mary, >> >> Try sending them the correct address to use for subscribing. Where >> you show -request below, change that to -join.  So >> LISTNAME-join@rootsweb.com instead of what you provided the first time. >> >> -- Mary > > _______________________________________________ > 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

Where does "join" come from? Not seen that before, if you follow the subscribing link it gives "subscribe" As in listname-subscribe@rootsweb.com Or listname-unsubscribe@rootsweb.com Nivard Ovington in Cornwall (UK) On 05/01/2019 19:24, Mary D. Taffet wrote: > Mary, > > Try sending them the correct address to use for subscribing. Where you > show -request below, change that to -join.  So > LISTNAME-join@rootsweb.com instead of what you provided the first time. > > -- Mary

Mary, Try sending them the correct address to use for subscribing. Where you show -request below, change that to -join.  So LISTNAME-join@rootsweb.com instead of what you provided the first time. -- Mary On 1/5/19 7:30 AM, Mary Russell wrote: > I have had one gentleman try 3 times with directions ,to subscribe to Dixon list, Each time it has failed. > He has given up. So I have lost a valuable poster to this list. > I have no way to put him on the list. This is sad. > I sent these directions. I guess there is nothing else to do. Sad, Mary R. > > LISTNAME-request@rootsweb.com (replacing LISTNAME with the actual >> name of the list) with the word SUBSCRIBE in the subject and message >> body. They then need to respond to the confirmation email to >> complete the subscription

Hi Lynn Can you say what the problem is you have found with "Find a list" search, as to date I haven't found one The browse is definitely glitched we know that Ah just saw your footer * message Frankly I don't think thats a problem, given that no one would know there was a hyphen, most people these days would search for just dna and see what comes up, they are unlikely to know that a dna-newbie list exists unless someone has told them the list address already I just tried a hyphened address and it came up as does DNA- which bring up 15 matches including DNA-NEWBIE But no one would search with a hyphen anyway unless they knew it was there IMHO If I wanted a dna list I would search for just dna and see what came up (over 200 as it happens) Or if I knew that NEWBIE was in the title I would try that on its own (9 matches including DNA-NEWBIE) So I would still say that "Find a list" search is the best way to advise anyone Nivard Ovington in Cornwall (UK) On 05/01/2019 16:57, Lynne wrote: > Mary, the old way to subscribe to and unsub from lists still works. Just tried it to make sure. Obviously there's something wrong somewhere that's preventing your person from subbing so entering his address into the "Mass Operations" field is the only way to go. If you haven't already, do make sure his email address isn't among your banned addresses. If his address is there anything else you do will be in vain. > > As Nivard said, pointing a subscriber to the list information page is usually a good thing. However, don't bother to ask anyone to search for a list. The list search functionality doesn't always work properly* and, as several LOs have already reported, browsing does not bring up all available lists, either. If Ancestry wants the lists to live long and prosper (which I'm beginning to doubt), fixing the search function of Find A List and making sure all lists are represented when browsing will go a long way to help would-be subscribers find what they're seeking. > > Lynne > > *Try searching for a list name that's hyphenated but leave the hyphen out during the search, such as DNA-Newbie. New subscribers are unlikely to know there should be a hyphen or to search for just DNA and then search the resulting list for Newbie.

Mary, the old way to subscribe to and unsub from lists still works. Just tried it to make sure. Obviously there's something wrong somewhere that's preventing your person from subbing so entering his address into the "Mass Operations" field is the only way to go. If you haven't already, do make sure his email address isn't among your banned addresses. If his address is there anything else you do will be in vain. As Nivard said, pointing a subscriber to the list information page is usually a good thing. However, don't bother to ask anyone to search for a list. The list search functionality doesn't always work properly* and, as several LOs have already reported, browsing does not bring up all available lists, either. If Ancestry wants the lists to live long and prosper (which I'm beginning to doubt), fixing the search function of Find A List and making sure all lists are represented when browsing will go a long way to help would-be subscribers find what they're seeking. Lynne *Try searching for a list name that's hyphenated but leave the hyphen out during the search, such as DNA-Newbie. New subscribers are unlikely to know there should be a hyphen or to search for just DNA and then search the resulting list for Newbie. Nivard Ovington <ovington.one@gmail.com> wrote: > >Hi Mary > >As Mike says you can add a subscriber with no problem > >But you are also giving the *old* subscribe instructions > >I would suggest always sending a potential subscriber to the home page >for your list which has all the correct addresses > >Tell them to start here >https://home.rootsweb.com/ > >Click Mailing lists > >Enter the list name and select from the list presented (there are >sometimes more than one offered) > >Selecting the list name will give the home page >

I don't think many browse the list of lists these days If anyone searches for CRUM they get several other variants, several of which are now marked inactive In the description of your list you might add a few more variants to point those who find it in the right direction But there will always be a problem for those completely new to it all Nivard Ovington in Cornwall (UK) On 05/01/2019 15:45, Jerry M Crumly wrote: > True. But there’s still something not quite right if a new researcher is browsing lists. My name has numerous variations: with and without a ‘b’, an ‘e’, both of those letters together and without, etc. No big deal for a List owner, but not good for a new researcher. > Jerry

True. But there’s still something not quite right if a new researcher is browsing lists. My name has numerous variations: with and without a ‘b’, an ‘e’, both of those letters together and without, etc. No big deal for a List owner, but not good for a new researcher. Jerry On Jan 5, 2019, at 9:34 AM, Nivard Ovington <ovington.one@gmail.com> wrote: > Not if you search for the list name > > I never bother with the A to Z etc > > Your list comes up as the only one for CRUMLEY > > https://mailinglists.rootsweb.com/listindexes/details?list_name=crumley > > Nivard Ovington in Cornwall (UK) > > On 05/01/2019 15:29, Jerry M Crumly wrote: >> Well, at least that’s what’s supposed to happen. I own the Crumley-List. Clicking on the C lists brings up a list of names that stops at Coleman. The other Lists are missing. >> Jerry Crumly > > _______________________________________________ > 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

Not if you search for the list name I never bother with the A to Z etc Your list comes up as the only one for CRUMLEY https://mailinglists.rootsweb.com/listindexes/details?list_name=crumley Nivard Ovington in Cornwall (UK) On 05/01/2019 15:29, Jerry M Crumly wrote: > Well, at least that’s what’s supposed to happen. I own the Crumley-List. Clicking on the C lists brings up a list of names that stops at Coleman. The other Lists are missing. > Jerry Crumly

Well, at least that’s what’s supposed to happen. I own the Crumley-List. Clicking on the C lists brings up a list of names that stops at Coleman. The other Lists are missing. Jerry Crumly On Jan 5, 2019, at 7:06 AM, Nivard Ovington <ovington.one@gmail.com> wrote: > Hi Mary > > As Mike says you can add a subscriber with no problem > > But you are also giving the *old* subscribe instructions > > I would suggest always sending a potential subscriber to the home page for your list which has all the correct addresses > > Tell them to start here > https://home.rootsweb.com/ > > Click Mailing lists > > Enter the list name and select from the list presented (there are sometimes more than one offered) > > Selecting the list name will give the home page > > > > Nivard Ovington in Cornwall (UK)

Not at all Mary But the latest way is really easy, just click the link and it should open a new email all filled in But you can always add them manually if they still have a problem Enter your admin tools Select "Mass Operations" (daft name for it really) Enter the email address and click Subscribe users at the bottom Nivard Ovington in Cornwall (UK) On 05/01/2019 14:53, Mary Russell wrote: > I tried the new and at age 84 got confused over it and don’t think I could subscribe > the new way. Maybe I’ve been here too long ................Mary >

I tried the new and at age 84 got confused over it and don’t think I could subscribe the new way. Maybe I’ve been here too long ................Mary From: Nivard Ovington Sent: Saturday, January 5, 2019 7:06 AM To: listowners@rootsweb.com Subject: [LO] Re: Failure to subscribe properly? Hi Mary As Mike says you can add a subscriber with no problem But you are also giving the *old* subscribe instructions I would suggest always sending a potential subscriber to the home page for your list which has all the correct addresses Tell them to start here https://home.rootsweb.com/ Click Mailing lists Enter the list name and select from the list presented (there are sometimes more than one offered) Selecting the list name will give the home page Nivard Ovington in Cornwall (UK) On 05/01/2019 12:30, Mary Russell wrote: > I have had one gentleman try 3 times with directions ,to subscribe to Dixon list, Each time it has failed. > He has given up. So I have lost a valuable poster to this list. > I have no way to put him on the list. This is sad. > I sent these directions. I guess there is nothing else to do. Sad, Mary R. > > LISTNAME-request@rootsweb.com (replacing LISTNAME with the actual >> name of the list) with the word SUBSCRIBE in the subject and message >> body. They then need to respond to the confirmation email to >> complete the subscription _______________________________________________ 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

Hi Mary As Mike says you can add a subscriber with no problem But you are also giving the *old* subscribe instructions I would suggest always sending a potential subscriber to the home page for your list which has all the correct addresses Tell them to start here https://home.rootsweb.com/ Click Mailing lists Enter the list name and select from the list presented (there are sometimes more than one offered) Selecting the list name will give the home page Nivard Ovington in Cornwall (UK) On 05/01/2019 12:30, Mary Russell wrote: > I have had one gentleman try 3 times with directions ,to subscribe to Dixon list, Each time it has failed. > He has given up. So I have lost a valuable poster to this list. > I have no way to put him on the list. This is sad. > I sent these directions. I guess there is nothing else to do. Sad, Mary R. > > LISTNAME-request@rootsweb.com (replacing LISTNAME with the actual >> name of the list) with the word SUBSCRIBE in the subject and message >> body. They then need to respond to the confirmation email to >> complete the subscription

If you are the admin, you can go here after logging in: https://lists.rootsweb.com/postorius/lists/dixon.rootsweb.com/mass_subscribe/ (this is under 'Mass operations') and place their e-mail in there and hit 'Subscribe users'. They will be instantly subscribed and don't need to confirm the subscription. Mike On 1/5/2019 6:30 AM, Mary Russell wrote: > I have had one gentleman try 3 times with directions ,to subscribe to Dixon list, Each time it has failed. > He has given up. So I have lost a valuable poster to this list. > I have no way to put him on the list. This is sad. > I sent these directions. I guess there is nothing else to do. Sad, Mary R. >

I have had one gentleman try 3 times with directions ,to subscribe to Dixon list, Each time it has failed. He has given up. So I have lost a valuable poster to this list. I have no way to put him on the list. This is sad. I sent these directions. I guess there is nothing else to do. Sad, Mary R. LISTNAME-request@rootsweb.com (replacing LISTNAME with the actual >name of the list) with the word SUBSCRIBE in the subject and message >body. They then need to respond to the confirmation email to >complete the subscription \ --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

was Re: About inactive mailing list on RootsWeb I agree with Joan & Dan . Conklin &, Conkling definitely are another 2 that need to be combined. And any variations of the name that remain in the archives should be merged. Most Conklins today had ancestors named Conkling, Conckin, Konkley, Conkline, Conklyn, Conkelen, Concklyne, etc When lists are combined subject lines with location, etc become more important ------------------------ From: Dan M This is also similar with the Rogers Rodgers and Roger... Plus Tom had a mess of various other Roger type lists. So many lists when the variable could be one list. ------------------------ On Thu, Jan 3, 2019, 7:59 AM Joan Young wrote: <snip> A lot of this issue with never used lists dates back to the time RootsWeb decided (seemed like a good idea at the time) to begin creating lists for surname variants. Other list services were doing it so it seemed like RootsWeb was losing customers because people searching for MAYER who didn't realize that MOYER, MAYER, MEYER, MEIER were all covered under the original MYERS list. Sure, the list description said they were all included in the single list but many people never read the list description. It is actually easier and more productive to include all spelling variants of a surname in a single list.