[Dx-qsl] Rcvd: PJ2T and...

Ron Notarius wn3vaw at verizon.net
Thu Apr 7 17:45:16 EDT 2005


Just heard back from DJ4KW. He took a look at his log, realized the problem
("operator error" is how he put it) and will be sending me a card direct.
Nice to know that there are still quite a few gentlemen out there!
73, ron wn3vaw
----- Original Message ----- 
From: "Ron Notarius" <wn3vaw at verizon.net>
To: "DX QSL Reflector" <dx-qsl at mailman.qth.net>
Sent: Thursday, April 07, 2005 4:06 PM
Subject: Re: [Dx-qsl] Rcvd: PJ2T and...
> Thanks to all who've replied so far.
>> Almost universal opinion has been for me to contact DJ4KW via email and
> explain the situation. So I'm going to give that a try, and then see how
to
> proceed.
>> I was a little leery of this... I had a situation a few years ago where I
> worked a Russian Antarctic station on 17, but his manager QSL'd me for 20.
> Turned out that the error was the Russian's, he'd forgotten to indicate
the
> band change in his log (which I could demonstrate thanks to a download of
DX
> Summit spots), and the manager offered to send me a corrected card via the
> buro (unless I could send him another SAE & 2GS!). I'm still waiting for
> that card...
>> Hope this turns out better!
>> 73
>> ----- Original Message ----- 
> From: "Ron Notarius" <wn3vaw at verizon.net>
> To: "DX QSL Reflector" <dx-qsl at mailman.qth.net>
> Sent: Wednesday, April 06, 2005 9:10 PM
> Subject: [Dx-qsl] Rcvd: PJ2T and...
>>> Well, it was an interesting pair of letters waiting for me today.
>> First the good news:
>> PJ2T via N9AG (ARRL DX CW 05), 4 week turn around.
>> Now, the puzzlement:
>> DJ4KW returned my request for a V31YN card as NIL. He even included a log
> extract to prove it.
>> And sure enough, at the time I thought I worked him, he worked someone
else.
> But two minutes before, his log shows WN3VA. This proves three things:
> (a) my clock was off;
> (b) he busted my call;
> (c) he didn't notice the busted call in the log extract he sent with
the
> returned card.
>> So, I'm not sure what to do now. First instinct is to send everything
back
> and point out the busted call in his log, and hope he corrects it (as
WN3VA
> has not, nor has it ever been, issued). OTOH, if he chooses to stick to
the
> letter of the log, I'll be out another 4ドル in stamps, envelopes, and GS's.
> (And I checked my log, I did note that he had trouble copying my call...
or
> at least acknowledging that I have a long and slightly unusual one, which
is
> another story and let's not go there)
>> Thoughts on what to do?
>> 73, ron wn3vaw
>> and now, the 2005 annual telling of the Jack Bogut Memorial Joke...
> They won't be serving beer at PNC Park this year...
> ...because the Pirates lost the opener *sigh*
>>> &quot;Don't it always seem to go that you don't know what you've
got...till
> it's gone.&quot; from Big Yellow Taxi (Joni Mitchell) but also true about
> QSL.NET if more users don't open their wallets and help financially.
Please
> contribute TODAY !!
>>> &quot;Don't it always seem to go that you don't know what you've
got...till it's gone.&quot; from Big Yellow Taxi (Joni Mitchell) but also
true about QSL.NET if more users don't open their wallets and help
financially. Please contribute TODAY !!


More information about the DX-QSL mailing list

AltStyle によって変換されたページ (->オリジナル) /