Return-Path: <owner-rsgb_lf_group@blacksheep.org>
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 w15GnKGe015358
	for <rlg@klubnl.pl>; Mon, 5 Feb 2018 17:49:21 +0100
Received: from majordom by post.thorcom.com with local (Exim 4.14)
	id 1eijsg-0008Fi-VW
	for rs_out_1@blacksheep.org; Mon, 05 Feb 2018 16:44:35 +0000
Received: from [195.171.43.32] (helo=relay1.thorcom.net)
	by post.thorcom.com with esmtp (Exim 4.14)
	id 1eijsg-0008FZ-41
	for rsgb_lf_group@blacksheep.org; Mon, 05 Feb 2018 16:44:34 +0000
Received: from mail-wr0-x22d.google.com ([2a00:1450:400c:c0c::22d])
	by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
	(Exim 4.89)
	(envelope-from <dead.fets@gmail.com>)
	id 1eijsd-0000yo-4R
	for rsgb_lf_group@blacksheep.org; Mon, 05 Feb 2018 16:44:32 +0000
Received: by mail-wr0-x22d.google.com with SMTP id v15so30296523wrb.8
        for <rsgb_lf_group@blacksheep.org>; Mon, 05 Feb 2018 08:44:30 -0800 (PST)
X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=date:from:message-id:to:cc:subject:in-reply-to:references
         :mime-version:content-transfer-encoding;
        bh=D0gbjR3izJYbrmV5fbK22qDyTPNRQzrI9BMCq3Wusbc=;
        b=SEfLxGCDvJaOUhU3g0SKSBXjzGfbgwZ8dS/CY19+6OuJAU4vkgWffwoc3s2LE2XEa5
         cFFAmTmyLMv4dDwJOWdJhdaVPSJXvtMj6QtmZ5BQAEvzTAEljiAusvsUEAOt2gFRs8Mj
         lay7IuhtAGVRFpLJM90Kk9NORq6xtttSu7NBF8YhWvTzGShkHCqOlLKLcYsUMRgGcrDn
         F2XBvto1SFBNLg4qy1RURLpT3tZTAODj3vQeZdzBbWlw2mMRT+qCnoxn0nZqUOOp4/ok
         tu8Oy2+Tmp0EP1+LKq7vQ52IqndfD5jg3KVxSnOGm3PgvFJP8GYWQkcSQSTA1KgYAbJv
         FqAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:date:from:message-id:to:cc:subject:in-reply-to
         :references:mime-version:content-transfer-encoding;
        bh=D0gbjR3izJYbrmV5fbK22qDyTPNRQzrI9BMCq3Wusbc=;
        b=Wtma/M3zDL9CcQ461Z0xco3cUs64anZAtn8oKyeQ0rnGFER+aIEC0gxON2/kyMh3G3
         tpHFf7BmdYg2ZvqDLNh1xY6PJvvhuoM6a2medziqVvirKoy3ZFLBoJqXkRxC2V8c0UmX
         gbpTwZYQnJl/1VAMkeFQy1e8m6tEAfY6gYocM6fMgQc5KvNH/SZSiO+e/3TvYSoNbfLQ
         NSl3RAqqpbE2VlaLFFz0cPq8yJVurz5vaWKSXyJPI2FKxGJdFsZHrJJFT4HCUUze224O
         gs3MllLAxhVb2D1z/80CDKNs1uoifzP2WUOdNNyaFhB+lr7r6Mr098ZKvdd0I9BZzkFO
         3mOg==
X-Gm-Message-State: AKwxytfuqZzWOViZqxdb0+feLMauPcRZCcIT3NwCmp6c5hm3YZrwBGhp
	evOqdSUZu/jdcCanhnLNt7feXg==
X-Google-Smtp-Source: AH8x2275PrwmvthOrHWUWVyvMDdEn4HYxW3MUkKrkee+meIwtZeiObMZF5h16nzbV1Y+cCetNEjc2w==
X-Received: by 10.223.160.172 with SMTP id m41mr27287803wrm.32.1517849069970;
        Mon, 05 Feb 2018 08:44:29 -0800 (PST)
Received: from OfficeWin7.lan (82-70-254-222.dsl.in-addr.zen.co.uk. [82.70.254.222])
        by smtp.gmail.com with ESMTPSA id 42sm15988163wrw.15.2018.02.05.08.44.29
        (version=TLS1 cipher=AES128-SHA bits=128/128);
        Mon, 05 Feb 2018 08:44:29 -0800 (PST)
Date: Mon, 5 Feb 2018 16:44:28 +0000
From: Chris Wilson <dead.fets@gmail.com>
X-Priority: 3 (Normal)
Message-ID: <797250428.20180205164428@gmail.com>
To: Rik Strobbe <rsgb_lf_group@blacksheep.org>
CC: dead.fets@gmail.com
In-Reply-To: <1517848469797.2746@kuleuven.be>
References: <E1eidmB-0005sH-1z@post.thorcom.com> <473da6a1-0b7d-1af6-5d0c-355b1c7bfe81@n1bug.com> <1E6A4083-58B4-455A-BEA5-64084858FF69@talktalk.net> <edfee178-0424-faf0-7f49-0978943b32db@n1bug.com> <1517845014772.54341@kuleuven.be> <cd7f524e-d953-4f58-cfff-5aba74d902ae@n1bug.com>,<809882652.20180205161611@gmail.com> <1517848469797.2746@kuleuven.be>
MIME-Version: 1.0
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:  Hello Rik, Thanks, but hmmm, when I TX in JT-9 on LF N1BUG
    doesn't have spots uploaded to PSK reporter site, although he receives me
    well. I asked on the WSJT group and they said it wouldn't as no proper QSO
    was completed. [...] 
 Content analysis details:   (1.6 points, 5.0 required)
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
  0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                             (dead.fets[at]gmail.com)
  1.6 SUBJ_ALL_CAPS          Subject is all capitals
  0.0 T_DKIM_INVALID         DKIM-Signature header exists but is not valid
X-Scan-Signature: 5c335215f1b3de26d890ee84d49616ce
Subject: Re: LF: MF/630M BAND
Content-Type: text/plain; charset=us-ascii
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.8 required=5.0 tests=PRIORITY_NO_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



Hello Rik,

Thanks, but hmmm, when I TX in JT-9 on LF N1BUG doesn't have spots
uploaded to PSK reporter site, although he receives me well. I asked
on the WSJT group and they said it wouldn't as no proper QSO was
completed.

Monday, February 5, 2018, 4:34:30 PM, you wrote:

> Hello Chris,

> there is no need to TX to spot on PSKreporter.info.

> To enable PSKreporter spotting (assuming you are using WSJT-X):
> - go to settings (in the file menu or simply press F2)
> - click the tab "reporting"
> - under "Network Services" check "Enable PSK Reporter Spotting"
> - return to the main screen

> 73, Rik  ON7YD - OR7T






-- 
Best regards,
 Chris                            mailto:dead.fets@gmail.com