Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id x15AnAkF008793 for ; Tue, 5 Feb 2019 11:49:12 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gqyBv-0006xS-K3 for rs_out_1@blacksheep.org; Tue, 05 Feb 2019 10:42:59 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gqyBs-0006xJ-RX for rsgb_lf_group@blacksheep.org; Tue, 05 Feb 2019 10:42:56 +0000 Received: from smtp1web.tin.it ([212.216.176.195]) by relay1.thorcom.net with esmtp (Exim 4.91) (envelope-from ) id 1gqyBp-00027s-QT for rsgb_lf_group@blacksheep.org; Tue, 05 Feb 2019 10:42:55 +0000 Received: from feu11 (10.192.64.21) by smtp1web.tin.it (8.6.060.43) id 5AB0B63D07C0D73D for rsgb_lf_group@blacksheep.org; Tue, 5 Feb 2019 11:42:51 +0100 Received: from (93.146.209.118) by webmailtin.pc.tim.it; Tue, 5 Feb 2019 11:42:51 +0100 Message-ID: <168bd40def4.marcocadeddu@tin.it> Date: Tue, 5 Feb 2019 11:42:51 +0100 (CET) From: "marcocadeddu@tin.it" To: Mime-Version: 1.0 X-Originating-IP: 93.146.209.118:51107 X-Spam-Score: 1.6 (+) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Hi Stefan, MF, the grabber resurrects after the winter rest ;-) compliments for good performance.I'm still running 24/24 WSPR beacon on MF since almost 3 months without interruptions (only exception s [...] Content analysis details: (1.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [212.216.176.195 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (marcocadeddu[at]tin.it) 1.6 SUBJ_ALL_CAPS Subject is all capitals 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: fb42d311bf65eb51bbb8124890b4f977 Subject: R: LF: MF WSPR Content-Type: multipart/alternative; boundary="----=_Part_1255_18547744.1549363371769" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.1 required=5.0 tests=HTML_20_30,HTML_MESSAGE, HTML_TAG_EXISTS_TBODY,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 ------=_Part_1255_18547744.1549363371769 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi Stefan, MF, the grabber resurrects after the winter rest ;-) compliments for good performance.I'm still running 24/24 WSPR beacon on MF since almost 3 months without interruptions (only exception sometime the windows 10 strike ;-) ) it is a relative low power beacon that anyway was heard sometime beyond the pond but since about a week I had no reports neither from TF3GZ nor from W or VE station.. last night also the reports from EA8 were missing...It is hard to state if it is due to propagation, environment (my location is close to Alps and I remember troubles both TX and RX on 160m ) or maybe speaking of SNR the noise level is higher than one week ago making my sigs not decodable..Anyway it is fun keep such a beacon in function and see what happens Marco, IK1HSS ----Messaggio originale---- Da: selberdenken@posteo.de Data: 5-feb-2019 9.25 A: Ogg: LF: MF WSPR MF, Since yesterday, there is some sun in Heidelberg and my tree grabber came back. MF reception is possible again (the VLF E field still has a problem). http://www.iup.uni-heidelberg.de/schaefer_vlf/DK7FC_remote_Grabber.html Last night i got my best RX distance on MF ever (i think): Timestamp Call MHz SNR Drift Grid Pwr Reporter RGrid km az 2019-02-05 06:12 WA4SZE 0.475703 -29 0 EM65 0.2 DK7FC/P JN49ik 7470 45 The band still seems to be open for DX. 73, Stefan ------=_Part_1255_18547744.1549363371769 Content-Type: text/html;charset="UTF-8" Content-Transfer-Encoding: 7bit
Hi Stefan, MF,

the grabber resurrects after the winter rest ;-) compliments for good performance.
I'm still running 24/24 WSPR beacon on MF since almost 3 months without interruptions (only exception sometime the windows 10 strike ;-) ) it is a relative low power beacon that anyway was heard sometime beyond the pond but since about a week I had no reports neither from TF3GZ nor from W or VE station.. last night also the reports from EA8 were missing...
It is hard to state if it is due to propagation, environment (my location is close to Alps and I remember troubles both TX and RX on 160m ) or maybe speaking of SNR the noise level is higher than one week ago making my sigs not decodable..
Anyway it is fun keep such a beacon in function and see what happens

Marco, IK1HSS

----Messaggio originale----
Da: selberdenken@posteo.de
Data: 5-feb-2019 9.25
A: <rsgb_lf_group@blacksheep.org>
Ogg: LF: MF WSPR

MF,

Since yesterday, there is some sun in Heidelberg and my tree grabber came back. MF reception is possible again (the VLF E field still has a problem).
http://www.iup.uni-heidelberg.de/schaefer_vlf/DK7FC_remote_Grabber.html

Last night i got my best RX distance on MF ever (i think):

Timestamp Call MHz SNR Drift Grid Pwr Reporter RGrid km az
 2019-02-05 06:12   WA4SZE   0.475703   -29   0   EM65   0.2   DK7FC/P   JN49ik   7470   45 

The band still seems to be open for DX.

73, Stefan


------=_Part_1255_18547744.1549363371769--