[Dx-qsl] What to do about "not in log"?

Mon Oct 2 14:49:26 EDT 2006

Ummmm, well, I wouldn't go so far as to use the term "pirate." I'd say that there's insufficient data to determine that, unless you got a large batch in all pointing to the same time frame.
It could be a busted or miscopied call (missing letter, one digit off, etc.) or otherwise honest mistake. It could be a logging error. It could be an attempt to get a card out of you by sending in a totally bogus request. And I'm sure we could think up a hundred more reasons.
(I've always wondered how many DX cards are or were sitting at the bureau for N3VAW or W3VAW, simply because of the number of stations who simply couldn't grasp that my old WN3VAW call was actually legit)
I say best thing to do is return it with your next outgoing buro shipment marked "NIL" and leave it at that. No point in embellishing without more data.
73, ron w3wn
From: Ed.Cox at legerity.com
Date: 2006年10月02日 Mon PM 01:34:05 CDT
To: dx-qsl at mailman.qth.net
Subject: Re: [Dx-qsl] What to do about "not in log"?
Interesting question to ask! I guess that I'd try sending it back in my 
next outgoing buro package. What about if you get a QSL for an old 
callsign for a QSO that supposedly happened a year after that call was 
invalid. And you didn't work the guy under any call? I suppose I'll 
answer it with an invalid card (e.g. one with invalid written across the 
face) having a note that the callsign was invalid and possibly a pirate.
Ed KE3D
"Don't it always seem to go that you don't know what you've got...till it's gone." 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 !!