From: "KKorn" <kkorn42@aol.com>
To: <rsgb_lf_group@blacksheep.org>
Date: Sat, 19 Jan 2013 14:58:59 +0100
Message-ID: <1C19719CC0644AACBFB47A57B1B2B557@KKneu>
MIME-Version: 1.0
Importance: Normal
In-Reply-To: <CAKvcm2fpe_RhUL0mUb8rMEy7wi1TkZGJSdRK1L6sNDN0dZvuTA@mail.gmail.com>
X-AOL-SCOLL-URL_COUNT: 0  
X-Spam-Score: 1.9 (+)
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:  Dimitris, Mauro, LF/MF I think I know how to handle WSPR (I
    once wrote the German Manual) but for me and several others there seems to
    be an unsolved bug. Either in WSPR-X or in WSPRnet. If you look a bit closer
    into the WSPRnet activity list, there seems to be often a discrepancy between
    stations reporting (database) and those appearing in the list. I also got
    feedback, that WSPR-X works re upload on one band and not on MW, aso. [...]
 Content analysis details:   (1.9 points, 5.0 required)
  pts rule name              description
 ---- ---------------------- --------------------------------------------------
 -0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
                             trust
                             [205.188.105.145 listed in list.dnswl.org]
  0.0 FREEMAIL_FROM          Sender email is commonly abused enduser mail provider
                             (kkorn42[at]aol.com)
  1.6 SUBJ_ALL_CAPS          Subject is all capitals
 -0.0 SPF_PASS               SPF: sender matches SPF record
 -0.0 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain
  0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
                             digit (kkorn42[at]aol.com)
  0.0 T_DKIM_INVALID         DKIM-Signature header exists but is not valid
X-Scan-Signature: e90dcb17768c7e768f13e0721cc1c0c7
Subject: AW: LF: WSPR-15 MF
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com
X-Spam-Level: ***
X-Spam-Status: No, hits=3.0 required=5.0 tests=FORGED_MUA_OUTLOOK,
	FROM_ENDS_IN_NUMS,SUBJ_ALL_CAPS 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-SCOLL-AUTHENTICATION: mtain-dk06.r1000.mx.aol.com ; domain : mx.aol.com DKIM : pass
x-aol-sid: 3039ac1db40a50faaffb627f
X-AOL-IP: 195.171.43.25
X-AOL-SPF: domain : blacksheep.org SPF : none


Dimitris, Mauro, LF/MF

I think I know how to handle WSPR (I once wrote the German Manual) but =
for
me and several others there seems to be an unsolved bug. Either in =
WSPR-X or
in WSPRnet.=20
If you look a bit closer into the WSPRnet activity list, there seems to =
be
often a discrepancy between stations reporting (database) and those
appearing in the list. I also got feedback, that WSPR-X works re upload =
on
one band and not on MW, aso.

Unclear situation.

Anyone out there with better infos?
Decoding works just fine.

Gr=FC=DFe / Greetings
Klaus
DJ6LB