Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-de05.r1000.mx.aol.com (Internet Inbound) with ESMTP id 590E1380000A1; Fri, 22 Jun 2012 13:34:26 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Si7jP-00073f-8P for rs_out_1@blacksheep.org; Fri, 22 Jun 2012 18:33:15 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Si7jO-00073W-Rp for rsgb_lf_group@blacksheep.org; Fri, 22 Jun 2012 18:33:14 +0100 Received: from moutng.kundenserver.de ([212.227.126.171]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1Si7jJ-0008TD-BH for rsgb_lf_group@blacksheep.org; Fri, 22 Jun 2012 18:33:13 +0100 Received: from [192.168.2.104] (p4FD17106.dip.t-dialin.net [79.209.113.6]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0Lm8VZ-1S945t1wEz-00ZKnS; Fri, 22 Jun 2012 19:33:08 +0200 Message-ID: <4FE4AC54.3090901@legal-medicine.de> Date: Fri, 22 Jun 2012 19:33:08 +0200 From: pws User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.24) Gecko/20111101 SUSE/3.1.16 Thunderbird/3.1.16 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: In-Reply-To: X-Provags-ID: V02:K0:og37EsEfiMDHsjpzWlE7j58sJc+oWot9KIPUK9GBnsV oI0ZmI68yd6kt7k0d3/7UtUbLX59TFLuD/eek2A40nf2iXsQEc 4JOYf/IZr6VVC0DUOemPylOiIah1bruGw/sXxPfBHwOL2OPbxm ux9NhY0OuxSb9ywH8fx55kWfUVJ9UjQCBTs0J7yBHGpGp821rC f5MabBdN7hKcJsOz8C+Wpsr8UC8ok02le2DduwReyLCzDFJp1u VhKzJA0kJ/6aWgxxvRvr4idYKbBvqyVIoWSTE8VTHuXkytTewi 2Q7HI+s3oFjzC+SRGPykqY8uRnU39kbNFK6pKtnyULA1c+EUYq 8j+z4fp5H+utHOIrTx+w= X-Spam-Score: -0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Roger, You wrote: > Just wondering how people think the current set-up is working? The recent > poll suggested a large majority would be happy with a full migration to > Yahoo, but we seem to now have a very messy split with postings in either > place or both. > ... [...] Content analysis details: (-0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [212.227.126.171 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record X-Scan-Signature: e90dcb17768c7e768f13e0721cc1c0c7 Subject: Re: LF: Blacksheep and Yahoo Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:433689920:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d40cd4fe4aca20e0b X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Roger, You wrote: > Just wondering how people think the current set-up is working? The recent > poll suggested a large majority would be happy with a full migration to > Yahoo, but we seem to now have a very messy split with postings in either > place or both. > ... 1. After those boring incident at the VLF Group at Yahoo! (look for "Schumann Resonance and Venus Transit" there) I propose using Yahoo! for day-to-day postings and Blacksheep for in-depth discussions. 2. If you cannot live without those Yahoo! stuff use an incognito without any call sign or full name. Keep in mind that all postings there are fully open to the world including all kinds of search engines, data mining engines, etc. Ignoring that is naive. Peter, df3lp