Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mg04.r1000.mx.aol.com (Internet Inbound) with ESMTP id D97C8380000E5; Thu, 20 Dec 2012 13:30:46 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Tlkry-0006Ok-GK for rs_out_1@blacksheep.org; Thu, 20 Dec 2012 18:29:22 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Tlkry-0006Oa-2y for rsgb_lf_group@blacksheep.org; Thu, 20 Dec 2012 18:29:22 +0000 Received: from out1.ip07ir2.opaltelecom.net ([62.24.128.243]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1Tlkrw-0008Nd-FT for rsgb_lf_group@blacksheep.org; Thu, 20 Dec 2012 18:29:20 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AucRAEdC01BcECPJ/2dsb2JhbABFimiyCwN6F3OCGQUBAQQBCAEBA0kCJgYBAQMFAgEDEQQBAQEJJRQBBAgSBhYIBhMKAQICAQGHcAMJCq96DYlVi2lpQFqDKQOILYVRhjeNDYURgnQ X-IronPort-AV: E=Sophos;i="4.84,324,1355097600"; d="scan'208";a="57245860" Received: from host-92-16-35-201.as13285.net (HELO xphd97xgq27nyf) ([92.16.35.201]) by out1.ip07ir2.opaltelecom.net with SMTP; 20 Dec 2012 18:28:59 +0000 Message-ID: <017901cddedf$dcdc49b0$0501a8c0@xphd97xgq27nyf> From: "mal hamilton" To: References: <010001cddec5$42b69d00$0501a8c0@xphd97xgq27nyf> <50D3373D.7080002@gmail.com> Date: Thu, 20 Dec 2012 18:28:52 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 3.8 (+++) 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: John If they do this will be the SHORTEST NOV EVER. I would be inclined to let it run for the value of a few days. or as it stated this morning START 20th December 2012 mal/g3kev ----- Original Message ----- From: "John Pumford-Green" To: Sent: Thursday, December 20, 2012 4:05 PM Subject: Re: LF: Fw: 5 MHZ NOV RENEWAL [...] Content analysis details: (3.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record 3.8 AXB_XMAILER_MIMEOLE_OL_024C2 AXB_XMAILER_MIMEOLE_OL_024C2 X-Scan-Signature: fc152e7304849b9a177649b85aea9f41 Subject: Re: LF: Fw: 5 MHZ NOV RENEWAL Content-Type: text/plain; charset="iso-8859-1" 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: 3039ac1d60cc50d359567220 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none John If they do this will be the SHORTEST NOV EVER. I would be inclined to let it run for the value of a few days. or as it stated this morning START 20th December 2012 mal/g3kev ----- Original Message ----- From: "John Pumford-Green" To: Sent: Thursday, December 20, 2012 4:05 PM Subject: Re: LF: Fw: 5 MHZ NOV RENEWAL > On 20/12/2012 15:18, mal hamilton wrote: > > MF for info I just renewed my 5 Mhz NOV for additional frequencies > > and it states clearly that the NOV ISSUE IS 1st January 2013 and > > expiry 1st January 2018. This makes it clear that any alterations to > > additional frequencies will not commence until the 1st January 2013. > > whereas the 472 NOV clearly states NOV ISSUE is 20th December 2012 > > until 20th December 2017 it could not be any clearer. > > Hello Mal, LF, > > That's just because you applied for your 5MHz NoV AFTER the RSGB fixed > their NoV issuing machine to change the date to the (correct) one of 1 > Jan 2013. > > Both of my new NoVs, for 5MHz and 472kHz state the same : 20 December > 2012, because I applied before they "fixed" their error. > > I imagine people applying for a 473kHz NoV later in the day will find > it's dated January 1 2013 as well. > > You seem to have managed to get one wrongly dated one (the MFpne) and > one correctly dated one (5MHz). > > The question now is, will they send out correctly dated ones to all > those people whove been given incorrect notices? > > John > GM4SLV >