--part1_157.22b3357.28f3cb67_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
--part1_157.22b3357.28f3cb67_boundary
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <owner-nccc@contesting.com>
Received: from rly-za04.mx.aol.com (rly-za04.mail.aol.com [172.31.36.100]) by
air-za05.mail.aol.com (v81.9) with ESMTP id MAILINZA57-1008231051; Mon, 08 Oct
2001 23:10:51 -0400
Received: from contesting.com (dayton.akorn.net [216.1.128.73]) by
rly-za04.mx.aol.com (v80.21) with ESMTP id MAILRELAYINZA45-1008231038; Mon, 08
Oct 2001 23:10:38 -0400
Received: from dayton.akorn.net (dayton.akorn.net [216.1.128.73])
by contesting.com (8.11.2/8.11.2) with SMTP id f993AaZ02208;
Mon, 8 Oct 2001 23:10:36 -0400
Received: by dayton.akorn.net (TLB v0.10a (1.23 tibbs 1997/01/09 00:29:32));
Mon, 08 Oct 2001 23:10:28 -0400 (EDT)
From: AD6E@aol.com
Message-ID: <140.2ca44d4.28f3c496@aol.com>
To: <writelog@contesting.com>
Date: Mon, 8 Oct 2001 23:10:14 EDT
Subject: Re: [NCCC] Re: [WriteLog] CQP logging
To: Darrell.Earnshaw@sun.com
CC: NCCC@contesting.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: AOL 5.0 for Windows sub 138
Sender: owner-nccc@contesting.com
Precedence: bulk
X-Sponsor: W4AN, KM3T, N5KO & AD1C
Hi Darrell,
Use OK1 instead of OK (for example) so it doesn't get confused with W5.
However, If you've already worked the W5 version of OK then another OK from
the OK1 won't hurt anything.
Please don't just leave the QTH field blank! This will guarantee the log
checkers will catch it even if the other guy doesn't send in a log. You'll
get dinged for a mis-copy.
73, Al AD6E
In a message dated 10/8/01 15:27:56 Greenwich Standard Time,
Darrell.Earnshaw@sun.com writes:
<<
Yep, again it wasn't intuitive. I just left the QTH field blank for DX
stations. I'm still not sure what is the correct approach. Putting in
the prefix doesn't work ("OK" for a Czech and/or Oklahoma station...).
-- Darrell NR3Y/6.
>>
--
Submissions: nccc@contesting.com
Administrative requests: nccc-REQUEST@contesting.com
Problems: owner-nccc@contesting.com
--part1_157.22b3357.28f3cb67_boundary--
|