Return-Path: <majordom@post.thorcom.com>
Received: (qmail 3100 invoked from network); 8 Apr 2002 10:07:45 -0000
Received: from unknown (HELO murphys-inbound.services.quay.plus.net) (212.159.14.225)  by excalibur.plus.net with SMTP; 8 Apr 2002 10:07:45 -0000
X-Priority: 3
X-MSMail-Priority: Normal
Received: (qmail 9026 invoked from network); 8 Apr 2002 10:07:44 -0000
Received: from unknown (HELO post.thorcom.com) (212.172.148.70)  by murphys.services.quay.plus.net with SMTP; 8 Apr 2002 10:07:44 -0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Received: from majordom by post.thorcom.com with local (Exim 3.33 #2) id 16uXXR-0003yZ-00 for rsgb_lf_group-outgoing@blacksheep.org; Mon, 08 Apr 2002 12:42:21 +0100
Received: from nat1.excitenetwork.com ([63.236.75.3] helo=xmxpita.excite.com) by post.thorcom.com with esmtp (Exim 3.33 #2) id 16uXXP-0003yU-00 for rsgb_lf_group@blacksheep.org; Mon, 08 Apr 2002 12:42:20 +0100
Received: by xmxpita.excite.com (Postfix, from userid 110) id C3C813DDD; Mon,  8 Apr 2002 06:03:42 -0400 (EDT)
To: rsgb_lf_group@blacksheep.org
Subject: Re: LF: Info's...
From: "john sexton" <computernetworks@excite.com>
MIME-Version: 1.0
X-Sender: computernetworks@excite.com
X-Mailer: PHP
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit
Message-ID: <20020408100342.C3C813DDD@xmxpita.excite.com>
Date: Mon,  8 Apr 2002 06:03:42 -0400 (EDT)
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
X-Listname: rsgb_lf_group
Sender: <majordom@post.thorcom.com>

 Hi Wolf,
<br />
Thanks for making the effort to complete a QSO with me on saturday.
<br />
When you returned QRZ I understood that 3 second dots would not work and went to 10 seconds, with success.
<br />
It takes a long time and requires patience, hence I kept the overs as short as possible. Nevertheless I was able to prepare and eat breakfast during the course of the QSO.
<br />
I have been and continue to send QRSS10 CQs in the hope that others will make the effort. Everyone piles in when there is a strong station around like RU6LWZ, but it requires more of an effort and a good receive set-up to winkle out the weak ones.
<br />

<br />
Hi Szigy,
<br />
As reported last week, I have seen your QRSS3 sigs here in England. Very readable but slightly broken so M/O.
<br />
If you are not getting responses it is more down to the poor receivers around than your sigs.
<br />

<br />
73 and good luck John, G4CNN
<br />

<br />

<br />
--- On Sun 04/07,  <DL4YHF@aol.com> wrote:
<br />
> Hello Szigy and group,
<br />
> 
<br />
> Thanks for your info.
<br />
> Have you been transmitting on late saturday evening ? There was a quite
<br />
> weak 
<br />
> trace on the waterfall, but I am not too sure if it was you calling
<br />
> someone 
<br />
> or someone calling you.
<br />
> 
<br />
> The signal from RU6LWZ / RU6LA was clearly visible here in northern DL,
<br />
> but 
<br />
> not as strong as on the previous weekend. Many stations called RU6, as
<br />
> seen 
<br />
> on the cluster spots relayed by Alan. The weaker ones (like myself at
<br />
> DF0WD) 
<br />
> didn't make it through, condx didnt help this time. So looking forward for
<br />
> 
<br />
> more activity from the East ;-) 
<br />
> 
<br />
>  -...-
<br />
> 
<br />
> About non-responded emails: I'm not sure about the AB6QV gateway (tried to
<br />
> 
<br />
> use it some years ago) - is it possible that it rejects email addresses
<br />
> which 
<br />
> don't look like amateur radio calls ?
<br />
> 
<br />
>  -...-
<br />
> 
<br />
> Congrats to all who made it into RU6LWZ's logbook, and thanks to John
<br />
> G4CNN 
<br />
> for your patience to make it into DF0WD's lookbook. There were static
<br />
> crashes 
<br />
> here making the AGC jump, cutting many 'dashes' into 'dots'. 
<br />
> 
<br />
> Regards,
<br />
>  Wolf  DL4YHF.
<br />
> 
<br />
> <p><hr>