<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">I am confused. And it's late. <br>
<br>
Are you saying that connecting via telnet and then sending a dx
command that then echos the formatted spot and this is wrong?
Because, according to versions before I starting messing with
this, this was the behaviour that I see. <br>
<br>
I have checked out the version dated Mon Jun 17 14:42:16 2024
+0100<br>
<br>
And, connected via telnet I see this:<br>
<br>
<font face="monospace">G1TLH de GB7TLH 30-Jan-2025 2157Z dxspider
><br>
dx 7211 g7brn test<br>
DX de G1TLH: 7211.0 G7BRN
test 2158Z<br>
G1TLH de GB7TLH 30-Jan-2025 2158Z dxspider ><br>
</font><br>
and on the version 560 I see this:<br>
<br>
<font face="monospace">G1TLH de GB7TLH 30-Jan-2025 2203Z dxspider
><br>
dx 7120 g1tlh test<br>
DX de G1TLH: 7120.0 G1TLH
test 2203Z<br>
</font><br>
<br>
I have just sent these spots from a telnet session for G1TLH and
G7BRN and they all appeared on my console:<br>
<br>
<font face="monospace">DX de G7BRN: 7203.0 G1TLH test
10
IO90 2211Z JO02<br>
DX de G1TLH: 7201.0 G1TLH test
12
IO90 2212Z IO90<br>
DX de G1TLH: 7011.0 G1TLH test
13
IO90 2221Z IO90<br>
</font><br>
It's late, I cannot count.<br>
<br>
You should be able to see these (+ a couple of others) with a
'sh/dx 5 call g1tlh or call g7brn ' as I can on several nodes not
directly connected to me.<br>
<br>
Dirk G1TLH<br>
<br>
<br>
On 30/01/2025 19:55, Keith, G6NHU wrote:<br>
</div>
<blockquote type="cite"
cite="mid:2291df11-5403-45d3-a135-f8f1b3ee04c6@Spark">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title></title>
<div name="messageBodySection">
<div dir="auto"><span
style="font-family:Arial;font-size: medium">Updated to
560. Note, all these different nodes I’m checking are node
partners.</span><span style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: 16px">Logged
on to my cluster via telnet as G0PKT and sent a self spot.</span><span
style="font-size: 16px"><br>
</span><span style="font-size: 16px"><br>
</span><strong style="font-family:Arial">dx 7074 g0pkt test,
please ignore</strong><br>
<strong style="font-family:Arial"> DX de G0PKT: 7074.0 G0PKT
test, please ignore JO01 1919Z JO01</strong><br>
<strong style="font-family:Arial"> G0PKT de G6NHU-2
30-Jan-2025 1919Z dxspider ></strong><span
style="font-size: 16px"><br>
</span><span style="font-size: 16px"><br>
</span><span style="font-family:Arial;font-size: 16px">As you
can see, it was echoed straight back to me.</span><span
style="font-size: 16px"><br>
</span><span style="font-size: 16px"><br>
</span><span style="font-family:Arial;font-size: 16px">I then
switched to my console window</span><span
style="font-size: 16px"><br>
</span><span style="font-size: 16px"><br>
</span><strong style="font-family:Arial">sh/dx g0pkt</strong><br>
<strong style="font-family:Arial"> G6NHU de G6NHU-2
30-Jan-2025 1919Z dxspider ></strong><br>
<strong style="font-family:Arial"> 7074.0 G0PKT 21-Jan-2025
1440Z test <G0PKT></strong><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span
style="font-family:SF Compact Display;font-size: medium">So
the spot I sent at 1919z isn’t shown.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span
style="font-family:SF Compact Display;font-size: medium">I
switched back to the telnet session and sent a spot for
G6NHU which was again echoed straight back to me.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><strong style="font-family:Arial">dx 7074 g6nhu test,
please ignore</strong><br>
<strong style="font-family:Arial">DX de G0PKT: 7074.0 G6NHU
test, please ignore JO01 1921Z JO01</strong><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">Going
back to the console window.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><strong style="font-family:Arial">sh/dx g6nhu</strong><br>
<strong style="font-family:Arial">G6NHU de G6NHU-2 30-Jan-2025
1921Z dxspider ></strong><br>
<strong style="font-family:Arial"> 7074.0 G6NHU 30-Jan-2025
1659Z test <G0PKT></strong><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">It’s
not there.</span><span style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">These
are the two spots I’ve just submitted.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><strong style="font-family:Arial">DX de G0PKT: 7074.0
G0PKT test, please ignore JO01 1919Z JO01</strong><br>
<strong style="font-family:Arial">DX de G0PKT: 7074.0 G6NHU
test, please ignore JO01 1921Z JO01</strong><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">I can
see that MX0NCA-2 has also updated to build 560.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><strong style="font-family:Arial">rcmd MX0NCA-2 sh/dx
g0pkt</strong><br>
<strong style="font-family:Arial">RCMD 'sh/dx g0pkt' sent to
MX0NCA-2</strong><br>
<strong style="font-family:Arial"><a class="moz-txt-link-freetext" href="MX0NCA-2:sh/dx">MX0NCA-2:sh/dx</a>: 'g0pkt' not
found</strong><br>
<br>
<strong style="font-family:Arial">rcmd MX0NCA-2 sh/dx g6nhu</strong><br>
<strong style="font-family:Arial">RCMD 'sh/dx g6nhu' sent to
MX0NCA-2</strong><br>
<strong style="font-family:Arial"><a class="moz-txt-link-freetext" href="MX0NCA-2:sh/dx">MX0NCA-2:sh/dx</a>: 'g6nhu' not
found</strong><span style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">G1FEF-2
is running build 559, both spots are there.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><strong style="font-family:Arial">rcmd G1FEF-2 sh/dx
g6nhu</strong><br>
<strong style="font-family:Arial">RCMD 'sh/dx g6nhu' sent to
G1FEF-2</strong><br>
<strong style="font-family:Arial">G1FEF-2: 7074.0 G6NHU
30-Jan-2025 1921Z test, please ignore
<G0PKT></strong><br>
<br>
<strong style="font-family:Arial">rcmd G1FEF-2 sh/dx g0pkt</strong><br>
<strong style="font-family:Arial">RCMD 'sh/dx g0pkt' sent to
G1FEF-2</strong><br>
<strong style="font-family:Arial">G1FEF-2: 7074.0 G0PKT
30-Jan-2025 1919Z test, please ignore
<G0PKT></strong><span style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">W9AEK
is using build 499, both spots are there.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><strong style="font-family:Arial">rcmd W9AEK sh/dx
g6nhu</strong><br>
<strong style="font-family:Arial">RCMD 'sh/dx g6nhu' sent to
W9AEK</strong><br>
<strong style="font-family:Arial">W9AEK: 7074.0 G6NHU
30-Jan-2025 1921Z test, please ignore
<G0PKT></strong><br>
<br>
<strong style="font-family:Arial">rcmd W9AEK sh/dx g0pkt</strong><br>
<strong style="font-family:Arial">RCMD 'sh/dx g0pkt' sent to
W9AEK</strong><br>
<strong style="font-family:Arial">W9AEK: 7074.0 G0PKT
30-Jan-2025 1919Z test, please ignore
<G0PKT></strong><span style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">R5ACQ-1
has also updated to build 560, both spots are there.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><strong style="font-family:Arial">rcmd R5ACQ-1 sh/dx
g6nhu</strong><br>
<strong style="font-family:Arial">RCMD 'sh/dx g6nhu' sent to
R5ACQ-1</strong><br>
<strong style="font-family:Arial">R5ACQ-1: 7074.0 G6NHU
30-Jan-2025 1921Z test, please ignore
<G0PKT></strong><br>
<br>
<strong style="font-family:Arial">rcmd R5ACQ-1 sh/dx g0pkt</strong><br>
<strong style="font-family:Arial">RCMD 'sh/dx g0pkt' sent to
R5ACQ-1</strong><br>
<strong style="font-family:Arial">G6NHU de G6NHU-2 30-Jan-2025
1937Z dxspider ></strong><br>
<strong style="font-family:Arial">R5ACQ-1: 7074.0 G0PKT
30-Jan-2025 1919Z test, please ignore
<G0PKT></strong><span style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">I
don’t know why they’re not showing on MX0NCA-2 or my own
node but they seem to be appearing on others.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">So
I’ve logged on to F1FCA-2 who is running build 560 as G0PKT
and sent a spot. </span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">As
you can see, it was echoed back.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><strong style="font-family:Arial">G0PKT de F1FCA-2
30-Jan-2025 1944Z dxspider ></strong><br>
<strong style="font-family:Arial">dx g6nhu 7074 Testing,
ignore me.</strong><br>
<strong style="font-family:Arial">DX de G0PKT:
7074.0 G6NHU Testing, ignore me. 1944Z</strong><span
style="font-size: 16px"><br>
</span><span style="font-size: 16px"><br>
</span><span style="font-size: 16px">But if I immediately
check, it’s not there, although my spot from earlier was.</span><span
style="font-size: 16px"><br>
</span><span style="font-size: 16px"><br>
</span><strong style="font-family:Arial">sh/dx g6nhu</strong><br>
<strong style="font-family:Arial">G0PKT de F1FCA-2 30-Jan-2025
1945Z dxspider ></strong><br>
<strong style="font-family:Arial"> 7074.0 G6NHU
30-Jan-2025 1921Z test, please ignore
<G0PKT></strong><span style="font-size: 16px"><br>
</span><span style="font-size: 16px"><br>
</span><span style="font-size: 16px">When I check my own node
via the console, the spot I posted from F1FCA-2 is there.</span><span
style="font-size: 16px"><br>
</span><span style="font-size: 16px"><br>
</span><strong style="font-family:Arial">sh/dx g6nhu</strong><br>
<strong style="font-family:Arial">G6NHU de G6NHU-2 30-Jan-2025
1946Z dxspider ></strong><br>
<strong style="font-family:Arial"> 7074.0 G6NHU
30-Jan-2025 1944Z Testing, ignore me.
<G0PKT></strong><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">Hopefully
all this is coming through OK and that the mailing list
doesn’t strip out the bold text as it should make it easier
to read.</span><span style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">It
looks to me as though spots are being accepted and passed on
but still not being displayed or saved locally. MX0NCA-2 is
doing something very odd by not showing any of them but the
rest are all behaving the same. The text with F1FCA-2 shows
the same symptoms as when I submit spots locally, they’re
passed on but not saved locally.</span><span
style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span><span style="font-family:Arial;font-size: medium">73
Keith G6NHU</span><span style="font-size: medium"><br>
</span><span style="font-size: medium"><br>
</span></div>
</div>
<div name="messageReplySection">On 30 Jan 2025 at 18:00 +0000,
Dirk Koopman via Dxspider-support
<a class="moz-txt-link-rfc2396E" href="mailto:dxspider-support@tobit.co.uk"><dxspider-support@tobit.co.uk></a>, wrote:<br>
<blockquote type="cite"
style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;">
<p>I have uploaded a new version of the code. Please update
and try again.</p>
<p>Dirk</p>
<p id="reply-intro">On 2025-01-30 17:07, Keith, G6NHU via
Dxspider-support wrote:</p>
<blockquote type="cite"
style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div id="replybody1">
<div>
<div>
<div dir="auto">To test this further, I've just logged
onto one of my partner nodes (MX0NCA-2) as
G0PKT. This node is running build 559.<br>
<br>
The spots I've sent today from my node of G0PKT
don't show on his node.<br>
<br>
Now I've submitted a spot on his node<br>
<br>
'dx 7074 g6nhu test'<br>
<br>
Then tried to look for it<br>
<br>
'sh/dx g6nhu'<br>
<br>
sh/dx: 'g6nhu' not found<br>
<br>
When I do the same check on my node, the spot isn't
there.<br>
<br>
When I look on PI4CC who is running build 547, the
spot is there.<br>
<br>
Checking another node running build 559 (R5ACQ-1),
the spot is missing as well.<br>
<br>
These aren't self spots, this is just normal
spotting. I'm convinced something isn't right.<br>
<br>
73 Keith G6NHU <br>
<br>
<br>
</div>
</div>
<div>On 30 Jan 2025 at 14:58 +0000, Keith, G6NHU via
Dxspider-support <a class="moz-txt-link-rfc2396E" href="mailto:dxspider-support@tobit.co.uk"><dxspider-support@tobit.co.uk></a>,
wrote:<br>
<blockquote
style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px; padding-left: 10px;">
<div>
<div dir="auto">I already have that variable set,
I've had it configured that way since March
2023!<br>
<br>
If you notice, some of those spots aren't self
spots. Some were (G0PKT spotting itself) but
others that don't appear locally were G6NHU
spotting G0PKT.<br>
<br>
There are no instances of 'swore' in the debug
log and no instances of 'trying to self spot'
either.<br>
<br>
73 Keith G6NHU <br>
<br>
</div>
</div>
<div>On 30 Jan 2025 at 14:25 +0000, Dirk Koopman via
Dxspider-support
<a class="moz-txt-link-rfc2396E" href="mailto:dxspider-support@tobit.co.uk"><dxspider-support@tobit.co.uk></a>, wrote:<br>
<blockquote
style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px; padding-left: 10px;">
<div class="v1moz-cite-prefix">Which means that
you are probably getting a message like this
in the debug:<br>
<br>
<span style="font-family: monospace;">(DXCommand)
G1TLH-2 swore: 7050 g1tlh (with <a
class="v1moz-txt-link-freetext moz-txt-link-freetext" href="words:G1TLH"
target="_blank" rel="noopener noreferrer"
moz-do-not-send="true">words:G1TLH</a>)<br>
(*) spotter G1TLH/G1TLH<br>
(DXCommand) G1TLH/G1TLH trying to self spot
below 1240000KHz (7050 g1tlh) from
82.68.205.1, not passed on to cluster<br>
</span><br>
I treat self spotting as "swearing" so it
dumps you off after three (configurable)
attempts.<br>
<br>
My memory is not what it was, but I am still
detecting a silent majority of sysops not
liking self-spotting.<br>
<br>
As it's getting near to contest time, I am
holding off any more updates that alter the
main code so you will have to set $<a
class="v1moz-txt-link-freetext"
href="Spot::minselfspotqrg" target="_blank"
rel="noopener noreferrer"
moz-do-not-send="true">Spot::minselfspotqrg</a>
= <strong>0</strong> if that's what you want
to allow on your node. This only affects <u>locally</u>
connected users, not any incoming spots.<br>
<br>
Dirk G1TLH<br>
<br>
On 30/01/2025 13:33, Keith, G6NHU via
Dxspider-support wrote:</div>
<blockquote type="cite"
style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div>
<div dir="auto">Considering this is where
this all started from with the discussion
about self spotting, I noticed this.<br>
<br>
sh/var $<a class="v1moz-txt-link-freetext"
href="Spot::minselfspotqrg"
target="_blank"
rel="noopener noreferrer"
moz-do-not-send="true">Spot::minselfspotqrg</a><br>
$<a class="v1moz-txt-link-freetext"
href="Spot::minselfspotqrg"
target="_blank"
rel="noopener noreferrer"
moz-do-not-send="true">Spot::minselfspotqrg</a>
= <strong>1240000</strong><br>
<br>
Shouldn't the default be 0 now as per
this: <a
class="v1moz-txt-link-freetext moz-txt-link-freetext"
href="https://mailman.tobit.co.uk/pipermail/dxspider-support/2023-March/018036.html"
target="_blank"
rel="noopener noreferrer"
moz-do-not-send="true">https://mailman.tobit.co.uk/pipermail/dxspider-support/2023-March/018036.html</a> ?<br>
<br>
73 Keith G6NHU.</div>
</div>
<div>On 30 Jan 2025 at 13:17 +0000, Keith,
G6NHU via Dxspider-support <a
class="v1moz-txt-link-rfc2396E"
href="mailto:dxspider-support@tobit.co.uk"
rel="noreferrer" moz-do-not-send="true"><dxspider-support@tobit.co.uk></a>,
wrote:<br>
<blockquote
style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px; padding-left: 10px;">
<div>
<div dir="auto">I'm not sure it's quite
right.<br>
<br>
I sent some test self spots from
within a normal telnet session.<br>
<br>
So this is G0PKT self spotting and
also G6NHU sending spots for G0PKT.<br>
<br>
When I do a sh/dx g0pkt, from the
telnet session, this is what I
see. The spot isn't showing.<br>
<br>
<span
style="color: #000000; font-family: Menlo; font-size: 11px;">sh/dx g0pkt</span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; font-family: Menlo; font-size: 11px;">G0PKT de
G6NHU-2 30-Jan-2025 1308Z dxspider
></span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; font-family: Menlo; font-size: 11px;"> 7074.0
G0PKT 21-Jan-2025 1440Z test
<G0PKT></span><span
style="font-size: 11px;"><br>
</span> <span
style="font-size: 11px;"><br>
</span> <span
style="font-size: 11px;"><br>
</span> I see the same if I do the
same command from a console session.<br>
<br>
However, if I do an rcmd to one of my
partners, the test spots I made from
both G0PKT and from G6NHU show.<br>
<br>
<span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">rcmd
pi4cc sh/dx g0pkt</span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">RCMD
'sh/dx g0pkt' sent to PI4CC</span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">G6NHU
de G6NHU-2 30-Jan-2025 1308Z
dxspider ></span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">PI4CC:
7074.0 G0PKT 30-Jan-2025
1245Z test
<G0PKT></span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">PI4CC:
7074.0 G0PKT 30-Jan-2025
1238Z test
<G0PKT></span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">PI4CC:
7074.0 G0PKT 30-Jan-2025
1237Z
<G6NHU></span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">PI4CC:
7074.0 G0PKT 30-Jan-2025
1214Z
<G6NHU></span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">PI4CC:
7074.0 G0PKT 21-Jan-2025
1440Z test
<G0PKT></span><span
style="font-size: 11px;"><br>
</span> <span
style="font-size: 11px;"><br>
</span> <span
style="font-size: 11px;"><br>
</span> Here's the same command
locally in the console.<br>
<br>
<span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">sh/dx
g0pkt</span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">G6NHU
de G6NHU-2 30-Jan-2025 1311Z
dxspider ></span><span
style="font-size: 11px;"><br>
</span> <span
style="color: #000000; background-color: #b2b2b2; font-family: Menlo; font-size: 11px;">
7074.0 G0PKT 21-Jan-2025
1440Z test
<G0PKT></span><span
style="font-size: 11px;"><br>
</span> <span
style="font-size: 11px;"><br>
</span> <span
style="font-size: 11px;"><br>
</span> It's as though the spots have
been sent but not shown or stored
locally.<br>
<br>
Can anyone test the same please, post
some spots and then see if they are
shown on the local node as well as
remote ones.<br>
<br>
73 Keith G6NHU (signing posts with my
callsign now as there seem to be about
three Keiths on here!).</div>
</div>
<div>On 30 Jan 2025 at 11:57 +0000, Dirk
Koopman via Dxspider-support <a
class="v1moz-txt-link-rfc2396E"
href="mailto:dxspider-support@tobit.co.uk" rel="noreferrer"
moz-do-not-send="true"><dxspider-support@tobit.co.uk></a>,
wrote:<br>
<blockquote
style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px; padding-left: 10px;">Please
update in the normal way. This was an
error inside the dx command<br>
caused by me changing a naming
convention. As always: more thought
(and<br>
better testing) required...<br>
<br>
You don't need to restart. The fix
will be picked up automatically when<br>
you next enter a dx command.<br>
<br>
Dirk G1TLH<br>
<br>
On 30/01/2025 11:30, Mike G3YPP via
Dxspider-support wrote:<br>
<blockquote type="cite"
style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">How
do we update the (mn) node command
that Kin mentions. My node will not
send spots<br>
<br>
Mike G3YPP<br>
Sent from my iPhone<br>
<br>
<blockquote type="cite"
style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">On
30 Jan 2025, at 10:03, <a
class="v1moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:dxspider-support-request@tobit.co.uk" rel="noreferrer"
moz-do-not-send="true">dxspider-support-request@tobit.co.uk</a>
wrote:<br>
<br>
Re: [Dxspider-support] New version
of Mojo</blockquote>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a
class="v1moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:Dxspider-support@tobit.co.uk" rel="noreferrer"
moz-do-not-send="true">Dxspider-support@tobit.co.uk</a><br>
<a
class="v1moz-txt-link-freetext moz-txt-link-freetext"
href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support"
target="_blank"
rel="noopener noreferrer"
moz-do-not-send="true">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a></blockquote>
<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a
class="v1moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:Dxspider-support@tobit.co.uk" rel="noreferrer"
moz-do-not-send="true">Dxspider-support@tobit.co.uk</a><br>
<a
class="v1moz-txt-link-freetext moz-txt-link-freetext"
href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support"
target="_blank"
rel="noopener noreferrer"
moz-do-not-send="true">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a></blockquote>
</div>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a
class="v1moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:Dxspider-support@tobit.co.uk" rel="noreferrer"
moz-do-not-send="true">Dxspider-support@tobit.co.uk</a><br>
<a
class="v1moz-txt-link-freetext moz-txt-link-freetext"
href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support"
target="_blank"
rel="noopener noreferrer"
moz-do-not-send="true">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a></blockquote>
</div>
<br>
<fieldset class="v1moz-mime-attachment-header"></fieldset>
<pre class="v1moz-quote-pre">_______________________________________________
Dxspider-support mailing list
<a class="v1moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:Dxspider-support@tobit.co.uk"
rel="noreferrer" moz-do-not-send="true">Dxspider-support@tobit.co.uk</a>
<a class="v1moz-txt-link-freetext moz-txt-link-freetext"
href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support"
target="_blank" rel="noopener noreferrer"
moz-do-not-send="true">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a>
</pre>
</blockquote>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a><br>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a></blockquote>
</div>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a><br>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a></blockquote>
</div>
</div>
</div>
<br>
<div class="pre"
style="margin: 0; padding: 0; font-family: monospace">_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@tobit.co.uk"
moz-do-not-send="true" class="moz-txt-link-freetext">Dxspider-support@tobit.co.uk</a><br>
<a
href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support"
target="_blank" rel="noopener noreferrer"
moz-do-not-send="true" class="moz-txt-link-freetext">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a></div>
</blockquote>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:Dxspider-support@tobit.co.uk">Dxspider-support@tobit.co.uk</a><br>
<a class="moz-txt-link-freetext" href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>