Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dg02.r1000.mx.aol.com (Internet Inbound) with ESMTP id AF92D38000085; Thu, 10 Jan 2013 13:39:37 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TtMW0-0003TO-RU for rs_out_1@blacksheep.org; Thu, 10 Jan 2013 18:06:08 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TtMW0-0003TF-AO for rsgb_lf_group@blacksheep.org; Thu, 10 Jan 2013 18:06:08 +0000 Received: from out1.ip05ir2.opaltelecom.net ([62.24.128.241]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1TtMVy-0006go-Os for rsgb_lf_group@blacksheep.org; Thu, 10 Jan 2013 18:06:07 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtkGAMkB71BcHn8A/2dsb2JhbABEhVCgOwOPaodzFmMQghkUAQEDSywCCAIBBwEIFDkBBBoqHQECAgEBiAyWHp4lkR8DiC2FUY4bijyCdQ X-IronPort-AV: E=Sophos;i="4.84,446,1355097600"; d="scan'208,217";a="405111937" Received: from unknown (HELO xphd97xgq27nyf) ([92.30.127.0]) by out1.ip05ir2.opaltelecom.net with SMTP; 10 Jan 2013 18:05:45 +0000 Message-ID: <007e01cdef5d$1a062620$0501a8c0@xphd97xgq27nyf> From: "mal hamilton" To: "rsgb" Date: Thu, 10 Jan 2013 18:05:40 -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: 4.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: MF At present 5 stns active some DX on QRSS mode, unfortunately in BEACON mode otherwise QSO'S are possible. This frequency seems to have turned into a BEACON BASHER QRSS freq and NO qso mode. Beacons are not really necessary on this band because of the abundance of NDB Beacons for propagation purposes. It seems to be a habit now to BEACON and QSL via Internet on this band instead of engaging in real time QSO;S I have been on this frequency lately using QRSS 5 for DX qso purposes and QSX 7033 but so far no calls in real time. If this frequency is going to be used for BEACONS only it might be better to QSY to either band edge top or bottom out of the way. preferably TOP to avoid QRM to the CW STNS active at the bottom end. [...] Content analysis details: (4.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 1.6 SUBJ_ALL_CAPS Subject is all capitals -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 3.2 AXB_XMAILER_MIMEOLE_OL_024C2 AXB_XMAILER_MIMEOLE_OL_024C2 X-Scan-Signature: 1e15d6d6179985f133b43d42d658878a Subject: LF: BUSY 476.175 Content-Type: multipart/alternative; boundary="----=_NextPart_000_007B_01CDEF5D.199FC330" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.4 required=5.0 tests=HTML_30_40,HTML_MESSAGE, SUBJ_ALL_CAPS 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: 3039ac1d410a50ef0ae91841 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ------=_NextPart_000_007B_01CDEF5D.199FC330 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MF At present 5 stns active some DX on QRSS mode, unfortunately in BEACON = mode otherwise QSO'S are possible. This frequency seems to have turned into a BEACON BASHER QRSS freq and = NO qso mode. Beacons are not really necessary on this band because of the abundance = of NDB Beacons for propagation purposes. It seems to be a habit now to BEACON and QSL via Internet on this band = instead of engaging in real time QSO;S I have been on this frequency lately using QRSS 5 for DX qso purposes = and QSX 7033 but so far no calls in real time. If this frequency is going to be used for BEACONS only it might be = better to QSY to either band edge top or bottom out of the way. preferably TOP to avoid QRM to the CW STNS active at the bottom end. 73 de mal/g3kev ------=_NextPart_000_007B_01CDEF5D.199FC330 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
MF
At present 5 stns active some DX on QRSS=20 mode,  unfortunately in BEACON mode otherwise QSO'S are=20 possible.
This frequency seems to have turned into a = BEACON BASHER=20 QRSS freq and NO qso mode.
Beacons are not really necessary on this band = because of=20 the abundance of NDB Beacons for propagation purposes.
It seems to be a habit now to BEACON and QSL via = Internet=20 on this band instead of engaging in real time QSO;S
I have been on this frequency lately using QRSS = 5 for DX=20 qso purposes and QSX 7033 but so far no calls in real time.
If this frequency is going to be used for = BEACONS only it=20 might be better to QSY to either band edge top or bottom out of the=20 way.
preferably TOP to avoid QRM to the CW STNS = active at the=20 bottom end.
 
73 de mal/g3kev
 
 
 
------=_NextPart_000_007B_01CDEF5D.199FC330--