Delivered-To: daveyxm@virginmedia.com Received: by 10.50.208.67 with SMTP id mc3csp83062igc; Sun, 11 May 2014 04:12:01 -0700 (PDT) X-Received: by 10.152.6.131 with SMTP id b3mr8289913laa.9.1399806721108; Sun, 11 May 2014 04:12:01 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id zv4si3977176lbb.188.2014.05.11.04.12.00 for ; Sun, 11 May 2014 04:12:00 -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=@mx.aol.com; dmarc=pass (p=REJECT dis=NONE) header.from=aol.com Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1WjR1n-0001j2-R6 for rs_out_1@blacksheep.org; Sun, 11 May 2014 11:30:43 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1WjR1n-0001it-8U for rsgb_lf_group@blacksheep.org; Sun, 11 May 2014 11:30:43 +0100 Received: from omr-m08.mx.aol.com ([64.12.222.129]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1WjR1k-0002ij-S8 for rsgb_lf_group@blacksheep.org; Sun, 11 May 2014 11:30:42 +0100 Received: from mtaout-mbd02.mx.aol.com (mtaout-mbd02.mx.aol.com [172.26.252.14]) by omr-m08.mx.aol.com (Outbound Mail Relay) with ESMTP id 6681170000094 for ; Sun, 11 May 2014 06:30:37 -0400 (EDT) Received: from White (95-91-237-52-dynip.superkabel.de [95.91.237.52]) by mtaout-mbd02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id D2FC23800008D for ; Sun, 11 May 2014 06:30:36 -0400 (EDT) Message-ID: From: "Markus Vester" To: References: <536F1A51.3060806@abelian.org> <536F4BBF.7050506@gmail.com> Date: Sun, 11 May 2014 12:30:35 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 x-mimeole: Produced By Microsoft MimeOLE V12.0.1606 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1399804237; bh=twE9tTjyUltClUfGJZZkdYxGmVPdB1Y6CL8AJjboybw=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=AKgZayDFDhj2lICDso1kwsk0lPScYlwWjZgsnQCnxtmYesIHF4iN4K1NzxgXgFOet VasZ4gzyOpOiPOlDrwnrNRucdnu8zzdkzeHQJwLL8ke4612YyeXzLOAOcAKjugJNn8 wuX1w2xBvoehdkUBTPMCNrKUFe/GYiIzKAClVBOA= x-aol-sid: 3039ac1afc0e536f514c1f2b X-AOL-IP: 95.91.237.52 X-Spam-Score: 0.4 (/) 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: 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 ;-) [...] Content analysis details: (0.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [64.12.222.129 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.7 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 1.0 FREEMAIL_REPLY From and body contain different freemails X-Scan-Signature: 5934134de2d93cab1d5fc440b67de82f Subject: Re: VLF: Coherent BPSK at 8270 from DF6NM Content-Type: multipart/alternative; boundary="----=_NextPart_000_0049_01CF6D14.CEE3C1C0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_40_50,HTML_MESSAGE, MISSING_OUTLOOK_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 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0049_01CF6D14.CEE3C1C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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=20 Sent: Sunday, May 11, 2014 12:06 PM To: rsgb_lf_group@blacksheep.org=20 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=20 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: ... ------=_NextPart_000_0049_01CF6D14.CEE3C1C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Stefan,
 
yes, you guessed right, the message = content was=20 indeed "DF6NM" ;-) Let me cite from a recent direct mail to=20 Paul:
 
>> I was using a somewhat = guessable message,=20 foreseeing a possible "official first" demonstration. Maybe a = truely=20 random message would have looked even more impressive ;-) = Anyhow as=20 this is formally not "amateur radio" but rather using an = unallocated=20 frequency range, so there's no need for an=20 allocated callsign. Maybe if you'd set up a transmitter = (relatively=20 easy) and I'd learn how to decode (the hard part), we could start = chatting away=20 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,=20 Markus,

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

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

73, = Stefan

Am=20 11.05.2014 08:36, schrieb Paul Nicholson:
... ------=_NextPart_000_0049_01CF6D14.CEE3C1C0--