Delivered-To: daveyxm@virginmedia.com Received: by 10.50.208.67 with SMTP id mc3csp81670igc; Sun, 11 May 2014 03:39:17 -0700 (PDT) X-Received: by 10.153.6.2 with SMTP id cq2mr8205881lad.0.1399804756074; Sun, 11 May 2014 03:39:16 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id l7si3870132lae.27.2014.05.11.03.39.15 for ; Sun, 11 May 2014 03:39:16 -0700 (PDT) Received-SPF: none (google.com: owner-rsgb_lf_group@blacksheep.org does not designate permitted sender hosts) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: owner-rsgb_lf_group@blacksheep.org does not designate permitted sender hosts) smtp.mail=owner-rsgb_lf_group@blacksheep.org; dkim=pass header.i=@googlemail.com Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1WjR8i-0001pM-TD for rs_out_1@blacksheep.org; Sun, 11 May 2014 11:37:52 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1WjR8i-0001pD-CM for rsgb_lf_group@blacksheep.org; Sun, 11 May 2014 11:37:52 +0100 Received: from mail-ee0-f49.google.com ([74.125.83.49]) by relay1.thorcom.net with esmtps (TLSv1:RC4-SHA:128) (Exim 4.82) (envelope-from <73dk7fc@googlemail.com>) id 1WjR8g-0002kx-JH for rsgb_lf_group@blacksheep.org; Sun, 11 May 2014 11:37:51 +0100 Received: by mail-ee0-f49.google.com with SMTP id e53so3781360eek.36 for ; Sun, 11 May 2014 03:37:49 -0700 (PDT) X-DKIM-Result: Domain=googlemail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=+kS7D7Xnx5TQDtdkVYBMWFI83jM7wZckiP4LtdYMkHY=; b=Rv7xNBgjH8sGLRsl1GD4u7turcGMJN8U4fti0B1byQYvnSY/1YYj2aInjjWyUpZrkI 3HYcS/+jMgRH8rzf5+sV0BbmaAYJSEoSYI2kEkMhezkA4Js2wJJNiipC0stgtVxaJu+g 9kz2qXv88VoZoOFOJvK/u11li+K/CpsCvAfCZwOpIDJQn12lqzpE1L/V9LnXs8n3i2Mf 41lRnybBFTUTMZCBTdh8rI5LCHFfxh4PbKap7hQewKrMC30+z7Dyv8FgPZJIt3zGd+vx k1+JJc/YBCIpUjrhcosIekeyq5Rl2OZZtFCxPfZPljKiJJ1teyIr2Ty07q51GkpssiGC NdYA== X-Received: by 10.14.206.137 with SMTP id l9mr25179530eeo.40.1399804669887; Sun, 11 May 2014 03:37:49 -0700 (PDT) Received: from [129.206.22.206] (pc206.iup.uni-heidelberg.de. [129.206.22.206]) by mx.google.com with ESMTPSA id f3sm24660920eep.40.2014.05.11.03.37.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 11 May 2014 03:37:49 -0700 (PDT) X-Google-Original-From: DK7FC <73dk7fc@gmail.com> Message-ID: <536F52FC.504@gmail.com> Date: Sun, 11 May 2014 12:37:48 +0200 From: DK7FC <73dk7fc@googlemail.com> 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: <536F1A51.3060806@abelian.org> <536F4BBF.7050506@gmail.com> In-Reply-To: X-Spam-Score: -0.7 (/) 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: Hi Markus, Uuuh, chatting with max. 5 characters will become difficult i think :-) As in JT-9, there should be 13 characters, so one can at least write "i have a cat"... :-) Well, what does one need to arrange such a decoder? How is the message displayed? Is it possible to run a detection window, as a text file, like in OPDS? [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [74.125.83.49 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (73dk7fc[at]googlemail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: eeb98d9e5f7535b37e24952fd7f85252 Subject: Re: VLF: Coherent BPSK at 8270 from DF6NM Content-Type: multipart/alternative; boundary="------------050902020304050307010504" 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=FROM_HAS_MIXED_NUMS,HTML_30_40, HTML_MESSAGE 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 This is a multi-part message in MIME format. --------------050902020304050307010504 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Markus, Uuuh, chatting with max. 5 characters will become difficult i think :-) As in JT-9, there should be 13 characters, so one can at least write "i have a cat"... :-) Well, what does one need to arrange such a decoder? How is the message displayed? Is it possible to run a detection window, as a text file, like in OPDS? 73, Stefan Am 11.05.2014 12:30, schrieb Markus Vester: > Stefan, > yes, you guessed right, the message content was indeed "DF6NM" ;-) Let > me cite from a recent direct mail to Paul: > >> I was using a somewhat guessable message, foreseeing a > possible "official first" demonstration. Maybe a truely random > message would have looked even more impressive ;-) Anyhow as this > is formally not "amateur radio" but rather using an unallocated > frequency range, so there's no need for an allocated callsign. Maybe > if you'd set up a transmitter (relatively easy) and I'd learn how to > decode (the hard part), we could start chatting away on VLF ;-) > 73, Markus > > *From:* DK7FC > *Sent:* Sunday, May 11, 2014 12:06 PM > *To:* rsgb_lf_group@blacksheep.org > *Subject:* Re: VLF: Coherent BPSK at 8270 from DF6NM > > Hello Paul, Markus, > > Well done! Interesting stuff. I see you never stop to find some new > things to try :-) Well well, i should think about... > > What was the contest of the message? A complete callsign, DF6NM? > > 73, Stefan > > Am 11.05.2014 08:36, schrieb Paul Nicholson: > ... --------------050902020304050307010504 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Markus,

Uuuh, chatting with max. 5 characters will become difficult i think :-) As in JT-9, there should be 13 characters, so one can at least write "i have a cat"... :-)

Well, what does one need to arrange such a decoder? How is the message displayed? Is it possible to run a detection window, as a text file, like in OPDS?

73, Stefan

Am 11.05.2014 12:30, schrieb Markus Vester:
Stefan,
 
yes, you guessed right, the message content was indeed "DF6NM" ;-) Let me cite from a recent direct mail to Paul:
 
>> I was using a somewhat guessable message, foreseeing a possible "official first" demonstration. Maybe a truely random message would have looked even more impressive ;-) Anyhow as this is formally not "amateur radio" but rather using an unallocated frequency range, so there's no need for an allocated callsign. Maybe if you'd set up a transmitter (relatively easy) and I'd learn how to decode (the hard part), we could start chatting away on VLF ;-)
 
73, Markus
 

From: DK7FC
Sent: Sunday, May 11, 2014 12:06 PM
Subject: Re: VLF: Coherent BPSK at 8270 from DF6NM

Hello Paul, Markus,

Well done! Interesting stuff. I see you never stop to find some new
things to try :-) Well well, i should think about...

What was the contest of the message? A complete callsign, DF6NM?

73, Stefan

Am 11.05.2014 08:36, schrieb Paul Nicholson:
...
--------------050902020304050307010504--