Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mg03.r1000.mx.aol.com (Internet Inbound) with ESMTP id 5A27B38000067; Sun, 23 Dec 2012 05:55:04 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TmjBT-0003hb-1X for rs_out_1@blacksheep.org; Sun, 23 Dec 2012 10:53:31 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TmjBS-0003hS-6I for rsgb_lf_group@blacksheep.org; Sun, 23 Dec 2012 10:53:30 +0000 Received: from smtpout1.wanadoo.co.uk ([80.12.242.29] helo=smtpout.wanadoo.co.uk) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1TmjBP-0004E5-RF for rsgb_lf_group@blacksheep.org; Sun, 23 Dec 2012 10:53:29 +0000 Received: from AGB ([2.26.46.2]) by mwinf5d07 with ME id eyt31k00G02pKvm03yt3zW; Sun, 23 Dec 2012 11:53:06 +0100 Message-ID: From: "Graham" To: References: <1D00CE16DCF340D7BE56065B76EF1A5F@AGB> <50D65418.2040808@freenet.de> In-Reply-To: <50D65418.2040808@freenet.de> Date: Sun, 23 Dec 2012 10:53:03 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Spam-Score: 0.3 (/) 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: Ok Wolf, Ah , so when is a beacon not a beacon .?.. when its a slow cw qso ! I only looked for short time and copied the call two times [...] Content analysis details: (0.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.12.242.29 listed in list.dnswl.org] 0.0 HTML_MESSAGE BODY: HTML included in message 0.3 URIBL_RHS_DOB Contains an URI of a new domain (Day Old Bread) [URIs: blacksheep.org] X-Scan-Signature: 9bd342c7d74bc0c7d15d59c1164ca995 Subject: Re: LF: DF0WD 472 cw beacon ? Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01CDE0FB.AE824B00" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_40_50,HTML_MESSAGE, 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 x-aol-global-disposition: G x-aol-sid: 3039ac1d60cb50d6e3085367 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_0028_01CDE0FB.AE824B00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ok Wolf,=20 Ah , so when is a beacon not a beacon .?.. when its a slow cw = qso !=20 I only looked for short time and copied the call two times =20 Jan had qsb on my signal , but he was ok with me , only 1 or 2 = s points , but 500 seems to have a distinct time X distance = window at these ranges , where signal's peak and fall away=20 73 -G.. From: wolf_dl4yhf=20 Sent: Sunday, December 23, 2012 12:45 AM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: DF0WD 472 cw beacon ? No beacon, one of the very last modes I'd ever use on MF. Actually I had heard you (G0NBD) with a strong solid signal earlier with = PA3ABK. Had switched to 'really slow cw' (but not QRSS) to work 9H1ES, and = thought there may be even more "dx". There wasn't . 73, Wolf DL4YHF / DF0WD . Am 23.12.2012 01:10, schrieb Graham: Ok, no cq when I received df0wd , slow cw , beacon may be , = just called 502/472 2400z no reply , good signal from bia ? = wherever that is ! 73 -G.. =20 From: Markus Vester=20 Sent: Saturday, December 22, 2012 11:34 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: DF0WD 472 cw beacon ? Now at 23:32 Wolf has been calling CQ. a while ago he had mentioned = that he was listening 501 to 503 kHz as well. 73, Markus From: Graham=20 Sent: Saturday, December 22, 2012 11:55 PM To: rsgb_lf_group@blacksheep.org=20 Subject: LF: DF0WD 472 cw beacon ? Is DF0WD a 5 wpm CW beacon ? round 472k ? Graham G0NBD ------=_NextPart_000_0028_01CDE0FB.AE824B00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Ok Wolf,
 
Ah , so  when is a  beacon not  a  beacon = .?.. =20 when its a  slow  cw  qso  !
 
I only looked  for short time  and  copied the  = call   two  times 
 
Jan had  qsb on my  signal  , but  he was  = ok  with  me , only   1  or 2   s = points ,=20 but  500  seems to  have a distinct   = time =20 X  distance  window at these  ranges , where = signal's =20 peak  and  fall  away
 
73 -G..

Sent: Sunday, December 23, 2012 12:45 AM
To: rsgb_lf_group@blacksheep.org= =20
Subject: Re: LF: DF0WD 472 cw beacon ?

No beacon, one of the very last modes I'd = ever use on=20 MF.

Actually I had heard you (G0NBD) with a strong solid signal = earlier=20 with PA3ABK.

Had switched to 'really slow cw' (but not QRSS) to = work=20 9H1ES, and thought there may be even more "dx". There wasn't=20 .

73,
   Wolf DL4YHF / DF0WD .

Am 23.12.2012 = 01:10,=20 schrieb Graham:
Ok,   no cq  when I received   = df0wd  ,=20 slow  cw  , beacon   may be , just =20 called 502/472   2400z  no  reply , = good  signal=20 from  bia  ? wherever  that  is !
 
73 -G.. 

From: Markus = Vester=20
Sent: Saturday, December 22, 2012 11:34 PM
Subject: Re: LF: DF0WD 472 cw beacon ?

Now at 23:32 Wolf has = been calling CQ. a=20 while ago he had mentioned that he = was listening 501=20 to 503 kHz as well.
 
73, Markus

From: Graham
Sent: Saturday, December 22, 2012 11:55 PM
Subject: LF: DF0WD 472 cw beacon ?

Is  DF0WD  a  5  wpm  CW  beacon=20 ?   round 472k ?
 
Graham
G0NBD

------=_NextPart_000_0028_01CDE0FB.AE824B00--