Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mk04.r1000.mx.aol.com (Internet Inbound) with ESMTP id 0C52B380000A2; Fri, 21 Dec 2012 12:23:23 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Tm6IT-0003M5-3i for rs_out_1@blacksheep.org; Fri, 21 Dec 2012 17:22:09 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Tm6IS-0003Lw-Jk for rsgb_lf_group@blacksheep.org; Fri, 21 Dec 2012 17:22:08 +0000 Received: from relay.uni-heidelberg.de ([129.206.100.212]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1Tm6IQ-0005DP-PI for rsgb_lf_group@blacksheep.org; Fri, 21 Dec 2012 17:22:07 +0000 Received: from freitag.iup.uni-heidelberg.de (freitag.iup.uni-heidelberg.de [129.206.29.204]) by relay.uni-heidelberg.de (8.14.1/8.14.1) with ESMTP id qBLHLjlb017650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 21 Dec 2012 18:21:45 +0100 Received: from [129.206.22.206] (pc206.iup.uni-heidelberg.de [129.206.22.206]) by freitag.iup.uni-heidelberg.de (8.12.11.20060308/8.11.2) with ESMTP id qBLHLjrS015577 for ; Fri, 21 Dec 2012 18:21:45 +0100 Message-ID: <50D49AA4.4010404@iup.uni-heidelberg.de> Date: Fri, 21 Dec 2012 18:21:40 +0100 From: =?UTF-8?B?U3RlZmFuIFNjaMOkZmVy?= 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: <1355416452.510251.21507.26940@saddam1.rambler.ru> <50D0883E.7010306@iup.uni-heidelberg.de> <50D0AD04.6070607@iup.uni-heidelberg.de> <1355929041.681284166@f319.mail.ru> In-Reply-To: <1355929041.681284166@f319.mail.ru> 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: Hello Alex, I've analyzed the files here. I guess that 18z (BTW what is "z"? I only know UTC. Have often heared about z but never really knew what it means) was not the best time for the recording. Didn't you save images to a local folder in 5 minute steps or so? There was nothing on 13.dec. Here is a screenshot from the 14dec analysis: https://dl.dropbox.com/u/19882028/LF/14Dec2.png There is a very faint trace arround 19 o'clock. The timestamp is not correct in this reprocessing. The trace shows a dash and 1/3 of a dot in DFCW. But the traces are not clear enough to proof that it is my signal. Sorry! [...] 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 [129.206.100.212 listed in list.dnswl.org] -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: b45446db24846e84db90eb694609e205 Subject: Re: LF: Re[2]: LF: Re[2]: LF: PAM-PAM! JT/RN3AUS next 2 days! Content-Type: multipart/alternative; boundary="------------090009010903060402010106" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_20_30,HTML_MESSAGE, MANY_EXCLAMATIONS 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 x-aol-global-disposition: G x-aol-sid: 3039ac1d618850d49b0b1d97 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. --------------090009010903060402010106 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by relay.uni-heidelberg.de id qBLHLjlb017650 Hello Alex, I've analyzed the files here. I guess that 18z (BTW what is "z"? I=20 only know UTC. Have often heared about z but never really knew what it=20 means) was not the best time for the recording. Didn't you save images=20 to a local folder in 5 minute steps or so? There was nothing on 13.dec. Here is a screenshot from the 14dec analysis:=20 https://dl.dropbox.com/u/19882028/LF/14Dec2.png There is a very faint=20 trace arround 19 o'clock. The timestamp is not correct in this=20 reprocessing. The trace shows a dash and 1/3 of a dot in DFCW. But the=20 traces are not clear enough to proof that it is my signal. Sorry! 73, Stefan/DK7FC Am 19.12.2012 15:57, schrieb Alex K: > Hello Stefan, LF! > Yes, wav files: > https://dl.dropbox.com/u/33303813/mongolia-13dec2012-18z.wav > https://dl.dropbox.com/u/33303813/mongolia-14dec2012-18z.wav > RX dial is 135000 Hz, files recorded fm 18:00 to 23:59 UTC 13and 14=20 > dec 2012. > Time error about 2 min and freq offset is abt -0.5 Hz. HGA22 is audible. > PSE info about your reprocessing results! > 73 de rn3aus > > =D0=92=D1=82=D0=BE=D1=80=D0=BD=D0=B8=D0=BA, 18 =D0=B4=D0=B5=D0=BA=D0=B0= =D0=B1=D1=80=D1=8F 2012, 18:51 =D0=BE=D1=82 Stefan Sch=C3=A4fer=20 > : > > Alex, > > Looks like i've been a bit distracted. The image i thought is from > your > reprocessing is actually by UA0AET... > The image you have generated is not clear enough to proof that it > is my > signal. Do you still have the wav file so i can take a look at it? > > 73, Stefan/DK7FC > > --------------090009010903060402010106 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by relay.uni-heidelberg.de id qBLHLjlb017650 Hello Alex,

I've analyzed the files here. I guess that 18z=C2=A0=C2=A0=C2=A0 (BTW wha= t is "z"? I only know UTC. Have often heared about z but never really knew what it means) was not the best time for the recording. Didn't you save images to a local folder in 5 minute steps or so?
There was nothing on 13.dec.
Here is a screenshot from the 14dec analysis: https://dl.dropbox.com/u/19882028/LF/14Dec2.png=C2= =A0 There is a very faint trace arround 19 o'clock. The timestamp is not correct in this reprocessing. The trace shows a dash and 1/3 of a dot in DFCW. But the traces are not clear enough to proof that it is my signal.
Sorry!

73, Stefan/DK7FC


Am 19.12.2012 15:57, schrieb Alex K:
= Hello Stefan, LF!
Yes, wav files:
https://dl.dropbox.com/u/33303813/mongolia-13dec2012-18z.wav https://dl.dropbox.com/u/33303813/mongolia-14dec2012-18z.wav RX dial is 135000 Hz, files recorded fm 18:00 to 23:59 UTC 13and 14 dec 2012.
Time error about 2 min and freq offset is abt -0.5 Hz. HGA22 is audible.<= br> PSE info about your reprocessing results!
73 de rn3aus

=D0=92=D1=82=D0=BE=D1=80=D0=BD=D0=B8=D0=BA, 18 =D0=B4=D0=B5=D0=BA=D0=B0=D0= =B1=D1=80=D1=8F 2012, 18:51 =D0=BE=D1=82 Stefan Sch=C3=A4fer <Stefan.Schaefer@iup.uni-heidelberg.de>:
Alex,

Looks like i've been a bit distracted. The image i thought is from your
reprocessing is actually by UA0AET...
The image you have generated is not clear enough to proof that it is my
signal. Do you still have the wav file so i can take a look at it?

73, Stefan/DK7FC

--------------090009010903060402010106--