Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dc02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 4EB9B3800008A; Thu, 7 Jun 2012 06:48:05 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ScaEn-0000vP-Q3 for rs_out_1@blacksheep.org; Thu, 07 Jun 2012 11:46:45 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1ScaEn-0000vG-AF for rsgb_lf_group@blacksheep.org; Thu, 07 Jun 2012 11:46:45 +0100 Received: from relay.uni-heidelberg.de ([129.206.100.212]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1ScaEl-00011C-9h for rsgb_lf_group@blacksheep.org; Thu, 07 Jun 2012 11:46:44 +0100 Received: from freitag.iup.uni-heidelberg.de (freitag.iup.uni-heidelberg.de [129.206.29.204]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id q57AkeQ6000721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 7 Jun 2012 12:46:41 +0200 Received: from [129.206.22.206] (pc206.iup.uni-heidelberg.de [129.206.22.206]) by freitag.iup.uni-heidelberg.de (8.12.11.20060308/8.11.2) with ESMTP id q57AkeUu025998 for ; Thu, 7 Jun 2012 12:46:40 +0200 Message-ID: <4FD08634.8010402@iup.uni-heidelberg.de> Date: Thu, 07 Jun 2012 12:45:08 +0200 From: =?ISO-8859-1?Q?Stefan_Sch=E4fer?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <00ad01cd424c$0138a690$0401a8c0@xphd97xgq27nyf> <00d301cd4255$b6428ac0$0401a8c0@xphd97xgq27nyf> <636F5742-6949-4616-9CFD-3FCF99B4506A@gmail.com> <00f301cd4263$4ce62880$0401a8c0@xphd97xgq27nyf> <4FCCD78A.6030302@iup.uni-heidelberg.de> In-Reply-To: X-Spam-Score: -0.7 (/) 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: Hi Joe, LF, Yes, we're here of course :-) Unfortunately i still cannot receive on MF. My RX is home made and vy narrow band. But i'm going to have a suitable RX in some time. BTW, what about all the 500 kHz allocations. What happens to them when the new 475 kHz band becomes permitted? Will you have an extended frequency range then or will you have to QSY? And what about the chances of this band? How easy is a TA detection? Would it be possible to have a CW QSO over that 4400 km distance? It would be possible for me to radiate 1 kW ERP on that band, however with a 1W (EIRP of course) limitation, this may become a problem... [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [129.206.100.212 listed in list.dnswl.org] -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Scan-Signature: f62c7cf8eeb8e5a327b71719e9bffff1 Subject: Re: LF: VX9MRC 504.1 kHz 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:374529504:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d40824fd086e404f3 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Hi Joe, LF, Yes, we're here of course :-) Unfortunately i still cannot receive on MF. My RX is home made and vy narrow band. But i'm going to have a suitable RX in some time. BTW, what about all the 500 kHz allocations. What happens to them when the new 475 kHz band becomes permitted? Will you have an extended frequency range then or will you have to QSY? And what about the chances of this band? How easy is a TA detection? Would it be possible to have a CW QSO over that 4400 km distance? It would be possible for me to radiate 1 kW ERP on that band, however with a 1W (EIRP of course) limitation, this may become a problem... 73, Stefan/DK7FC Am 07.06.2012 02:15, schrieb jcraig@mun.ca: > > Hopefully someone will read this on Baa Baa.... > > The beacon is running on a new frequency with a CW ID and > a 10 second carrier. Reports most welcomed. > > 73 > Joe VO1NA > > This electronic communication is governed by the terms and conditions at > http://www.mun.ca/cc/policies/electronic_communications_disclaimer_2012.php >