Let me get this straight. You may or may not keep a log, that is up to you.=
=20
They are now saying that if you can't confirm the QSO because you don't=20
have a log, then you can't view the card, so you can't get the QSO data=20
from THEIR card so that you know what to put on your card. In other works=20
if I needed a card from VE5 all I would have had to do was send you a card=
=20
with made up information on it & you would have put the same information on=
=20
your card and posted it back to me. to me this just confirms that they=20
needed to close that avenue. If I can't confirm a QSO I don't send an QSL,=
=20
paper or e. If you do then you are not really helping the system.
Or am I mistaken. Is there another reason that you would be unable to=20
confirm a QSO?
At 11:18 AM 4/3/02, Sylvan Katz wrote:
>So what do other people think about eQSL.cc change of policy?
>
>The main page of the web site now says:
>
>"We are one step closer to DXCC acceptance with the modification of our
>InBox. You can now only display/print eQSLs that you have confirmed."
>
>So for those of us who have no interest in the ARRL DXCC award and who by
>law are not required to keep a log but simply wish to return an eQSL out of
>courtesy we can no longer send reply eQSLs using eQSL.cc.
>
>Over the past year I have enjoyed receiving a few hundred eQSLs. I have
>faithfully responded to each and everyone with a courtesy eQSLs. My
>apologies to all of you who recently sent me a eQSL via eQSL.cc -- now you
>are likely to receive a email indicating that I reject your eQSL. It seems
>that until eQSL.cc reverses its policy not only will I not be able to
>respond to your eQSLs to VX5ZX and VE5ZX .... In fact, I will not even be
>able to look at your eQSLs. What a pity!
>
>.. sylvan
>
>=D4=BF=D4=AC
>----------------
>Sylvan Katz, VE5ZX
>Saskatoon, SK
>http://www.dynamicforesight.com/~ve5zx
>
>_______________________________________________
>CQ-Contest mailing list
>CQ-Contest@contesting.com
>http://lists.contesting.com/mailman/listinfo/cq-contest
Jim Rhodes K0XU
jim@rhodesend.net
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
|