Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+FW\:\s+\[N1MM\]\s+wont\s+accept\s+3Z1918PR\s+as\s+a\s+vaild\s+callsign\s+in\s+qtc\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+FW\:\s+\[N1MM\]\s+wont\s+accept\s+3Z1918PR\s+as\s+a\s+vaild\s+callsign\s+in\s+qtc\s*$/: 2 ]

Total 2 documents matching your query.

1. [RTTY] FW: [N1MM] wont accept 3Z1918PR as a vaild callsign in qtc (score: 1): Author: "Dick White" <whiter26@sbcglobal.net>; Date: Sun, 9 Nov 2008 17:24:43 -0600; I was doing S&P. When I found the 3Z1918PR call N1MM did not take it when clicked on. . So, I typed in the call and worked him. N1MM logged it ok. It was a simple thing to do and didn't take up much; /archives//html/RTTY/2008-11/msg00047.html (8,493 bytes)
2. Re: [RTTY] FW: [N1MM] wont accept 3Z1918PR as a vaild callsign in qtc (score: 1): Author: Fabi va2up <va2up@live.ca>; Date: Sun, 9 Nov 2008 21:37:28 -0500; Hi Dick, yes to log it is quite simple but to receive it in qtc exchange was a lot less fun let me tell you...I got it hihi. I had to change it to another callsign and then re edit into the log since; /archives//html/RTTY/2008-11/msg00053.html (10,179 bytes)

Current List: 1 - 2
Page: [1]