Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-da06.r1000.mx.aol.com (Internet Inbound) with ESMTP id 6A122380000E8; Wed, 20 Mar 2013 18:31:49 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UIRWY-0006mA-Hp for rs_out_1@blacksheep.org; Wed, 20 Mar 2013 22:30:22 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UIRWY-0006m1-5w for rsgb_lf_group@blacksheep.org; Wed, 20 Mar 2013 22:30:22 +0000 Received: from out1.ip03ir2.opaltelecom.net ([62.24.128.239]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1UIRWW-0003n5-Nn for rsgb_lf_group@blacksheep.org; Wed, 20 Mar 2013 22:30:21 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkADANs3SlFOlmIn/2dsb2JhbAANLwi+H4h3g1dlGBYYAwIBAgFYCAEBty2TRY1bgVGDKgOWYJQM X-IronPort-AV: E=Sophos;i="4.84,880,1355097600"; d="scan'208";a="418151482" Received: from host-78-150-98-39.as13285.net (HELO [127.0.0.1]) ([78.150.98.39]) by out1.ip03ir2.opaltelecom.net with ESMTP; 20 Mar 2013 22:29:59 +0000 Message-ID: <514A3867.6050600@psk31.plus.com> Date: Wed, 20 Mar 2013 22:29:59 +0000 From: g3zjo User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org X-Antivirus: avast! (VPS 130320-1, 20/03/2013), Outbound message X-Antivirus-Status: Clean 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: LF I have not yet received any stations using WSPR-X v0.8 r3058 because it is locked out, yet the new Hashtable contains all the callsigns I have received previously. Is this the beginning of a step too far for WSPR? I see no option for disabling a so called 'deep search' or mention of it being implemented. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- X-Scan-Signature: e4383209d2ccb9552700d53c0b540538 Subject: LF: WSPR-X v0.8 r3058 Hashtable 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-sid: 3039ac1d404e514a38d5358c X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none LF I have not yet received any stations using WSPR-X v0.8 r3058 because it is locked out, yet the new Hashtable contains all the callsigns I have received previously. Is this the beginning of a step too far for WSPR? I see no option for disabling a so called 'deep search' or mention of it being implemented. 73 Eddie G3ZJO