Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w2QIpJOE021162 for ; Mon, 26 Mar 2018 20:51:20 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1f0X9I-0008BA-IG for rs_out_1@blacksheep.org; Mon, 26 Mar 2018 19:47:16 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1f0X9I-0008B1-4w for rsgb_lf_group@blacksheep.org; Mon, 26 Mar 2018 19:47:16 +0100 Received: from omr-a011e.mx.aol.com ([204.29.186.59]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from ) id 1f0X9F-0000UC-EK for rsgb_lf_group@blacksheep.org; Mon, 26 Mar 2018 19:47:14 +0100 Received: from mtaout-aam01.mx.aol.com (mtaout-aam01.mx.aol.com [172.27.19.145]) by omr-a011e.mx.aol.com (Outbound Mail Relay) with ESMTP id 486873800041 for ; Mon, 26 Mar 2018 14:47:11 -0400 (EDT) Received: from MichaelSappPC (MichaelSappPC [96.236.217.188]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mtaout-aam01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPSA id 08A123800008A for ; Mon, 26 Mar 2018 14:47:11 -0400 (EDT) Message-ID: <8194EE67E5F74A189129087781B57F8D@MichaelSappPC> From: "Michael Sapp" To: References: <5AB9374C.12364.F8711DB@mike.dennison.ntlworld.com> In-Reply-To: <5AB9374C.12364.F8711DB@mike.dennison.ntlworld.com> Date: Mon, 26 Mar 2018 14:47:01 -0400 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18197 X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.19705 x-aol-global-disposition: G x-aol-sid: 3039ac1b13915ab9402f0b7c X-AOL-IP: 96.236.217.188 X-Spam-Score: 0.2 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: FB Mike, Thank you for your beaconing efforts as well. If I can figure out how to squeeze another dB or 2 of SNR out of my system, we may get an entire call capture some day.....73, Mike, wa3tts ----- Original Message ----- From: "Mike Dennison" To: ; Sent: Monday, March 26, 2018 2:09 PM Subject: LF: 136k QRSS suspended [...] Content analysis details: (0.2 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.2 STOX_REPLY_TYPE No description available. X-Scan-Signature: e09cca6d8e44a91eadbdfb3e1b8aec09 Subject: LF: Re: 136k QRSS suspended Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original 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.1 required=5.0 tests=MISSING_OUTLOOK_NAME 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 FB Mike, Thank you for your beaconing efforts as well. If I can figure out how to squeeze another dB or 2 of SNR out of my system, we may get an entire call capture some day.....73, Mike, wa3tts ----- Original Message ----- From: "Mike Dennison" To: ; Sent: Monday, March 26, 2018 2:09 PM Subject: LF: 136k QRSS suspended > Thanks to all who reported my 136kHz QRSS60 signals over the last > weekend, especially for the excellent screenshots from N1BUG and > WA3TTS. > > I am returning to my evening Op32 transmissions for a few days, plus > receiving on as many modes as I can. > > I will resume QRSS60 (weather permitting) from Sun 8 Mar. > > Mike, G3XDV > ========== >