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 w2NDGF6h007930 for ; Fri, 23 Mar 2018 14:16:16 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ezMKr-0000KM-3E for rs_out_1@blacksheep.org; Fri, 23 Mar 2018 13:02:21 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1ezMJq-0000K2-OG for rsgb_lf_group@blacksheep.org; Fri, 23 Mar 2018 13:01:18 +0000 Received: from mout01.posteo.de ([185.67.36.65]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1ezMJn-0007bt-MM for rsgb_lf_group@blacksheep.org; Fri, 23 Mar 2018 13:01:17 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id B182921491 for ; Fri, 23 Mar 2018 14:01:11 +0100 (CET) X-DKIM-Result: Domain=posteo.de Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1521810072; bh=XHKhndX/VUSvLcdUTOTQi5aRQVhj8yfbYviIZBSEMZE=; h=Date:From:To:Subject:From; b=mhlodMt6y8dlacmmNnAl501WexSbfrUG9aPyGjIhZvYbxxBGi5Q2KldJNIkLgXn97 5su62Ekt7C493ZNaJ59EbH3ecSfvuB14MZ2VbRJKq9CgbbGI8WgJeO+GSqgzN8GCRj lYfCiq8Zlu2RkiwIeONdiJ5WCwhRNGEgri/fGDSK33ECPha4W8JLPH0OcJbnmdVLWu LPwEKmiAhLmZYssteNHfeaep5mQ//Qr7byT0++nFiikTvF+do8ntaieXYQ6p9yZWHf +wbg6ZSwJ45QFszaH0xRv2m6gH+LvEsMUWKb6lBHcMBQwU/+oNEsjp3MOQ0nIf3AYB 1c+KXDAsmq7Kw== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4073ZG694Wz9rxR for ; Fri, 23 Mar 2018 14:01:09 +0100 (CET) Message-ID: <5AB4FA95.9080006@posteo.de> Date: Fri, 23 Mar 2018 14:01:09 +0100 From: DK7FC User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <77fdd1d6-7e60-2f33-8c6e-98f787fe0ca8@n1bug.com> In-Reply-To: <77fdd1d6-7e60-2f33-8c6e-98f787fe0ca8@n1bug.com> X-Spam-Score: 0.0 (/) 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 Paul, Am 23.03.2018 13:38, schrieb N1BUG: > LF / 2200 meter community, > > I am a little afraid to ask this question. I don't want to start a > "war" here. But... > No problem! > What is the feeling in the LF community about a QSO (DFCW or QRSS) > which takes more than a single night to complete? Is this OK or will > it be seen as cheating? > Also no problem. The problem is, you need to find someone on the other side who is motivated to try the wholw night. It is more likely to do it in JT9-10 or so. Or in EbNaut, if there has been a clear definition of the parameters and the start time and repeat sequence. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 33d261536bb1467bb13d5764461d5ec4 Subject: Re: LF: Important question on LF QSOs Content-Type: text/plain; charset=UTF-8; format=flowed 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.0 required=5.0 tests=none 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 Hi Paul, Am 23.03.2018 13:38, schrieb N1BUG: > LF / 2200 meter community, > > I am a little afraid to ask this question. I don't want to start a > "war" here. But... > No problem! > What is the feeling in the LF community about a QSO (DFCW or QRSS) > which takes more than a single night to complete? Is this OK or will > it be seen as cheating? > Also no problem. The problem is, you need to find someone on the other side who is motivated to try the wholw night. It is more likely to do it in JT9-10 or so. Or in EbNaut, if there has been a clear definition of the parameters and the start time and repeat sequence. > I am a very conservative operator but I cannot think of any reason > why a QSO spanning a few nights would not be perfectly OK. To me it > seems that's just taking advantage of available propagation and > (very slow) modes which can get information across. > There is a rule that there must be no information exchanged by the QSO partners on another channel (like this reflector). > I do think that if the operators stop for some nights, the QSO > should reset to the beginning because that is a new attempt. > > I'm trying to find out what the community feels about this. I want > to be a respectable member of this community, not an invading > outlaw. ;-) If a QSO taking a few nights is considered evil, I won't > do it. Now is your chance to educate me. > https://www.youtube.com/watch?v=YR5ApYxkU-U We don't need no education :-) 73, Stefan > 73, > Paul N1BUG > >